From: Tim Olson [mailto:[EMAIL PROTECTED]
oh? i'd like to hear about that.activities often have results which need to be displayed byah, okay. this requirement is neither an argument for nor against flowscript (it should be very easy to implement it using flowscript)
the generated page, and the emission of XML seems very natural to me.
as you described your scenario you collect xml streams and write them in some store (whatever this store is - maybe an object in the users's session). This can be easily done with flowscript.
Then, to provide a view of your store can be done using a pipeline with a generator capable reading this store.
Yep. It's as simple as storing DOM nodes or objects implementing XMLizable in request attributes and outputing them in an XSP with an <xsp:expr><request:get-attribute name="foo"/></xsp:expr>
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
