java: signifies a VM name space. Are you running that code within the same VM?
If not, change the JNDI name to mySource, that should make it globally available.
All i just deployed one simple web application with spring capabilities..
When i call the JNDI name using simple JSP page with scriptlet i am able to get the connection object but when i give the same JNDI name to spring context it is not able to find the NAME in JNDI Tree...i belive spring does not run in a seperate VM?
For the refernce i am providing datasource configuration..
sql to call on an existing pooled connection when it is obtained from pool
And the server log says..
17:10:23,998 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=mysource' to JNDI name 'java:mysource'
i found the problem myself...when i include the hibernate related libraries with my deployed application none of the JNDI references working...when i remove them JNDI references working correctly..
does anybody experiences this..? any solution i need hibernate libraries to make spring DAO's work? How to resolve this situation?
This is just wiered behaviour from JBOSS 5.1.0 GA??
jboss-archive-browsing.jar from hibernate causing the problem to spring while identifying JNDI datasource...
Looks like the version i am using is not compatible with JBOSS 5.1.0???
Anyideas wht this library is used for?
Which version of Hibernate do you use? And please post the entire exception stacktrace.
i am using 3.2 version but JBOSS 5.1.0 has 3.4 in common\lib...removing the old libraries solved the problem...
it seems jboss-archiving-browsing.jar has no use in 3.4 version..