users@glassfish.java.net

Re: Standalone Client - exception invoking method on EJB3 method

From: <glassfish_at_javadesktop.org>
Date: Tue, 29 May 2007 12:02:11 PDT

It appears my problem is that all my calls are actually connecting to a 'remote' localhost, i.e. my test unix machine which has another version of glassfish running AND an older version of the ejb w/ different interface, hence the exceptions.

 However, I can't get my test client to connect to a remote Naming service. I've tried both of the following from two different locations in the FAQ.

Using
 -Djndi.provider.url=corbaloc::mlingk.theocc.com:3700/NameService

and using jndi.properties directly in the classpath:
java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
java.naming.factory.url.pkgs=com.sun.enterprise.naming
java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl
jndi.provider.url=corbaloc::mlingk.theocc.com:3700/NameService

which throws an exception,
CLASSPATH component ./jndi.properties: java.util.zip.ZipException: error in opening zip file

and I've tried putting the jndi.properties in a jarfile, directly referenced first in the classpath, and it seems to be ignoring it altogether.

Is there a trick to getting the jndi.properties settings applied?

thanks again, Mike
[Message sent by forum member 'mlingk' (mlingk)]

http://forums.java.net/jive/thread.jspa?messageID=219320