cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject Re: JXTemplates - what's in a name?
Date Wed, 05 May 2004 12:02:30 GMT
On Wed, 2004-05-05 at 11:34, Derek Hohls wrote:
> Bruno
> 
> Thanks for helping clarify this - maybe all this is "obvious"
> to well-seasoned developers, but perhaps not to everyone.
> 
> To continue; assuming that inserting database records, 
> modifying object models etc does not take place anywhere in
> the pipeline; where *does* it take place in your application as
> a whole - in custom written actions?  in the flowscript??

Previously in actions, now that there is flowscript in flowscript. In
both cases, that doesn't mean you should put that all in there as one
big spaghetti-coded method. Delegate things to other components (plain
javascript or java objects, Avalon-based components, EJB's, whatever
that makes sense, but this falls outside the scope of Cocoon).

There's one important practical reason to do it that way (besides
maintainability, transparency and such): based on the results of the
operations you do, you can decide to redirect to some place else, call
another pipeline, whatever. If in the middle of your generator/XSP you
suddenly realise you want to show another page, you can't redirect
anymore since the output-generation process already started. (ok, if you
buffer all output you can, but that's a work-around [or worse, using
html meta-tags])

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message