I don't have a direct answer for you Rob, but what we did was to create a
custom tag that looks for errors in all scopes. Once it is rendered, then it
removes it from all scopes. This allows me to propogate error from page X to
page J by placing them in the session scope. There may be some
Thank you for the reply Robert,
Because saveErrors() signature requires the request object I assume that
the errors object have a request scope and I'm dealing with that
appropriately.
For the time being your solution is the one I'l have to use (which have
already been using) but to be
I am wondering if you can set validate=false on the
second mapping (Y)?
maybe because it is going through validation again?
sandeep
--- rob [EMAIL PROTECTED] wrote:
It would appear that you can not maintain saved
errors in the http
request across a forward to an action before
displaying it
Neither of the Actions use validation. The attribute is not even
defined in the struts-config.xml for the actions.
The actual struts-config.xml entries for the two actions are:
action path=/viewResource
type=gen.ViewResourceAction
name=ViewResourceForm
4 matches
Mail list logo
