tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14261] - JNDI data source not configured correctly.
Date Wed, 05 Feb 2003 11:15:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14261>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14261

JNDI data source not configured correctly.





------- Additional Comments From ole@sugarshark.com  2003-02-05 11:15 -------
I have run into something what seems like this bug as well. I have a DataSource
with a selfwritten JNDI ObjectFactory configured in the DefaultContext:

<DefaultContext>
  <Resource auth="Container" name="jdbc/TCDB" scope="Shareable"
     type="de.cegedim.iss.tyrex.OracleXAConnectionCacheTyrexImpl"/>
  <ResourceParams name="jdbc/TCDB">
    <parameter>
      <name>factory</name>
      <value>de.cegedim.iss.naming.OracleConnectionCacheFactory</value>
    </parameter>
    ...
  </ResourceParams>
</DefaultContext>

I have a ServletContextListener registered. In the #contextInitialized method
and during Servlet#init the DataSource returned if of type BasicDataSource and
the driverName is null.

But when the first request comes, everything works as intended. A JNDI Lookup
returns a OracleXAConnectionCacheTyrexImpl.

when I put the same Resource definition into a <Context> tag for a single
webapplication, it does work even in the
ServletContextListener#contextInitialized method. It seems like the binding of
Global Resources to the context happens to late.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message