+ 100
I think implementations such as the one you are proposing to change have created a great deal of confusion in the java community about the relationship between DataSource and XADataSource.
If you can make it so ClientBaseDataSource can also be subclassed easily to implement ManagedConnectionFactory, so much the better.
thanks david jencks
On May 2, 2005, at 1:38 PM, Jeremy Boynes wrote:
The class hierarchy the client DataSources is:
ClientBaseDataSource | +-- ClientDataSource | +-- ClientXADataSource | +-- ClientConnectionPoolDataSource
The three standard interfaces DataSource, ConnectionPoolDataSource and XADataSource are not related to each other with different get??Connection methods that return different classes.
I would like to propose refactoring this so that all three extend ClientBaseDataSource directly which will mean moving some of the properties from ClientDataSource down into the base class.
Any thoughts on why this should not be done?
-- Jeremy
