On Wed, 13 Mar 2002, Porter, Roy wrote:
> Date: Wed, 13 Mar 2002 15:24:07 -0000
> From: "Porter, Roy" <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: 'Struts Developers List' <[EMAIL PROTECTED]>
> Subject: FormTag problem with VisualAge
>
> Whenever I get a new copy of the Struts Source, I have to go in and make the
> following change to the FormTag java code:
>
>
> >From doEndTag:
>
> Remove:
> pageContext.removeAttribute(Constants.BEAN_KEY,
> PageContext.REQUEST_SCOPE);
> pageContext.removeAttribute(Constants.FORM_KEY,
> PageContext.REQUEST_SCOPE);
> Add:
> pageContext.getRequest().removeAttribute(Constants.BEAN_KEY);
> pageContext.getRequest().removeAttribute(Constants.FORM_KEY);
>
> I realise this is probably only affecting VisualAge (& possibly WebSphere
> ?), but could this change be made to the base code ?
>
I'm a little hesitant to do this, because the JSP spec does *not* require
that they do exactly the same thing. It's legal for a container to cache
the current state of the attributes and then sync up at certain defined
points.
To be fair, the JSP code that WebSphere is using for this originally came
from a bug in Tomcat 3.0, which incorrectly disallowed removing attributes
from request scope. That was more than a couple of years ago, though;
it's really time for IBM to have fixed this by now.
> Roy.
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
