The problem is that there's not a one-size-fits-all answer to the question.
A lot depends on the size and scope of your application, the state of your database, and the preferences of your developers. Of the three, what your developers think might be the most important. People can make any system work, but they have to *want* to make it work. The best answer, really, is to code a representative part of your application either way, and then decide. If the application isn't important enough to code some trials, then it's not important enough to sweat the decision either. Pick one and have at it. HTH, Ted. On 7/21/05, Access Denied <[EMAIL PROTECTED]> wrote: > Alls, > > I can't seem to get a convincing answer to the question of using an > ORM utilitiy, DB interface framework, or home-grown POJO DAOs. Would > you guys with experience in these methodologies comment, please? I > think I am spending too much time reading propaganda from iBatis and > Hibernate, don't think JDO is ready for prime time yet, and it seems > no one is writing their own DAOs anymore. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
