Thanks Scott, it worked. All I need to do was put the following jar in remote
client's classpath:
$jboss-root\server\default\lib\jboss-common-jdbc-wrapper.jar
The said jar contains
"org.jboss.resource.adapter.jdbc.remote.DataSourceFactory".
One last thing though...following is the way I am ge
"jitesh_popat" wrote : Hi Scott,
|
| Thanks a lot for your reply.
|
| Agreed, I was able to bind the datasource to global JNDI. But while trying
to get it from a remote client, I directly do not get back
"javax.sql.DataSource" instance, instead I get "javax.naming.Reference" object.
W
Any access to the jboss jndi tree requires that the jboss object factories are
available in the jndi context configuration as many things in jndi are
references to information on how to create the indicated object. This is true
of all jndi providers.
View the original post :
http://www.jboss.
Hi Scott,
Thanks a lot for your reply.
Agreed, I was able to bind the datasource to global JNDI. But while trying to
get it from a remote client, I directly do not get back "javax.sql.DataSource"
instance, instead I get "javax.naming.Reference" object. Why is this? In case
of weblogic I can d
Thanks, will give it a try
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862687#3862687
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862687
---
The SF.Net email i
4.0.x has a native proxy and all DataSources are available remotely. You need
to specify a use-java-context=false to avoid binding the data source under the
java: context which is a vm local construct in order to be able to lookup the
DataSource from a remote client. The following template binds
