Ah. The reason I ask is I had a similar problem but with the updated StrutsPrepare and StrutsExecute filters. Spring Security modified the request in a way that Struts was not expecting and therefore Struts could not find what it was looking for. You may need to step through Spring Security and Struts and watch the request to see what changes made in Spring Security are affecting the Struts interceptors.
dubrovsky wrote: > > > dusty wrote: >> >> What is your filter order in web.xml. Can you show your web.xml config? >> > > Yes, of course. I think my web.xml is all right. Here it is: > > <display-name>Infm Client</display-name> > <context-param> > <param-name>contextConfigLocation</param-name> > <param-value>/WEB-INF/applicationContext-beans.xml > /WEB-INF/applicationContext-security.xml</param-value> > </context-param> > <filter> > <filter-name>springSecurityFilterChain</filter-name> > > <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class> > </filter> > <filter-mapping> > <filter-name>springSecurityFilterChain</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> > <filter> > <filter-name>struts2</filter-name> > > <filter-class>org.apache.struts2.dispatcher.FilterDispatcher</filter-class> > </filter> > <filter-mapping> > <filter-name>struts2</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> > <listener> > > <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> > </listener> > > -- View this message in context: http://www.nabble.com/Spring-Security-method-security-with-struts2-make-all-request-params-in-action-NULL-tp21624393p21709119.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
