You could use the MBean
to bring the remote context into the local jndi
> Unfortuntley not.
> You could use the MBean
> to bring the remote context into the local jndi
Thanks for the suggestion Adrian.
But will it be possible to bind that remote context into the ENC of the MessageBean or would it have to go into the Global JNDI namespace?
you can bind the external context into global jndi
then configure ENC in the usual way, i.e.
a the global jndi name.
> Not directly,
> you can bind the external context into global jndi
> then configure ENC in the usual way, i.e.
> a the global jndi name.
That's great - many thnx - it works exactly as I'd like it to and means I can remove remote hostnames/address/port numbers from my EJB descriptors.
One minor gottcha occurs if you define the ExternalContext::RemoteAccess property==true and have (as my application has) two 'sibling' systems with ExternalContext references to each other. Invoking the JNDIView::list service puts both systems into a spin as I assume it chases the reference round and round. Setting RemoteAccess == false avoids this problem. Should I put a bug report in for this behavior?
You could post a bug report,
but it is really a user error for configuring
a recursive jndi.
I'm not sure it would be easy to detect
this definition, it could in principle hop over
any number of servers before returning to the