On Sat, 4 Nov 2000, Rickard [iso-8859-1] �berg wrote:
> 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
Let's say you run jBoss A with naming on port 1122 and jBoss B
with naming on port 1513. Now a session bean in jBoss A attempts to look
up an entity bean in jBoss A. To do so, it calls new InitialContext(),
which locates a jndi.properties. Since the PROVIDER_URL line is
commented-out, doesn't it look on localhost:1099 (the default) and
explode? If jBoss A JNDI server *was* on 1099, wouldn't jBoss B queries
look to the jBoss A JNDI server instead of the jBoss B JNDI server?
Or am I just missing some hook where the JNP implementation within
the server either 1) automatically knows what port to look at or
2) doesn't go out over the network at all?
Aaron
