Daniel,
How did you convince Websphere to use your updated version? 
I tried adding the updated FormTag but it's not being picked up.  I know it's
a classpath issue, but I can't figure it out.  From my
experiments, it looks like Websphere 3.5.3 uses an old version of struts internally --
If I put the updated jar file on the classpath at one level, it complains because of
"Cannot find message resources under key" but if I put it on the webapp's
classpath or remove it entirely, I'm back to the
"cant remove Attributes from request scope" error [Any chance we could
get the apostrophe back in that error message?]
Thanks,
Roxie
-----Original Message-----
From: Daniel Benzimra-Ceuppens [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 6:40 AM
To: Jon.Ridgway; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Form tag problem in VAJ 3.5.3 WTE with 1.0b2

Yes sir,
 
It does work, also under WAS 3.5.3.  Thanks alot: you allow me to use Struts 1.0b2 !
 
Daniel.
-----Original Message-----
From: Jon.Ridgway [mailto:[EMAIL PROTECTED]]
Sent: Wed, 30 May, 2001 12:58
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Form tag problem in VAJ 3.5.3 WTE with 1.0b2

Hi All,

 

Opps and apologies, adding a getRequest may resolve this little one, I tried 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);

 

And when I called :

 

Object o = pageContext.getRequest().getAttribute(Constants.BEAN_KEY);

 

Got null as I would expect.

 

Jon.

 

Reply via email to