the lifespan of a request?

[Per Jorgen Walstrom]

hello,
I have the following actions

    <action path="/listChannels"
            type="ChannelListAdminAction"
            name="channellistForm"
            scope="request">
        <forward name="forward" redirect="true" path="/channellist.jsp"/>
    </action>
    <action path="/saveChannel"
            type="ChannelAction"
            name="channelForm"
            scope="session"
            input="/channel.jsp"
            parameter="method">
        <forward name="errors" path="/listChannels.do"/>
    </action>
  

I call listDocuments.do and the resulting jsp-page lists some "channels" where it is possible to delete a chosen channel, by following a link to http://localhost:8080/saveChannel.do?method=delete&id=40278. ChannelAction extends DispatchAction. Now, in ChannelAction, I do a check if the channel can be deleted. If not, I do the following:

request.setAttribute(Globals.ERROR_KEY, ae);
return mapping.findForward("errors");

The thing is now, that listChannels.do does not seem to be able to display the errors. The attribute is gone from the request. Why is this? I have only done one request, as far as I can see. Does Struts consider going to another Action to be a completely new request?

any help would be appreciated!

cheers,
pj

[David Ulicny]

Request is valid only for request time. If you want have data longer use another scope - session for example. I'm not sure how struts handle with request, but it is possible that after forward it creates new request.

[Stefan Evans]

Request attributes last for the scope of a request.
Forward/include happens on the same request.
A redirect sends a response telling the browser to send a new request.

So request attributes are retained over a forward/include
Request attributes are lost if you issue a redirect.

Looking at your actionforward for /listChannels:
<forward name="forward" redirect="true" path="/channellist.jsp"/>

Solutions
- put the attribute in session
- don't redirect on a "listChannels" request