Error Handling across multiple Actions

[Daniel McDade]

I am storing ActionError objects (under the Globals.ERROR_KEY) in Action1 and then forwarding to Action2 for processing, but I'm then getting an JspException saying the 'error' bean cannot be found in any scope. When Action2 runs, are the error objects in the original request overwritten or erased?

Can someone help me out in diagnosing the issue. This is using Struts 1.1

In my jsp, I'm accessing the collection as follows:

<logic:messagesPresent>
      <ul>
<html:messages id="error">
 <li class="errorhighlightbold"><bean:write name="error" /></li>
</html:messages>
      </ul>   
      </logic:messagesPresent>

Thanks for any help,
Daniel

[Merrill Higginson]

Originally posted by Daniel McDade:
When Action2 runs, are the error objects in the original request overwritten or erased?

Yes, they are. Struts cleans them out for each new action. That's one of the disadvantages of "action chaining". You will have to come up with some other way of passing messages from one action to another, such as storing them under a different key in the request and then having the second action retrieve them under that key and rewriting them using the saveErrors method.

[Daniel McDade]

Originally posted by Merrill Higginson:

Yes, they are. Struts cleans them out for each new action. That's one of the disadvantages of "action chaining". You will have to come up with some other way of passing messages from one action to another, such as storing them under a different key in the request and then having the second action retrieve them under that key and rewriting them using the saveErrors method.

Would the code to retreive those stored ActionError objects look something like this?

 
ActionErrors errs = (ActionErrors) request.getAttribute(Info.Key.MAIN_ERRORS);
 
        if(errs != null && !errs.isEmpty()) {
              saveErrors(request, errs);
        }
 

[Merrill Higginson]

Yes, that looks good.