Hi, I used to filter the request parameters of certain actions. It works like this: the original bean is stored in the session. When the user hits update, the filter replaces the paramters submitted by the user with the original ones. Then, it replaces or deletes the values the user has changed and has access to. In that way I always end up with a valid bean...
I'm using a requestwrapper, as the parameter map of the original request isn't writable. My problem is now that as soon as the wrapper is used to encapsulate the request, the action mapping isn't working anymore. So after the user hits update, he returns to the start page (but he should be redirected to the UserDispatchAction). I thought about reimplementing my filters as chain commands, but that would be alot of trouble... And it doesn't help with the non-writeable parameter map. Any ideas why the request wrappers aren't working anymore? Arne Struts Users Mailing List wrote: D>> Something in your application is pre-loading the D>> dynaform with reasonable values, no? I don't really D>> remember S1.1 at this point; do you have a filter, D>> request processor, action controller, etc. other than D>> the default? A> Yes, as it turns out, I'm using a request filter defined in the A> web.xml for the actions. It looks up the actions, fetches the original A> bean of the form, and checks for every submitted request parameter if A> the user has access. If yes, it replaces the attribute with the new A> values, if not, the change will be discarded. A> I'm currently trying to find out why the request filter doesn't work A> anymore. I thought this is not connected to the new request processor, A> as it's defined in the web.xml outside of struts. And I'm using the A> old request processor in the struts-config.xml: A> <controller A> processorClass="org.apache.struts.action.RequestProcessor" /> A> The only change I made to the filter was replacing A> public HttpServletRequest getRequest() A> by A> public ServletRequest getRequest() --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
