[kpgelli]

I have this test EJB module for HelloWorld. From the
plugin I am able to deploy it in weblogic container. I
am able to access the remote interface if I set the
classpath including weblogic.jar, ojdbc14.jar and run
the HelloClient from the command promt.

But if I run the client in the plugin environment I am
getting this error:

java.lang.ExceptionInInitializerError
at
weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:481)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:444)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:350)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:313)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at
javax.naming.InitialContext.init(InitialContext.java:219)
at
javax.naming.InitialContext.<init>(InitialContext.java:195)
at examples.HelloClientW.main(HelloClientW.java:35)
Caused by: java.lang.NullPointerException
at
weblogic.utils.classfile.utils.CodeGenerator.<clinit>(CodeGenerator.java:31)
… 12 more
Exception in thread “main”

In the run configuration for the client I have
specified the VMParameters:
-Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
-Djava.naming.provider.url=t3://localhost:7001

and I have also included the jar files in the clients
classpath.

I have set the jre environment to jdk included in weblogic8.1

What else do I have to do in myeclipse plugin to be
able to run the client?

[Riyad Kalla]

Moving this to ‘Support’ forum.

[Scott Anderson]

Did you include tools.jar on your client’s classpath?

[kpgelli]

I have included these jars into bootstrap classes of the classpath of client:
J2EE1.3LibraryContainer (default from myeclipse plugin)
JRE System Library[WebJRE} (located in bea)
bea/weblogic81/server/lib/webservices.jar
bea/weblogic81/server/lib/weblogic.jar
bea/weblogic81/server/lib/ojdbc.jar
bea/jdk141_05/lib/tools.jar
bea/jdk141_05/jre/lib/rt.jar

I am using:
eclipse2.1.3 and for this project jdk1.4.1_05 (that is bundled in weblogic)…but my the default jdk on the computer is jdk1.4.1_02

[Scott Anderson]

The reason I asked about tools.jar was that from the stacktrace it appears that WebLogic is trying to generate remote proxies and would thus need the Java compiler. From what you said earlier, the fact that your client works from the commandline but not when launched as a Java executable within Eclipse does point to some sort of configuration problem. Your commandline version is able to pick something up from the environment that it can’t get to within Eclipse. Unfortunately, the error message doesn’t make what ‘it’ is too apparent.

[Author]

Posts