Your work with the modular db actions and the sql transformer will not be portable since they are tightly coupled to Cocoon. This is going to limit you at some point when you want to write some junit tests or command line apps.
Furthermore, I've found that both the sql transformer and the modular db actions are fairly buggy and quite incomplete in what they offer. Try doing some complex stuff with multiple queries and transactions to see what I mean.
More importantly: Hibernate, OJB, or JDO are much more compelling. You'll be several times more productive using one of these than you will by hand-coding sql, mapping resultset data back and forth, etc. These ought to be wrapped in a facade and exposed to your application that way rather than intersprinkling lots of sql stuff throughout your sitemap.
phil.
Kim Toms wrote:
I have cocoon and can create pages reflecting queries in the database.
I recently got enough working to be able to change the database.
The question is, what is the best procedure to perform SQL "Update" or "Insert" type statements?
Choices appear to be - Modular DB action; database logicsheet; put statement in XML and have it transformed by transformer="SQL". I'd just like to know which is viewed as the most modern of these.
If I choose to write a new action, is there a way I can get at the DB pool that the other pieces of cocoon uses?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Whirlycott Philip Jacob [EMAIL PROTECTED] http://www.whirlycott.com/phil/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
