aspose file tools*
The moose likes BEA/Weblogic and the fly likes Resolve jndi names at deploy time Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Resolve jndi names at deploy time" Watch "Resolve jndi names at deploy time" New topic
Author

Resolve jndi names at deploy time

Pedro Gongora
Greenhorn

Joined: Oct 03, 2003
Posts: 17
hi, can anyone help me with these problem
when i deploy a webapp that calls an ejb it throws me this exception:
[weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'Test/TestEJB' declared in the ejb-ref or ejb-local-ref 'ejb/Test' in the application module 'testweb.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.]
but if i eliminate the ejb-ref entry on deplyment descriptor and access ejb like this
ctx.lookup("Test/TestEJB")
instead of
ctx.lookup("java:comp/env/ejb/Test")
on my code it just works !
any ideas will be wellcome
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Have you mapped the logical JNDI name into a real JNDI name using the vendor-specific deployment descriptor?


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Pedro Gongora
Greenhorn

Joined: Oct 03, 2003
Posts: 17
i didn't noticed that there are 2 different ways for resolving ejb links depending if they are application scoped (same ear) or external.
the doc. describing it is here
i hope it's useful for some one else
thanks !
 
Don't get me started about those stupid light bulbs.
 
subject: Resolve jndi names at deploy time