[ http://issues.apache.org/struts/browse/STR-279?page=all ]
Don Brown closed STR-279:
-------------------------
Resolution: Not A Problem
> Form tag does not work (generate Exception "cant remove attribute")
> -------------------------------------------------------------------
>
> Key: STR-279
> URL: http://issues.apache.org/struts/browse/STR-279
> 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
> http://www7.software.ibm.com/vad.nsf/Data/Document2558), 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 com.ibm.ivj.jsp.jasper; 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
> ApplicationResources.properties - 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 [email protected]
> (msg01242.html) that a recent change in
> org.apache.struts.taglib.html.FormTag.java 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:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
