JIRA added: 305
On 16 Sep 2004, at 00:37, Ken Horn wrote:
On 15 Sep 2004, at 23:07, Dain Sundstrom wrote:
On Sep 15, 2004, at 2:14 PM, Ken Horn wrote:
On WLS, the datastore on the default drivers is serializable (it's
bound to the clustered jndi, via a ClusterRemoteRef), and so an
servlet / ejb /
On 15 Sep 2004, at 23:07, Dain Sundstrom wrote:
On Sep 15, 2004, at 2:14 PM, Ken Horn wrote:
On WLS, the datastore on the default drivers is serializable (it's
bound to the clustered jndi, via a ClusterRemoteRef), and so an
servlet / ejb / client app can grab the ds from jndi (this may be
using
On Sep 15, 2004, at 2:14 PM, Ken Horn wrote:
On WLS, the datastore on the default drivers is serializable (it's
bound to the clustered jndi, via a ClusterRemoteRef), and so an
servlet / ejb / client app can grab the ds from jndi (this may be
using JNDI Reference / Factory stuff). The ds can the
On WLS, the datastore on the default drivers is serializable (it's
bound to the clustered jndi, via a ClusterRemoteRef), and so an servlet
/ ejb / client app can grab the ds from jndi (this may be using JNDI
Reference / Factory stuff). The ds can then create a direct db
connection from the cod
On Sep 15, 2004, at 7:11 AM, Ken Horn wrote:
Quick question on remote JNDI access.
Does the java: provider below one provide remote access -- ie j2ee
client app?
For security reasons, we want to be able to bind some/all resources
for a given app into a jndi tree (by any reasonable means: subtree
Quick question on remote JNDI access.
Does the java: provider below one provide remote access -- ie j2ee
client app?
For security reasons, we want to be able to bind some/all resources for
a given app into a jndi tree (by any reasonable means: subtree /
provider / naming convention) that cannot
