> > BTW, can you explain how you use xsp-action?
I use xsp-actions with esql - this way you can not only fetch data from
databases quickly from xsp but also handle simple logic via actions.
> > Do you need xsp taglibs in an action or is it just a convenient way to
> write small custom actions without writing a java class?
>
> We just need 1 xsp taglib:
> xmlns:action="http://apache.org/cocoon/action/1.0";
xsp-request, xsp-response (setting caching headers and so on), esql,
xsp-session
> flow-actions? some people requested this before. I remember people angry
> because under the newer flow concept we don't allow a map:call flow
> without a sendpage() inside.
I have requested something upside down - the ability to call actions from
flow. It has been implemented in old FOM - now it's not even deprecated - it
just has been removed.
>
> I am not sure. I think everything can be done using flow. In that way I
> don't see flow-actions as something useful. Also sitemaps are cleaner
> without calling to much actions and branching inside.
>
> Of course this is my point of view. If some one else need it, go ahead. It
> is up to the users to choose what they need.
I do a MASSIVE amount of prototyping. With xsp-actions I manage to build a
nice looking and working prototype in few minutes/hours. It would be even
faster if I could call actions from flow.
Sometimes implementing something nice and clean is just a waste of time. My
prototypes are usually one look only and are thrown away afterwards.
Leszek Gawron
