There are a number of posts in the archive about how to configure the
initial context (either programmatically or by using a jndi.properties
file). In addition to that:
Define a META-INF/application-client.xml and package it in the client's
jar.
Define the application client in the j2ee application.xml descriptor
with <module><java>.
Package the client jar in the ear.
Deploy the ear file.
Run the client from the "applications" directory. Theoretically the
client has been "deployed", but I don't think Orion does anything to it
other than unpack the ear.
Make sure that orion.jar is in the classpath when executing the client.
This is more challenging that you would think. The Sun JDK 1.3 "java"
ignores the classpath (even if you specify it on the command line) if
you use the -jar parameter ($@#&%!!). You can either put your app
client jar and orion.jar on the classpath and specify the main class, or
you can put orion.jar in the Class-Path field of the
META-INF/MANIFEST.MF for your application client (but be careful of the
path).
If you're running on Windows, watch out executing the app client from
the orion "applications" directory (or whever you have it deployed to);
subsequent deployments of the ear file will fail with an IO error
because it can't write to the client jar file. Even if you haven't
changed the client jar file and it shouldn't need to be written.
There are probably other ways of doing this, but this is what seemed
most j2ee-correct to me. I imagine some app servers do something
special to the client in the process of deploying it, but Orion is not
that sophisticated (yet).
Jeff
>-----Original Message-----
>From: Alexander Jerusalem [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, February 21, 2001 2:11 PM
>To: Orion-Interest
>Subject: Application clients
>
>
>Hi,
>
>Can anyone tell what I have to do to use EJBs in Orion from an
>application
>client?
>
>thanks,
>
>Alexander Jerusalem
>vknn
>[EMAIL PROTECTED]
>
>
>
