look up datasource failing~

[tntxia]

I deploy my application ear in jboss-4.0.4.CR2;
flow is jboss console:

8:27:45,218 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
18:27:45,500 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
18:27:47,156 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
18:27:47,625 INFO [A] Bound to JNDI name: queue/A
18:27:47,625 INFO [B] Bound to JNDI name: queue/B
18:27:47,625 INFO [C] Bound to JNDI name: queue/C

This is my client class :

InitialContext context;
try {
context = new InitialContext();
Object obj = context.lookup("java:/DefaultDS");
} catch (NamingException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}

When I run the class ;throw the exception :

javax.naming.NameNotFoundException: DefaultDS not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.netsboss.btoss.logic.traceInfo.test.Test.main(Test.java:22)

How can I write the jndi name for datasource in client class ?ths

[jaikiran]

Looking at your stacktrace it appears that you are looking up the datasource from a standalone java class. This will not work since datasources are not exposed remotely. Have a look at:

http://wiki.jboss.org/wiki/Wiki.jsp?page=HowCanIAccessADataSourceFromAClient

for more details

[weston.price]

Note, exposing a DataSource remotely is *not* encouraged.

But yes, that is the issue.

[jaikiran]

Note, exposing a DataSource remotely is *not* encouraged.

Mentioned this in the wiki as well so that this need not be repeated.

[weston.price]

Actually it is here

http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources

Note: JBoss does not recommend using this feature on a production environment. It requires accessing a connection pool remotely and this is an anti-pattern as connections are not serializable. Besides, transaction propagation is not supported and it could lead to connection leaks if the remote clients are unreliable (i.e crashes, network failure). If you do need to access a datasource remotely, JBoss recommends accessing it via a remote session bean facade.

But it doesn't hurt to have it in two places people won't read ;-)

[jaikiran]

But it doesn't hurt to have it in two places people won't read ;-)

:-)