You dont nead to deploy the client on the server. you just do a lookup on the
JNDI server for finding your bean. you nead to have one jndi.propeties file in
your classpath.
sample jndi.properties
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.provider.ur
Use a simple java class that can look up the JNDI name you have given.
Once the lookup is successfull you can access the application.
The stand alone java application need not be on the same server.
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp:
Hi,
Thank you all for the replies.
It really was the missing link in the code.
Cheers,
Shai :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920976#3920976
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920976
--
Hi,
I have an issue on this even though I included the properties code as suggested.
I can get the InitialContext but when I lookup the ejb I get:
javax.naming.CommunicationException [Root exception is
java.lang.ClassNotFoundException: com.etc.etc.HomeInterface (no security
manager: RMI class l
anonymous wrote : Root exception is java.lang.ClassNotFoundException:
com.etc.etc.HomeInterface
This class in not in the classpath. Put this class in the classpath
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926757#3926757
Reply to the post :
http://www.
Ok that was as simple as that. I forgot to add the jar :)
Thanks mate.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926778#3926778
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926778
-
