On 12/27/2017 7:01 PM, Dave Weis wrote: > Where it gets odd is that if I change that action definition to the > following and completely stop and start Tomcat from Eclipse I still get an > error: > > <action name="logout2"> > <result>/landing.jsp</result> > </action> > <action name="logout"> > <result>/landing.jsp</result> > </action> > > Struts Problem Report > > Struts has detected an unhandled exception: > *Messages*: > - No result defined for action com.subecon.actions.auth.LogoutAction and > result success > ------------------------------ > Stacktraces > *No result defined for action com.subecon.actions.auth.LogoutAction and > result success* > > > com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:375) > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:277) > > org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:253) > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:247) > > .... rest omitted. > > You can see there is no mention of LogoutAction in the struts.xml file yet > it's still being called. This is with a complete stop and restart of Tomcat.
Maybe you have struts-convention-plugin and it automatically maps /auth/logout to LogoutAction.
