I've noticed what *looks like* a bug to me in Jboss 2.4.1 with tomcat.
I'm using the Weblogic JDBC driver. I tried to create mappings like this:/comp/jdbc/OrdersDataSource
This mapping doesn't work.
(from the startup log)
XA Connection pool comp/jdbc/OrdersDataSource bound to java:/comp/jdbc/OrdersDataSource
With this one, the code fails on ejbload creating a prepared statement even though the datasource creation is successful.
This one does work: java:/jdbc/OrdersDataSource
But, why does this one work where the first one fails. If I expand it to the JNDI name comp/env/jdbc/XXX I get a jdbc not bound error. Is there a limit to the number of levels the JNDI name can have in JBOSS? Or is jdbc not allowed in the context of env for some reason?
Also, if I specify the name as comp/env/OrdersDataSource
The server tries to use the hsql driver even though the WEBLOGIC driver is mapped to this JNDI name path. Is there a configuration option I missed somewhere?
--using the hsql connection
[Default] at org.hsql.Trace.getError(Trace.java:124)
[Default] at org.hsql.Result.(Result.java:70)
[Default] at org.hsql.jdbcConnection.executeHSQL(jdbcConnection.java:644)
[Default] at org.hsql.jdbcConnection.execute(jdbcConnection.java:540)
Could someone with more experience with JBOSS illuminate me as to why this is happening?