All you need is the orion.jar. Here is an example
client:
package com.test;
import java.rmi.RemoteException;
import java.util.*;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.ejb.EJBException;
import javax.ejb.FinderException;
import javax.rmi.PortableRem
,ex2)
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 19, 2001 12:21 PM
To: Orion-Interest
Subject: RE: Which JAR do I need to run an external client app
In my case at least it is java:whatever-is-in-application-client.xml or
orion-application-client.xml that's not available. Is there any o
do I need to run an external client app
Peter,
The problem you are experiencing is because the JNDI locations need to be
changed when the location of the client jar is changed -- namely change
'java:comp/env/' to 'java:hello/client/' or some other path that is
appropriate. &#
This problem seems to be similar to what I have been running into when
trying to start an Application Client from WebStart - which also involves
copying the jars to the webstart cache.
It's got something to do with Orions jndi implementation, I suspect - we got
the same thing running in another a
Peter,
The problem you are experiencing is because the JNDI locations need to be
changed when the location of the client jar is changed -- namely change
'java:comp/env/' to 'java:hello/client/' or some other path that is
appropriate. 'java:comp/env' is reserved for the application server's
envir
