It should not be set. The cvs was not working because multiple jndi.properties
and been placed on the classpath and one had an empty url provider which
caused problems.

----- Original Message ----- 
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 7:16 PM
Subject: RE: [JBoss-dev] CVS update: jbossmq/src/etc/conf/default jndi.properties


> What is the deal with setting/not setting this property?  With a CVS
> shapshot of jboss last week I was unable to get my application to work
> correctly unless this was set, where it was working fine with 2.2 (I think
> it was 2.2).
> 
> Any ways, I am still working on build systems, and have not had time to
> track this down, but I am curious what the effect is either way.
> 
> --jason
> 
> 
> 
> On Sun, 24 Jun 2001, marc fleury wrote:
> 
> > |  User: chirino
> > |  Date: 01/06/24 14:51:57
> > |
> > |  Modified:    src/etc/conf/default jndi.properties
> > |  Log:
> >
> > |   # Do NOT uncomment this line as it causes in VM calls to go over
> > |   # RMI!
> > |  -#java.naming.provider.url=localhost
> > |  +java.naming.provider.url=localhost
> > |
> >
> > Hiram... no log????
> >
> > why do you override the recommendation?
> >
> > marcf
> > |
> > |
> > |
> > |_______________________________________________
> > |Jboss-development mailing list
> > |[EMAIL PROTECTED]
> > |http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
> 


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to