>From: "Sri Sankaran" <[EMAIL PROTECTED]> >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > >You haven't given enough information below (seems like a continuation of = >some previous thread). > >I *think* what you are trying to do is go "forward" from one action to = >another [*] but before so doing removing a attribute from the request. = >If so, some obvious checks would be > > - ensure that the request.removeAttribute(...) *is* being > invoked > - ensure that there isn't some logic in your admin action > whose role is to add one of these objects into the=20 > request Sri: Thanks much for your reply. You are right, perhaps I omitted to state completely what I was/am trying to have happen. Basically I have an application where there's a master page .. (I mean "master" in the master/details sense). The user clicks on ONE of the items displayed in the master, and goes into a task loop where he or she might spend several iterations operating on the item they are dealing with. This dispatches to several actions, queries, updates etc. When they are done, they "close" the item, and at that point, I want to go to the "master" page again.
Now .. one could argue that the master jsp is what I should merely "forward" to from one of the details panel's "close" action, but I really want the "view" action of the "master" page executed.. (since this view action queries the database etc. and composes the view of the master page). Forwarding to the master jsp from the detail would mean that I would need to construct and set up the request and session attributes for the master page "in" the close action of the item, which just doesn't seem right to me. So I thought.. hmm.. it should be easy to have a "goback" action on the detail that dispatches to the "view" action on the master. Is that not the right way to be thinking about this? Does it make sense now? I have verified that request.removeAttribute() is being called. (I can step past it.. correctly). Weird thing is that I notice in struts the "same" request object is what struts uses.. but at some point it dispatches to my container's dispatcher.. so I'm wondering now if this is really not a problem with struts so much as the container (unfortunately it behaves like this in tomcat too). Any thoughts on what I might check next? Your suggestion about checking if something is not adding the attribute I'm trying to remove is a good one. I don't think so.. but I'll double check. >Sri >[*] Check out the archives for various threads on action-chaining. It's = >a slippery slope Why? Is this not a good/blessed way of doing things? Just curious to learn the right idioms. Thanks again. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
