Hi Jeromy, Thanks for the info. Several of the interceptors require configuring, for example the Scope interceptor. The example provides some examples of this. However it seems that the only way to configure a interceptor is to redefine an interceptor stack. Is this correct ? Can I not just use the default stack, and configure the specific interceptor for a specific actions use ?
Regards Ian CSC Solutions Norge AS Registered Office: Sandsliåsen 57, 5254 Sandsli, Norway Registered in Norway No: 958 958 455 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Jeromy Evans <[EMAIL PROTECTED]> 09.04.2008 01:23 Please respond to "Struts Users Mailing List" <[email protected]> To Struts Users Mailing List <[email protected]> cc Subject Re: interesting proxy + action chain issue Ian Meikle wrote: > HI, > > I have been following this post with interest since I used the PRG pattern > in previous projects. > We are using struts 2 in are current project and I like the errorMessages > behaviour that is part of the Action. > > Is it possible to persist these over the PRG cycle ? > By default I assume they would be lost when we get to the GET stage since > they are request scope and the GET is a seperate request than the POST > that caused the error. > > Hi Ian, This is an issue that Struts2 needs to handle better. It can be done but its not as straight-forward as it could be. The scope interceptor [1] provides this feature. It allows you to specify which properties should be bound to session or application scope and injected into the action. The scoped modeldriven interceptor is for modeldriven actions [2]. Both are included in the default stack. The scope plugin allows annotations to specify which properties persist over a cycle. It's not bundled with struts but I have heard good comments about it [4]. [1] http://cwiki.apache.org/WW/scope-interceptor.html [2] http://cwiki.apache.org/WW/scoped-model-driven-interceptor.html [3] http://cwiki.apache.org/S2PLUGINS/scope-plugin.html [4] http://article.gmane.org/gmane.comp.jakarta.struts.devel/65052 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
