Hi!
Aaron Mulder wrote:
> On Sat, 4 Nov 2000, Rickard [iso-8859-1] �berg wrote:
> > You are correct in that jndi.properties is particularly static and
> > should not change between configurations. So, your workaround is rather
> > good.
>
> I'm not sure I agree. If you run jBoss twice out of the same
> installation, and just point it to different config directories each time,
> the JNDI server has to listen on a different port for each, so the
> jndi.properties must be different for both (to include the appropriate
> ports).
Nope. Note that jndi.properties is only for clients of the JNDI
provider. The reason we have it in the configuration is that parts in
the server need to access JNDI. But, I recently made a little
optimization: leave out PROVIDER_URL and it will look for a JNDI
provider in the local host. And this is precisely how the configuration
is set to in the server, i.e. there is no tie in jndi.properties to what
port it is running on.
Do you see what I mean? Check jndi.properties and you will see that
provider URL is not set...
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
