RE: Missing JNDI support in DataSource implemenataion

[Schroeder, Alexander]

Title: Missing JNDI support in DataSource implemenataion

Hi Staffan,

-----Original Message-----
From: Staffan Furn [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 26, 2003 1:02 PM
To: [EMAIL PROTECTED]
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.  

At first, I don't know exactly what your application server does here, and whether you will get some advantage of this, as the connection pool data source provides only some callbacks where a JDBC driver developer can put special things, if they are needed and bring benefit for the driver, and where the application server provider can do special things to monitor and handle the connections. For SAP DB there are no such special things necessary. Having a lot of JDBC 2.0 driver out there I assume the application server vendor will have some pooling implemented anyway, independent of whether the connection was acquired via some DataSource, or using the DriverManager.

But of course it should work ...

  he 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?  

It was simply that the environments under which those implementations where tests were not so fussy as your application server. I assume those products all stored the properties elsewhere and supplied them from scratch when it was necessary to construct the instance. So, that particular feature just dropped onto the floor.

 experienced the same problems? 
 

 know of any solutions or workarounds for this problem?  

If you only want to use connection pooling, you may look into the server's documentation whether there is some pooling there for JDBC 2.0 drivers without data sources, and use this meanwhile. If you want to use those distributed transactions, you'll have to wait until a bug fix is prepared.

I would be grateful for answers!  

Staffan Furn  

Sorry for any inconvenience caused.

Regards

Alexander Schr�der