Access Denied wrote: > it seems no one is writing their own DAOs anymore.
No one except those of us who have no choice. :) I use a multi-valued database, IBM's UniData, which does not [easily] speak JDBC. (The DBMS can, but there is a third-party app sitting on top of it that severely limits my options.) My only way in is through IBM's proprietary Java API, UniObjects for Java. Years ago I asked for help here, and was directed to the J2EE Data Access Objects pattern. Which I implemented from the ground up, all the POJOs, all the database-specific DAOs with interfaces in front of everything. So when you guys argue about whether iBatis or Hibernate is better, believe me, I'd be happy to be able to use EITHER one of them! At one time I thought JDO was going to help, and "Bean Managed Persistence" has always sounded promising. Unfortunately, all of the examples are SQL based and I don't immediately see how to plug in this strange API that does not have Connection or DataSource. Has anyone else had to deal with a non-JDBC data source? Is there anything I can do to make this as painless as possible? -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
