...Persistence layer: OJB, Hibernate or similar O/R mapping tool Business logic: Java classes Controller: Flowscript View: JXTemplateGenerator or Velocity
Don't let anyone try to convince you that you can find a better combination for Cocoon. You won't....
But some of us (some of me at least ;-) still think that direct SQL *might* make sense for the database access layer depending on your app, environment and skills.
I'm 100% with Ugo in the general case, but I wouldn't want us to "lose" users because they think they must learn too much stuff to be productive with Cocoon.
It mostly depends on what a "quite big web site" is. Generating a couple hundred thousand pages out of a database with direct SQL would be no problem if the database schema is a simple one and if you're doing "read-only" stuff, only generating XML out of the database, not writing to it.
Of course, as soon as you start talking transactional processes and/or complex databases, a persistence layer like Hibernate or OJB is way better in terms of clean structure and maintainability.
Unfortunately the situation for direct SQL with Cocoon is suboptimal (IMHO) at the moment: the components mentioned by Ugo are the latest and greatest stuff, all very well designed and functional, but the "direct SQL" stuff (ESQL and SQLTransformer) is not as "modern" in concept or as "nice" to write code for. The Groovy-based SQL query stuff could improve things, at least on the "nice to write" front, but it's only vaporware ATM (fairly hot vapor though ;-)
Hope this helps, trying not to add to the potential confusion here...
-Bertrand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
