JNDI datasource name bound but not accessible

[eric_lemaitre]

Hi all !

I made a MySQL datasource like examples show :

<?xml version="1.0" encoding="UTF-8"?>

<local-tx-datasource>
<jndi-name>MySQL_DS</jndi-name>
<connection-url>jdbc:mysql://localhost/test</connection-url>
<driver-class>org.gjt.mm.mysql.Driver</driver-class>
<user-name>admin</user-name>
admin
<min-pool-size>50</min-pool-size>
<max-pool-size>100</max-pool-size>
<blocking-timeout-millis>10000</blocking-timeout-millis>
<idle-timeout-minutes>15</idle-timeout-minutes>
</local-tx-datasource>


But once deployed I can see it only JNDI available in "java:" Namespace, while I want to access it from an external standalone client so its JNDI name "MySQL_DS" should be available in "Global JNDI" Namespace through a "namingContext.lookup("MySQL_DS")" with or without a "java:/" before the name. How can I achieve this ?

WebLogic datasource worked this way at first try :-(( .

Best regards.

[juhalindfors]

You cannot bind a datasource to the global namespace.

-- Juha

[eric_lemaitre]

Hi Juha !

I don't want to extend too much, but WHY isn't it possible to bind a datasource to global namespace ? For example, WebLogic an WebSphere do, while JBoss and BES don't. what are the reasons, EJB specs or editor's personnal choice ?

Thanks for having answered anyway.

[juhalindfors]

From maintainability and scalability point of view it makes more sense to have a server side component (such as a stateless session bean) to interact with your datasource rather than having a remote client using the datasource directly.

-- Juha

[eric_lemaitre]

Hi Juha !

Thanks for satisfactory comprehensive answer.

Best regards.