cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: Why does Action extend ThreadSafe ?
Date Fri, 10 Aug 2001 14:26:46 GMT
On Fri, 10 Aug 2001, Jeremy Quinn wrote:

> At 12:21 AM +0200 10/8/01, giacomo wrote:
> >On Thu, 9 Aug 2001, Sylvain Wallez wrote:
> >
> >>
> >>
> >> Giacomo Pati wrote:
> >> >
> >> > Quoting Sylvain Wallez <sylvain.wallez@anyware-tech.com>:
>
> [snip]
>
> >> There are two distinct problems here that I'd like to discuss
> >> separately: XSP as actions and the Action interface.
>
> Fantastic work Sylvain!!
>
>
> >>
> >>                              --o--
> >>
> >> First, about the XSP-action : XSP is a great language to dynamically
> >> generate XML. The purpose of the XSP-action is to be able to easily
> >> generate XML fragments as part of actions processing (before generation
> >> starts). We have in our C1 apps a set of form validation and database
> >> update logicsheets that fit in this area and that I would like to adapt
> >> to C2.
> >
> >Well, I simply don't understand why you have to generate XML in a
> >Action.
>
> For outputting XML error reports from action-type tags used in the
> XSPAction that get rendered later by the Generator phase?

That doesn't answer my question. Rendering or marshalling is quite the
same process. So why does it have to be XML? XML is far from being an
ideal representation for inter object communication (Action ->
Generator).

Giacomo


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


Mime
View raw message