struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Don Brown (JIRA)" <>
Subject [jira] Closed: (STR-279) Form tag does not work (generate Exception "cant remove attribute")
Date Fri, 28 Apr 2006 05:06:19 GMT
     [ ]
Don Brown closed STR-279:

    Resolution: Not A Problem

> Form tag does not work (generate Exception "cant remove attribute")
> -------------------------------------------------------------------
>          Key: STR-279
>          URL:
>      Project: Struts Action 1
>         Type: Bug

>   Components: Taglibs
>     Versions: 1.0 Final
>  Environment: Operating System: All
> Platform: PC
>     Reporter: arenaud
>     Assignee: Craig McClanahan
>  Attachments: FormTag.doEndTag.txt
> After installing Struts on VisualAge 3.5.3 (Websphere Test Engine), if you try 
> to use some examples (Struts' or the one documented in Kyle Brown article at 
>, you will run into three 
> problems:
> - the first one, which is more of IBM concern, is the webapp.xsl used to convert 
> web.xml to example.webapp: running Xalan on it won't produce a workable solution 
> because the "jsp" section (wrongly named "jsp11") of the output tries to use 
> org.apache.jasper instead of; pasting the relevant 
> section of WTE default_app.webapp will do the trick...
> - the second one is trivial and I admit more of the concern of Kyle Brown: the 
> resources strings pointed to in his index.jsp (like index.title) do not exist in 
> - you have to add them manually (no comment...); 
> admitedly Struts own example does not suffer from that glaring bug...
> - the third one is the reason why we do post this bug report here: May 2nd 2001, 
> Nick Chalko (thanks!) posted on 
> (msg01242.html) that a recent change in 
> introduced a bug that will result in 
> an Exception ("cant -SIC- remove attribute") on any page with a "form" tag 
> (that's about 50% of any Website pages...): we don't know if that bug is only on 
> WTE/Websphere (if it is, IBM looks bad too...) or shows on standard Apache also; 
> either case, our point is that this should have been fixed long ago in the 1.0 
> final release dated 45 days later (June 16th), but was still present in 
> yesternight build (July 8th)... - manually changing the source code 
> (REQUEST_SCOPE to PAGE_SCOPE) from an obvious bug is not our idea of fun, 
> especially when you only try to evaluate a product...
> After a day of install, we will finally be able to actually DO something with 
> this...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message