Hi,
D> With what?
Well, that was what I was asking myself. :) Problem is, the app hasn't
been touched since 4 years. So I kind of re-engineering here.
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?
Yes, as it turns out, I'm using a request filter defined in the
web.xml for the actions. It looks up the actions, fetches the original
bean of the form, and checks for every submitted request parameter if
the user has access. If yes, it replaces the attribute with the new
values, if not, the change will be discarded.
I'm currently trying to find out why the request filter doesn't work
anymore. I thought this is not connected to the new request processor,
as it's defined in the web.xml outside of struts. And I'm using the
old request processor in the struts-config.xml:
<controller processorClass="org.apache.struts.action.RequestProcessor" />
The only change I made to the filter was replacing
public HttpServletRequest getRequest()
by
public ServletRequest getRequest()
Arne
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
