No, I think it's really a case of chained actions. I have one action that get's called every time the "user form" is displayed in order to populate it with the pertinent information, i.e. the list of all users. I have got some other actions that handle deleting, creating and editing users. So if a user is deleted my app will call "DeleteUserAction" which deletes the user, puts a message stating "User Bond, James was successfully removed from our database." onto the property stack (is that correct ww2 lingo?) and transfers control to the "GotoUserMainFormAction" which reads the updated user list from the db and dispatches to "userMainForm.jsp". Obviously I will want the message issued by "DeleteUserAction" preserved along the action chain.
Anyhow, the ChainingInterceptor does the trick quite nicely. One minor issue that is left is that in "GotoUserMainFormAction" I have to implement a corresponding property "actionMessages" if I want these messages displayed on the result page. Is this how the ChainingInterceptor works, i.e. it transfers those properties that are also present in the second action from the first action to said second action? From the paragraph in the docs I would have guessed that the first action is preserved on the stack and any of its properties will be accessible as long as they won't be hidden by properties of the second action. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Patrick Lightbody > Sent: Thursday, November 13, 2003 4:46 AM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] [WW2] How to pass action properties in chained > actions > > > Sounds like you're doing a redirect rather than a real chain (or > dispatch at least), and so the properties could not possibly be chained > togther. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Olaf Bergner > Sent: Wednesday, November 12, 2003 5:09 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] [WW2] How to pass action properties in chained > actions > > Following the examples that come with WW2 (<ww:iterator > value="actionErrors"> ...) I use ActionSupport's actionErrors property > for > communicating errors to the user. Actually I found this feature so neat > that > I added an actionMessages property to my Action base class derived from > ActionSupport since sometimes I have some more in store form my users > than > only error messages ;) This works like a charm unless I chain actions, > which > I do quite often. In these cases the actionErrors and actionMessages > properties will get lost. Is there an elegant solution to this problem? ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
