Right... That explains it...
Thanks to all who responded... I can see that it's explained at http://www.jboss.org/online-manual/HTML/ch01s15.html indeed, but it's a bit tricky, since on the jboss site, it is referred to as deprecated docs, so you don't really know which parts are relevant for jboss3 and which aren't... Hans On Mon, 2002-11-18 at 14:47, Stefan Arentz wrote: > > On Monday, Nov 18, 2002, at 14:12 Europe/Amsterdam, Brian Johnson wrote: > > > A "client" would be in the same VM if it was a servlet or something > > similar running within the app server. > > Back to the original question, if you need to talk to JBoss from a > different *process* or even a different *machine* then you will need to > specify the location of the initial context. > > The easiest way to do that is to include a jndi.properties file in your > client's classpath. Mine looks like this: > > java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory > java.naming.provider.url=jnp://localhost:1099 > java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces > > If you need to talk to a remote instance of JBoss then change the > provider.url accordingly. You can also programatically create the > properties and pass them to the constructor of the InitialContext(). > > S. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user >
signature.asc
Description: This is a digitally signed message part
