cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <tcu...@dff.st>
Subject RE: [PROPOSAL] mulitple actions per class
Date Tue, 12 Feb 2002 16:43:56 GMT
On Tue, 12 Feb 2002, Carsten Ziegeler wrote:

> > Torsten Curdt wrote:
> > <snip>
> >
> > > The verbose solution from above has the advantage that the
> > sitemap editor
> > > (the person writing the pipelines) sees which actions are available.
> >
> > Hm... that's true. But I guess these actions are would be mainly used for
> > webapp purposes and will be used with the cocoon-action parameter anyway.
> > Not inside the sitemap. ...but maybe we could provide both syntaxes?
> >
> Ah, you mean as an action-set, right?
> So something like this (don't quote me on the syntax):
>
> <map:action-set name="mysuperactionset">
>   <map:action type="multiaction" method="a" action="add"/>
>   <map:action type="multiaction" method="d" action="delete"/>
> </map:action-set>
>
> For this I'm +1.
>
> But I'm not sure about a
> <map:act type="multiaction method="a"/> somewhere in the pipelines
> section.

Yes, in particular for action-sets. Actually right now I am +0 for
supporting it within the pipelines but for consistancy reasons I tend to
+1. What would we tell someone on cocoon-users why it is not supported
within the pipelines?!

Is this also a +1 for the method-attribute syntax? ;)
--
Torsten


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


Mime
View raw message