For a more flexible flow control you can use selectors:
http://xml.apache.org/cocoon2/userdocs/selectors/selectors.html
Personally, I don't like selectors' syntax and prefer the Struts's version
of flow control:
<action name="logon" ...>
<forward name="success" path="welcome.jsp" />
<forward name="fail" path="login.jsp" />
<forward name="error" path="error.jsp" />
</action>
it works like a switch - case operator in Java and is less verbose.
The best for me would be to have all the following in one:
- flow control and form processing (from Struts)
- html, bean taglibs (from Struts)
- flexible matchers with wildcard and regexp patterns (from Cocoon 2)
- possibility to generate response from multiple sources: JSP, XML/XSL
(Cocoon 2)
- configurable page aggregation (Cocoon 2)
etc.
Regards,
Konstantin Piroumian
> Also, is it just me or is the flow control in sitemaps really weak?
>
> You have 1 option for flow control: returning a Map from an action. Flow
control is decided on whether the map returned from the action is null. If
it's null then the code within is skipped; if it's not null then it's
executed.
>
> Seems very limiting to me though. What if you want to return data back to
the sitemap regardless (e.g., success message if success; error message if
error)? You can't. If you return a message for both success and failure,
then the ability to do flow control is lost.
>
> The basic problem is that the Map returned from the action is the only way
to return data to the sitemap. But using it for flow control too really
makes things difficult.
>
> What if you want more fine-grained flow control? (e.g., if x do a; if y
do b; if z do c). Doesn't seem to be any way to do it.
>
> Agree/disagree?
>
>
> DR
>
>
>
> >Date: Wed, 14 Nov 2001 14:24:28 -0500
> >To: [EMAIL PROTECTED]
> >From: David Rosenstrauch <[EMAIL PROTECTED]>
> >Subject: Sitemap variables?
> >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
> >
> >Is it possible to set variables in the sitemap (i.e., similar to
xsl:variable)?
> >
> >I find myself passing the same map:paramaters in different places in the
map over and over again and would like to centralize this in one place.
> >
> >If not a map:variable, is it possible to set a map:parameter at the top
of the sitemap that applies globally?
> >
> >
> >Bonus question: is there other functionality that can be utilitzed in
the map besides that described in the docs (e.g., map:generate,
map:serialize, etc.) i.e., adding in additional code like as in xsp:logic,
or calling external taglibs?
> >
> >
> >Thanks,
> >
> >DR
> >
> >
> >---------------------------------------------------------------------
> >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]>
>
>
> ---------------------------------------------------------------------
> 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]>
>
---------------------------------------------------------------------
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]>
