Ugo said: > Sorry but this approach has never worked in practice for me. Programming > is hard and I don't think adding another level of abstraction is going to > change this any time soon. Class diagrams may be cool, if used as a tool for > communicating design between designers and programmers, but they tend to > promote a top-down approach whereby coding is seen as a purely mechanical > activity. Realizing that it isn't so is one of the greatest insights of the > Agile movement. > > Besides, Cocoon flowscript should be really only used for implementing the > flow between pages of your web application, whereas business logic should be > nicely tucked away inside a domain model. In other words, flowscripts should > be *very* simple, in which case I don't think you can simplify them further by > using a model.
Hmmm....if the flow is that simple (and I agree that it should be) then specifying it declaratively using and XML vocabulary should not be a big deal, since it won't be "hard programming". Business logic, on the other hand, is the "harder" stuff, and thus does not lend itself to declarative approaches. Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
