First off, I'm an Orion newbie, so I'm probably doing something stupid.
I'm trying to deploy the ConverterApp example distributed with the J2EE
RI from Sun (described in Chapter 2 of its User Guide). I added this
line to server.xml:
<application name="Converter" path="/my/path/ConverterApp.ear" />
To run the ConverterClient with the J2EE RI, I had to include in the
classpath the ConverterAppClient.jar file that was created when I
deployed the application. But I didn't think I'd need to do that with
Orion since it builds the stubs on demand. I [naively] figured all I
had to do was set the JNDI properties on the client command line
properly and everything would just magically work! But instead I got
the following error.
$ java
-Djava.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
-classpath $HO\
ME/usr/orion/orion.jar:. ConverterClient
Caught an unexpected exception!
javax.naming.NamingException: META-INF/application-client.xml resource
not found
at
com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext(JAX,
Compiled Code)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java,
Compiled Code)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java,
Compiled Code)
at javax.naming.InitialContext.init(InitialContext.java, Compiled
Code)
at javax.naming.InitialContext.<init>(InitialContext.java, Compiled
Code)
at ConverterClient.main(ConverterClient.java, Compiled Code)
Why does Orion require an application-client.xml file? Assuming I
figure out what that file should look like, do I really have to wrap it
and the client class up in a jar file just to run a simple test???
Thanks for any light you can shed.
