It shouldn't. The interceptor only autowires become the action invocation.
http://svn.opensymphony.com/fisheye/browse/xwork/trunk/src/java/com/opensymphony/xwork2/spring/interceptor/ActionAutowiringInterceptor.java?r=1063 -T. On 4/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Sorry Ted! I should have been more clear with my question. Does S2 leverage Spring in such a way as so fetch a new Action bean when the Action method returns SUCCESS? It appears a new bean is being injected into my Action when a method returns SUCCESS. Scott On 4/9/07, Ted Husted <[EMAIL PROTECTED]> wrote: > > By default, "input" is one of the magic methods that bypass > validation. In the case of a request for the input method, validation > is not applied, and input is returned. In the case of request for the > default execute/success method, input would be returned if validation > fails, and success returned if validation succeeds. Of course, if an > exception is thrown, then the exception handling would apply instead. > > HTH, Ted > <http://www.husted.com/ted/blog/> > > On 4/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I have an interesting situation occurring but let me first ask how the > > request lifecycle differs between returning INPUT or SUCCESS from an > action > > method. Consider this action mapping: > > > > <action name="course_*" method="{1}" class="course"> > > <result name="input">/pages/course.jsp</result> > > <result>/pages/course.jsp</result> > > </action> > > -- > > Scott > > [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
