aspose file tools
The moose likes JDBC and the fly likes Why don't  XADataSource and ConnectionPoolDataSource extend the DataSource interface? Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of Mongo DB Applied Patterns this week in the MongoDB forum
or a resume review from Five Year Itch in the Jobs Discussion forum!
JavaRanch » Java Forums » Databases » JDBC
Reply Bookmark "Why don Watch "Why don New topic
Author

Why don't XADataSource and ConnectionPoolDataSource extend the DataSource interface?

Dan Bizman
Ranch Hand

Joined: Feb 25, 2003
Posts: 387
Can someone explain this logic to me? Why aren't they all DataSources? Wouldn't it have made more sense and cleaner code to have them all be DataSources so that the common elements could be handled the same way and the diff. elements could be handled by casting when needed? Am I missing something?
steve souza
Ranch Hand

Joined: Jun 26, 2002
Posts: 852
I was wondering that myself. I recently coded a jdbc driver for jamon and looked into doing a DataSource, but found it all to be quite confusing. Also it would have been nice if somehow DataSources would have leveraged the Driver interface somehow.


http://www.jamonapi.com/ - a fast, free open source performance tuning api.
JavaRanch Performance FAQ
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Why don't XADataSource and ConnectionPoolDataSource extend the DataSource interface?
 
Similar Threads
NoClassDefFoundError for driver in db2java.zip
Datasources and databases
Configuring multiple datasources
rollback() and setRollbackOnly()
Connecting to MySQL 5 in JBoss 5 AS