I guess it would be good enough when you do the lookup in the JNDI tree.
Just deploy the beans with a known JNDI name to the server.
I'v read the thread about loading the JDBC classes on a PA RISC system, and I have the
same problem on HP/UX 11. Starting the Orion server in the Orion root path does not
help, copying it into $JRE/lib does the job, but it seems to be an UGLY hack.
Java HotSpot(TM) Server VM (build 1.3.1
I have created an orion-ejb-jar.xml descriptor for the Session bean Foo and
Foo2, but I can't succeed in looking up the object using JNDI. The
descriptor is located in META-INF/ in the EJB jar and looks like this:
===
orion-ejb-jar
enterprise-beans
session-deployment name=Foo