Re: Missing JNDI support in DataSource implemenataion

[Martin Cordova S.]

Title: Missing JNDI support in DataSource implemenataion

All I can tell you is that I have successfully used the SAPDB driver (com.sap.dbtech.jdbcext.ConnectionPoolDataSourceSapDB) with WebSphere 4.x, which also requires a driver that implements the DataSource APIs.   I have a very brief how-to about configuring SAPDB for WebSphere 4 in case you are interested.   Regards, Martin   ----- Original Message ----- From: Staffan Furn To: [EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 8:01 AM Subject: Missing JNDI support in DataSource implemenataion Hi! I�m using SapDB with an application server (Borland Enterprise Server to be more precise) and want to use the SapDB implemenation of ConnectionPoolDataSource in order to take advantage of connection pooling. The problem is that when I deploy my datasource definitions in the app server the naming service generate errors during the binding process. After inspecting the jdbc driver source, I�ve seen that the DataSource and ConnectionPoolDataSource implementation does not implement java.io.Serializable nor javax.naming.Referenceable, which as far as I understand it, is required in order to support JNDI binding and look-up on the data source. I�ve looked at the jdbc implemenation of other databases (like MySQL for example) and they all have  JNDI support in their data source classes. Does anyone have an explanation why these interfaces are not implemented? experienced the same problems? know of any solutions or workarounds for this problem? I would be grateful for answers! Staffan Furn