Well, you could do that with chain now by writing an action that
deferred handling to a particular chain, but I do like the sitemap
concept as evidenced by my porting of their wildcard matching to
Struts.
It might be interesting for an alternate struts-config format that
does allow us to stick chain commands right in struts-config rather
than having them defined somewhere else and have it look kinda like
ant:
<action-mapping path="edit*">
<authorize type="{1}" />
<retrieveFormData type="{1}" />
<generateJsp path="/jsp/{1}.jsp" forward="success" />
</action-mapping>
Personally, however, I prefer something like struts-flow which allows
workflows to be defined in a more powerful scripting language. These
XML mappings work great for simple cases, but don't really for the
more complex workflows you'd find in a real application. I think that
was one of the main reasons why Struts developers insist on one Action
per request as Java is a much more capable workflow language than XML.
Don
On Wed, 10 Nov 2004 19:25:57 +0200, Emmanouil Batsis
<[EMAIL PROTECTED]> wrote:
> Don Brown wrote:
>
> >Well, pipelines won't work for Struts in the strictest sense, as they
> >rely on SAX and Struts isn't an XML transformation framework.
> >
> >
>
> Struts could use a sitemap thingy to pass a request along actions
> (without having the action choose an ActionForward). I guess that could
> work by consulting the sitemap object like
> mapping.findForward(sitemap.getForward(request));
>
> Manos
>
> ---------------------------------------------------------------------
>
>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
