Askild Aaberg Olsen wrote:
Why is tightly coupling my data access code to Hibernate so much better
then, isn't this yet another framework (like EJBs)?
What if I don't have the need to reuse this code?
What if I'm just a newbie trying to get some data into my webapp?
I should clarify that I'm not necessarily advocating Hibernate or OJB,
because those two particular solutions come with baggage.
What I would recommend is wrapping all of those implementation details
behind DAOs. This way, you're not coupling your application logic to
anything but your own DAOs.
How does one does this in a reusable way while using modular database
actions or the SQL transformer? The answer is that you can't. And that
makes it a bad idea.
I never argued Hibernate/OJB wrong or bad practive, I just outlined an
alternative method to get a simple db-driven app up and running using a
stock Cocoon, without the need to write a single line of Java-code (not
using modular db actions, by the way...).
I'm not sure what the value of this is. This approach seems like it
will get you 20% of the way to something useful really quickly.
phil.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
