Yes Shale dialogs are very nice indeed :-)
On 11/9/05, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 11/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> >
> > Are there any chances for the following in the 1.2 spec? I would like to
> increase the learning curve w/ declarative action chaining ;-). For
> example, (notice the to-action-id element).
> >
> > <navigation-rule>
> >
> <from-view-id>/admin/removeUser.jsp</from-view-id>
> > <navigation-case>
> > <from-action>#{UserBean.deleteUser}</from-action>
> > <from-outcome>SUCCESS</from-outcome>
> > <to-action-id>#{UserLister.load}</to-action-id>
> > </navigation-case>
> > <navigation-case>
> > <from-action>#{UserLister.load}</from-action>
> > <from-outcome>SUCCESS</from-outcome>
> >
> <to-view-id>/admin/displayAllUsers.jsp</to-view-id>
> > </navigation-case>
> > </navigation-rule>
> >
> > This means you could implement a deleteUser action method that does just
> that, and there is no need to implement a method that has to delete the user
> AND reload a list of users. Developers could spend less time writing
> "compound actions" and our conf files could get even more bloated ;-)
>
> Dennis,
>
> In the mean time, you might want to take a look at how Dialogs are
> implemented in Shale. Instead of trying to corrupt :-) the standard
> navigation rules, it allows you to define transitions between action states
> and view states in a separate configuration file ... and you can explicitly
> chain action states together if you like.
>
> http://struts.apache.org/shale/
>
> Craig McClanahan
>
>
> > Dennis Byrne
> >
> >
>
>
