Thanks Sami, I apologise. I know that there are a few different solutions around. We use a our own custom interceptor which works for us.
My point was more that I think that action chaining is probably the feature of S2 I find most trying. I suspect that of the work would be in improving the documentation. But at the same time I can understand that the documentation overall isn't the best and there are limited resources. My guess would be that it's being left to the authors of the various S2 books to deal with. Z. > Hi, > > you should take a look at Spring Web Flow > (http://www.springframework.org/webflow) and its Struts2 plugin > (http://cwiki.apache.org/S2PLUGINS/spring-webflow-plugin.html). > > Regards, > Sami Dalouche > > Le lundi 08 octobre 2007 à 15:03 +1000, Zoran Avtarovski a écrit : >> Action chaining isn't just to access logic in two separate action classes, >> but is often necessary when intermediate input is required from the user, >> for example complex forms which need to be broken down into multiple pages, >> wizards if you like. >> >> Since Struts 1 we have been sticking the user entered data in the session >> scope, which poses its own problems. I thought the big advantage of S2 was >> the ability to "easily" implement action chaining and let the framework deal >> with how to persist the data across multiple requests. But I'm finding that >> it's not the case. >> >> Z. >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
