I don't mean to start any kind of flame war here and the following is strictly my opinion.
Actually the statement below is the exact reason I and my colleagues are reticent to use flowscript. I have no problem with using flowscript to manage a couple of pages that are linked together (i.e. - a form to fill out followed by a confirmation page). But using it for more than this violates the separation of concerns principal that Cocoon strives to achieve through the sitemap. It is far too easy to start throwing all your business as well as presentation logic into flowscript and soon you'll end up with something worse than JSPs. This is impossible to do with just the sitemap. Frankly, I have been concerned with how so much effort seems to be focused on moving Cocoon from its sitemap roots to flowscript. -----Original Message----- From: Stephan Coboos [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 1:20 PM To: [EMAIL PROTECTED] Subject: Flowscript and return to pipeline Hello, in some discussions I'd heard that actions and XSP should be more and more replaced by flowscript. I think, this is a good idea because flowscript is a good way to integrate logic parts into an application. But with one thing I cant agree. Why shouldn't it be possible to return to the sitemap without sendPage? I had read some discussions about the decision, throwing a Exception if no sendPage existst within a flowscript but I think this decision was wrong.
