> 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?
Nope :-)
> 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?
Nope :-)
> 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?
2). If PROVIDER_URL is not set at all == use VM local server. Check
org.jnp.interfaces.NamingContext.checkref() method for details. This was
done
a) to remove configuration hassles with server components using JNDI
b) for performance
/Rickard
