• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Entity Bean Not getting Bound to JNDI in WLS 6.1

 
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi folks ...
I am trying to deploy the Classic 'CabinBean'on
WLS 6.1. On running the client , I am getting the following Exception Stack Trace . Clearly my Remote Object is not getting bounnd to the JNDI tree , which I have confirmed by checking the JNDI tree in Weblogic Console . I can see my other Session Beans Bound there but not my Cabin Entity Bean & also DataSource (for The connection pool required for Entity Beans).
Any Suggestions of how to deploy the Entity Bean,
Any typical problems in the ejb-jar.xml or weblogic-ejb-jar.xml files that I could have done


*************************************************
javax.naming.NameNotFoundException: Unable to resolve CabinJNDI. Resolved: '' Unresolved:'CabinJNDI' ; remaining name ''
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at Client_1.main(Client_1.java:22)
*************************************************
 
reply
    Bookmark Topic Watch Topic
  • New Topic