RT’s about Cocoon
Friday, April 23rd, 2004Ugo Cei recently wrote to cocoon-users:
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.
I’ve been having some ideas rolling around my head lately. They might be interesting, or they might not be.
What would the bare minimum for getting 80% of the webapp-programming needs accomplished under Cocoon? It looks like Ugo nailed it right on the head. Flow + Persistence Layer + Java Classes + Templates. Is everything else worthless? I don’t think so. Cocoon definitely suffers from the “kitchen sink” syndrome. Is there a way we can put these basic things together and still keep our best practices?
Perhaps 2.2 and “real blocks” will allow a basic Cocoon to be distributed, with only these simple things included. Still, there’s a huge learning curve.. but perhaps it would be lowered considerably if there was a lot less stuff to worry about, hence my idea of paring down Cocoon to the essentials.
Less stuff means less documentation to worry about. I just don’t like the idea of throwing code away.
And when 3.0 comes around, who knows what will happen.