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 request Sri [*] Check out the archives for various threads on action-chaining. It's a slippery slope -----Original Message----- From: Sundar Narasimhan [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 11:53 PM To: [EMAIL PROTECTED] Subject: Q: forwarding to another action .. Hi, I finally figured out that the problem w/ what I was trying to do was that the "back" forward didn't have the ".do". Once I included the .do things seem to work. (i.e. I can have my "compose", "save" etc. actions forward back to the master action in certain cases). <forward name="back" path="/admin.do"> </forward> However I now have another problem. I'd like to make sure that a certain request.attribute is removed when I go back to the master form. So in the above action I do a request.removeAttribute("someName"); But surprisingly I find that in the admin action this attribute is NOT removed. It's almost as though the "someName" attribute is saved and restored when I forward through "back". Why is this happening? I would have that the life-cycle of a "request" remains the same.. and struts wouldn't muck with it behind my back.. Any help will be much appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
