On Sun, 15 Jul 2001, Jeremy Quinn wrote:
> Being able to make Actions using XSP TagLibs allows existing XSP languages
> a route into the 'ideal' way of working with Cocoon 2, where they have
> developed out of the usage patterns in Cocoon 1.
Why not drop Actions altogether and instead put XSP taglibs in that place?
It's all just Java, so why should we have two places to do our custom
logic? From what I hear Actions allow more than XSP (redirects etc.), but
XSP taglibs have the better interface (XML). So just put XSP in the place,
where Actions are right now and we'd all be fine?
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
