Hi Steve,

Do you have a stack trace for the error? It will tell us which Struts class
the exception is being thrown from, we can then figure out how to solve it
for your container.

Jon.

-----Original Message-----
From: Ritter, Steve [mailto:[EMAIL PROTECTED]] 
Sent: 06 June 2001 15:28
To: '[EMAIL PROTECTED]'
Subject: RE: Need help with "Can't remove attributes from request scope" p
robl em.

Hi Jon, 

Thanks for the reply, I tried the recommended change to the source code and
still I get the same error.

I've sent an email to my vendor's support group, in lieu of that is there
anything else you would suggest?

--Steve

> -----Original Message-----
> From: Jon.Ridgway [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 06, 2001 2:10 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Need help with "Can't remove attributes from 
> request scope"
> p robl em.
> 
> 
> Hi Steve,
> 
> Try editing org.apache.struts.taglib.FormTag.doEndTag as follows : 
> 
>  
> // Remove the page scope attributes we created
> pageContext.getRequest().removeAttribute(Constants.BEAN_KEY);
> pageContext.getRequest().removeAttribute(Constants.FORM_KEY);
> 
> Jon.
> 
> -----Original Message-----
> From: Ritter, Steve [mailto:[EMAIL PROTECTED]] 
> Sent: 05 June 2001 20:03
> To: '[EMAIL PROTECTED]'
> Subject: Need help with "Can't remove attributes from request 
> scope" probl
> em.
> 
> Hi everyone,
> 
> We ran into a problem running b2/b3 on Servletmill that 
> others seem to have
> hit with WTE.  It occurs when trying to access the login page from
> struts-example, you get an IllegalArgumentException with 
> message "Can't
> remove attributes from request scope".  It seems this thread 
> discusses a
> potential HACK to "fix" the issue.
> 
> http://www.mail-archive.com/struts-user@jakarta.apache.org/msg
08663.html

The top-most posting in this thread indicates bugzilla id 932 which I
checked into:

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=932

So, according to Craig the bug is really in the servlet container and it
would seem that my servlet container has the very same prolem.  What is
suggested work around for this?  Can someone help me with some more details
in the event that I need to speak with my container vendor?

--Steve

Reply via email to