I suspect the class hierarchy has been made this way partly to match Embedded driver. I am still thinking why the Embedded driver does this..
Satheesh 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 > > >
