A Model. One can use XML tu build Models which are independent from the specific implementation. An example could be a UML Class Diagrams. You have a model (The Class Diagram Model) which is then converted in something concrete (ie. some .java files)
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.
Thank you! If we would have thought all the same way, the world "progress" will be never invented ;)
;-)
Ugo
-- Ugo Cei - Consorzio di Bioingegneria e Informatica Medica P.le Volontari del Sangue, 2 - 27100 Pavia - Italy Phone: +39.0382.525100 - E-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
