NameNotFound exception

Question

I am using weblogic 4.5. My application deployment descriptor shows like this:
SessionDescriptor
beanHomeName com.mortgagefamily.web.projects.loanstatus.businessservices.RequestDoradoLoanStatusHome
My client code is like this:
Context ctx = getInitialContext();
RequestDoradoLoanStatusHome home = (RequestDoradoLoanStatusHome)
ctx.lookup("com.mortgagefamily.web.projects.loanstatus.businessservices.RequestDoradoLoanStatusHome");
But when I try to run my client to find the bean with the given JNDI name I get
the following error.
dammala(ldevapp01)> java DoradoLoanStatusClient
Started client application
got context
javax.naming.NameNotFoundException: 'com.mortgagefamily.web.projects.loanstatus.
businessservices.RequestDoradoLoanStatusHome'; Remaining Name: 'loanstatus.busin
essservices.RequestDoradoLoanStatusHome'
at java.lang.Throwable.fillInStackTrace(Native Method)
at weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44
at weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
at weblogic.jndi.toolkit.WLContextStub.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(InitialContext.java:280)
at DoradoLoanStatusClient.main(Compiled Code)

Answer 1

Goutam Mukherjee <> writes:
The issue you are seeing has to do with client initialization - which is a big and hairy topic I won't bore you with. The simplest way to get this working is to use the J2EE appliction client which will ensure proper initialization - including the comp entries.
weblogic.j2eeclient.Main
You will need a generated client jar as well I believe.
andy
Hi,
we need to write a context propagation code. I tried the same using the example from - http://e-docs.bea.com/wls/docs90/programming/context.html#1058673. I have written the web service and it is getting the jndi for java:comp/WorkContextMap OK from it's own initial context. However, when I am writing a standalone java client to use WorkContextMap from the client side by getting a initial context to the weblogic 9.2 server by setting the initial context factory and the provider url, it does not work. I also tried by using only "WorkContextMap" in place of "java:comp/WorkContextMap". but that does not work either. How can this be fixed?
Just to test, I also tried to doa look up of "java:comp/UserTransaction" from the standalone client and it did not work either. I tried with different types of the jndi string - like with and without java:comp.
Here is the client code snippet -
               Hashtable env = new Hashtable() ;
               env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
               env.put(Context.PROVIDER_URL, "t3://172.20.8.211:7001");
               InitialContext ctx = new InitialContext(env) ;
               logger.info("in testEchoService...InitialContext=" + ctx) ;
               WorkContextMap map = (WorkContextMap) ctx.lookup("java:comp/WorkContextMap") ;
               logger.info("in testEchoService...map=" + map) ;
Appreciate your help,
Thanks.