Hi Paul,
I just dropped an example in the mailing list. For some reason Orion does not need
you to generate stubs. I do not fully understand how they get away with that. Wrt. your
ClassNotFoundException, which class can't be found?
It could be a bogus setting in the jndi properties or a bogus application-client.xml?
Frank
On Tuesday, August 22, 2000 4:37 PM, Paul Knepper [SMTP:[EMAIL PROTECTED]] wrote:
> I've been trying to get my standalone java client to access EJBs on a remote
> machine, but with no luck. I've deployed a J2EE application with my EJBs in
> it. But I can't figure out how to generate the stub classes.
>
> I can't find the Orion tool to generate the stub classes that the client
> would normally reference from the CLASSPATH (as described in "Java 2
> Enterprise Edition Developer's Guide" page 95). How do you generate the
> stub classes that enable the client to communicate with the enterprise bean?
> This is a simple thing to do with the deploytool that comes with Sun's J2EE
> Reference Implementation. During deployment you simply select a checkbox
> labelled "Return client Jar" when you deploy the application.
>
> I don't understand how the client can resolve the EJB classes if you don't
> have the client stubs to include in your CLASSPATH. I keep getting a
> java.lang.ClassNotFoundException exception.
>
> Also, what else do I need to deploy to my client machine, just orion.jar?
>
> Thanks,
> Paul Knepper
> <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
>
>
> << File: ATT00000.html >>
