tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48616] Struts 1.2 and bean:define tag throws jsp 1.1 regression exception
Date Sun, 14 Feb 2010 11:54:43 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48616

--- Comment #16 from DSEyers <dseyers@ntlworld.com> 2010-02-14 11:54:39 UTC ---
The page mentioned contridicts itself:
http://struts.apache.org/1.2.8/userGuide/struts-bean.html#define

*.  Unconditionally creates (or replaces) a bean under the specified identifier
and
*.  USAGE NOTE - There is a restriction in the JSP 1.1 Specification that
disallows using the same value for an id  attribute more than once in a single
JSP page. Therefore, you will not be able to use <bean:define> for the same
bean name more than once in a single page

I think if you are no longer going to allow a variable to be overwritten, then
add a environment variable so we can turn the old behaviour on.

For us there is to many pages to change and would make the page hard to code
using dozens of variables...

The comment about checking am not quite getting as one variable defined you
can't use again:
<c:if test="${true}">
   <bean:define id="configurationExists" toScope="request" value="0"/>
</c:if>
<c:if test="${true}">
   <bean:define id="configurationExists" toScope="request" value="1"/>
</c:if>

My personal view is you should be able to overwrite a variable.  You could then
mention scope, but thats the whole page, not block of code.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message