Found it I think...
binds the datasource in the global jndi space.
I have a same problem.
Could you please contribute more detailed info about the <use-java-context/> and the global JNDI namespace
I have a <no-tx-datasource> that I want to use from a client. To enable the lookup of this datasource from a client running outside the container, I had to set the
in the datasource configuration.
By default, the datasource is bound to java: namespace which is not availabe outside the container. If you set the above option, the datasource is bound to the global jndi and a client can lookup and use it.
But, DO NOT USE THIS IN PRODUCTION. This is an anti-pattern.
Seems to work ok for me.
If using this is anti-pattern, then what is the better way to go about this? Specifically, I'm using a DatabaseServerLoginModule from a remote client. Using the ProxyLoginModule was mentioned as an alternative in another thread.
Any examples out there?