Your remark is for when accessing JNDI server outside JBoss.
For the simple case : one jboss server being the JNDI server itself, if I
remember, from within one JBoss VM, it is better to specify nothing at all
and if nothing is found, the JNDI client will know the JNDI server is itself
and avoid Network call.
And that would be the WARNING that JBoss gives when he found a
jndi.properties in its classpath at startup : "Hey you do not need to do
that! I know what I am doing! You will make network round trip for nothing!"
To be honest I am not sure about the explanation but the fact is I do not
need jndi.properties from inside JBoss to make JNDI lookup.
Vincent.
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Lennart
> Petersson
> Envoyé : jeudi 12 avril 2001 12:48
> À : [EMAIL PROTECTED]
> Objet : SV: [JBoss-user] Setting up the naming provider
>
>
> Also useable with core jboss (no tomcat). Just make sure you have
> your jndi.properties in your classpath.
> /Lennart
>
> ----- Original Message -----
> From: Vincent Harcq <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 12, 2001 8:29 AM
> Subject: RE: [JBoss-user] Setting up the naming provider
>
>
> > Hi,
> > If you use Tomcat 3.2.1, you can put jndi.properties in the
> Tomcat CLASSPATH
> > and you do not need any System.setProperty(). That's how JNDI
> client has to
> > find its property. And that's the more proper usage of it
> since you do not
> > need to put JNP stuffs somewhere else.
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
