DO NOT REPLY [Bug 18185] New: - nested:present masks exceptions thrown by property getter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18185. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18185 nested:present masks exceptions thrown by property getter Summary: nested:present masks exceptions thrown by property getter Product: Struts Version: 1.1 RC1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Custom Tags AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When nested:present checks if a bean property is null or not any exception thrown by the bean's property getter is ignored and the tag simply evaluates to false; instead it should rethrow the exception (wrapped in a runtime exception, probably). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18186] New: - html:radio idName attribute doesn't work in resin 2.1.6
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18186.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18186
html:radio idName attribute doesn't work in resin 2.1.6
Summary: html:radio idName attribute doesn't work in resin 2.1.6
Product: Struts
Version: 1.1 RC1
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Custom Tags
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
## Test this code in resin 2.1.6
--test-radio.jsp
%@ taglib uri=/WEB-INF/struts-bean.tld prefix=bean %
%@ taglib uri=/WEB-INF/struts-html.tld prefix=html %
%@ taglib uri=/WEB-INF/struts-logic.tld prefix=logic %
%@ taglib uri=/WEB-INF/struts-nested.tld prefix=nested %
%@ page import=java.util.*%
%@ page import=org.apache.struts.util.*%
%
List l = new ArrayList( 5);
request.setAttribute( l, l);
for( int i = 0; i 5; i++) {
LabelValueBean lvb = new LabelValueBean( String.valueOf( i), labelxx +
i);
l.add( lvb);
}
%
html
head
title
test_radio
/title
/head
body bgcolor=#ff
html:form action=/test_radio
brbr
logic:iterate id=lvb name=l type=org.apache.struts.util.LabelValueBean
html:radio idName=lvb value=value property=x/ bean:write
name=lvb property=label/br
/logic:iterate
input type=submit name=Submit value=Submit
input type=reset value=Reset
/html:form
/body
/html
-- struts-config.xml
?xml version=1.0 encoding=UTF-8?
!DOCTYPE struts-config PUBLIC -//Apache Software Foundation//DTD Struts
Configuration 1.1//EN http://jakarta.apache.org/struts/dtds/struts-
config_1_1.dtd
struts-config
form-beans
form-bean name=testRadioForm
type=org.apache.struts.action.DynaActionForm dynamic=true
form-property name=x type=java.lang.String /
/form-bean
/form-beans
action-mappings
action name=testRadioForm forward=/test_radio.jsp path=/test_radio /
/action-mappings
controller processorClass=org.apache.struts.tiles.TilesRequestProcessor /
message-resources parameter=resources.application /
plug-in className=org.apache.struts.tiles.TilesPlugin
set-property value=/WEB-INF/tiles-defs.xml property=definitions-
config /
set-property value=true property=moduleAware /
set-property value=true property=definitions-parser-validate /
/plug-in
plug-in className=org.apache.struts.validator.ValidatorPlugIn
set-property value=/WEB-INF/validator-rules.xml,/WEB-INF/validation.xml
property=pathnames /
/plug-in
/struts-config
The problem happens when the container is going to render the second radio
button. It looses the value of the value attribute of RadioTag. The problem
is due to:
//Tomcat code
org.apache.struts.taglib.html.RadioTag _jspx_th_html_radio_0 =
(org.apache.struts.taglib.html.RadioTag)
_jspx_tagPool_html_radio_value_property_idName.get
(org.apache.struts.taglib.html.RadioTag.class);
_jspx_th_html_radio_0.setPageContext(pageContext);
_jspx_th_html_radio_0.setParent(_jspx_th_logic_iterate_0);
_jspx_th_html_radio_0.setIdName(lvb);
_jspx_th_html_radio_0.setValue(value);
_jspx_th_html_radio_0.setProperty(x);
//Resin code
if (_jsp_tag2 == null) {
_jsp_tag2 = new org.apache.struts.taglib.html.RadioTag();
_jsp_tag2.setPageContext(pageContext);
_jsp_tag2.setParent(_jsp_tag1);
_jsp_tag2.setProperty(x);
_jsp_tag2.setValue(value);
_jsp_tag2.setIdName(lvb);
}
Look in tomcat the radio tag is initialized every iterator but in resin the tag
is initialized first time, so if the RadioTag changes the value of the value
attribute, these changes remain for the rest of iterations.
I did search in the JSP Specification to find if it is a resin error or struts
error. I found the folowing:
All properties of a tag handler instance exposed as attributes will be
initialized by the container using the appropriate setter methods before the
instance can be used to perform the action methods. It is the responsibility of
the JSP container to invoke the appropriate setter methods to initialize these
properties. It is the responsability of user code, be it scriptlets, JavaBeans
code, OR CODE INSIDE CUSTOM TAGS, TO NOT INVOKE THESE SETTER METHODS, AS DOING
OTHERWISE WOULD INTERFERE WITH THE CONTAINER KNOWLEDGE.
The setter methods that should be used when assigning a value to an attribute
of a custom action are determined by using the JavaBeans introspector on the tag
handler class, then use the setter method associated with the property that has
the same name as the attribute in question. An implication (unclear in the
JavaBeans specification) is that there is only one setter per property.
Unspecified attributes/properties should not be set (using a setter method).
ONCE PROPERLY SET, ALL
DO NOT REPLY [Bug 18185] - nested:present masks exceptions thrown by property getter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18185. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18185 nested:present masks exceptions thrown by property getter [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 13:23 --- Sorry -- I entered this bug twice. *** This bug has been marked as a duplicate of 18187 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18187] - nested:present masks exceptions thrown by property getter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18187. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18187 nested:present masks exceptions thrown by property getter [EMAIL PROTECTED] changed: What|Removed |Added Summary|nested:present marks|nested:present masks |exceptions thrown by|exceptions thrown by |property getter |property getter --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 13:24 --- I'll get this right eventually. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16708] - I18N on ActionForwards
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16708. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16708 I18N on ActionForwards [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|--- |1.2 Family - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16117] - Html Link tag
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16117. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16117 Html Link tag [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|--- |1.2 Family --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 14:13 --- Marking for 1.2 family. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bugzilla queries
David Graham wrote: No. Currently, it looks like Martin thinks we should be using later and Ted thinks we should mark as unknown. I agree more with Martin on this issue. Actually, I was thinking that we couldn't make changes to the ticket or vote on it after it was closed this way, but I see now that we can. So, I'll go back to marking them RESOLVED LATER. While we are waiting on the final RC1 tickets, I'll start going through the 115 RESOLVED LATER tickets, weed out the ones that are obsolete, and see if we can make a roadmap out of the rest. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Interesting Bug Fact
I just did a quick bug search and roughly 35% of Struts' total bugs have been reported against the Custom Tags category. I think this highlights the difficulty of writing custom tags and supports a move to separate Struts distributions of Core and Custom Tags. David _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-struts/doc/userGuide dev_validator.xml
turner 2003/03/20 08:36:35 Modified:doc/faqs newbie.xml doc/userGuide dev_validator.xml Log: Added simpler example of using the requiredif validator test to dev_validator.xml, added faq on using requiredif to newbie.xml, also fixed syntax of more complicated example in dev_validator.xml to actually be correct (it was using things like fieldJoin instead of field-join. Revision ChangesPath 1.13 +63 -0 jakarta-struts/doc/faqs/newbie.xml Index: newbie.xml === RCS file: /home/cvs/jakarta-struts/doc/faqs/newbie.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- newbie.xml5 Feb 2003 04:23:20 - 1.12 +++ newbie.xml20 Mar 2003 16:36:34 - 1.13 @@ -5,6 +5,7 @@ authorJames Holmes/author authorCraig R. McClanahan/author authorEdgar Dollin/author +authorJames Turner/author titleNewbie FAQ - Apache Struts/title /properties body @@ -110,6 +111,10 @@ a href=#prepopulateHow can I prepopulate a form?/a /li +li +a href=#requiredifCan you give me a simple example of using the requiredif Validator rule?/a +/li + /ul p @@ -699,6 +704,64 @@ instead of calling your processing action./li /ul +/section + +section href=requiredif + name=Can you give me a simple example of using the requiredif Validator rule? + pLet's assume you have a medical information form with three fields, sex, dateOfLastMamogram, and testResult. + If sex is 'f' or 'F', dateOfLastMamogram is required. If dateOfLastMamogram is not blank, testResult is required. + The entry in your validation.xml file would look like this: + /p + pre +lt;form name=medicalStatusFormgt; + +lt;field +property=dateOfLastMamogram depends=requiredifgt; + lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt; + lt;vargt; +lt;var-namegt;field[0]lt;/var-namegt; +lt;var-valuegt;sexlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-test[0]lt;/var-namegt; +lt;var-valuegt;EQUALlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-value[0]lt;/var-namegt; +lt;var-valuegt;Flt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field[1]lt;/var-namegt; +lt;var-valuegt;sexlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-test[1]lt;/var-namegt; +lt;var-valuegt;EQUALlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-value[1]lt;/var-namegt; +lt;var-valuegt;flt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-joinlt;/var-namegt; +lt;var-valuegt;ORlt;/var-valuegt; + lt;/vargt; +lt;/fieldgt; + +lt;field +property=testResult depends=requiredifgt; + lt;arg0 key=medicalStatusForm.testResult.label/gt; + lt;vargt; +lt;var-namegt;field[0]lt;/var-namegt; +lt;var-valuegt;dateOfLastMamogramlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-test[0]lt;/var-namegt; +lt;var-valuegt;NOTNULLlt;/var-valuegt; + lt;/vargt; +lt;/fieldgt; +lt;/formgt; +/pre /section 1.30 +68 -12jakarta-struts/doc/userGuide/dev_validator.xml Index: dev_validator.xml === RCS file: /home/cvs/jakarta-struts/doc/userGuide/dev_validator.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- dev_validator.xml 19 Mar 2003 04:49:04 - 1.29 +++ dev_validator.xml 20 Mar 2003 16:36:34 - 1.30 @@ -502,8 +502,65 @@ non-null and field Y equals 'male'. /p + pLet's assume you have a medical information form with three fields, sex, dateOfLastMamogram, and testResult. + If sex is 'f' or 'F', dateOfLastMamogram is required. If dateOfLastMamogram is not blank, testResult is required. + The entry in your validation.xml file would look like this: + /p + pre +lt;form name=medicalStatusFormgt; + +lt;field +property=dateOfLastMamogram depends=requiredifgt; + lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt; + lt;vargt; +lt;var-namegt;field[0]lt;/var-namegt; +lt;var-valuegt;sexlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-test[0]lt;/var-namegt; +lt;var-valuegt;EQUALlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-value[0]lt;/var-namegt; +lt;var-valuegt;Flt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field[1]lt;/var-namegt; +lt;var-valuegt;sexlt;/var-valuegt; + lt;/vargt; + lt;vargt; +lt;var-namegt;field-test[1]lt;/var-namegt; +lt;var-valuegt;EQUALlt;/var-valuegt; + lt;/vargt; +
cvs commit: jakarta-struts/doc/userGuide dev_validator.xml
turner 2003/03/20 08:42:12 Modified:doc/faqs newbie.xml doc/userGuide dev_validator.xml Log: Fixed new examples to use camelCase as per nightly build change made by David Graham, and changed examples because discussing female anatomy evidently made him blush :-) Revision ChangesPath 1.14 +11 -11jakarta-struts/doc/faqs/newbie.xml Index: newbie.xml === RCS file: /home/cvs/jakarta-struts/doc/faqs/newbie.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- newbie.xml20 Mar 2003 16:36:34 - 1.13 +++ newbie.xml20 Mar 2003 16:42:11 - 1.14 @@ -708,26 +708,26 @@ section href=requiredif name=Can you give me a simple example of using the requiredif Validator rule? - pLet's assume you have a medical information form with three fields, sex, dateOfLastMamogram, and testResult. - If sex is 'f' or 'F', dateOfLastMamogram is required. If dateOfLastMamogram is not blank, testResult is required. + pLet's assume you have a medical information form with three fields, sex, pregnancyTest, and testResult. + If sex is 'f' or 'F', pregnancyTest is required. If pregnancyTest is not blank, testResult is required. The entry in your validation.xml file would look like this: /p pre lt;form name=medicalStatusFormgt; lt;field -property=dateOfLastMamogram depends=requiredifgt; - lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt; +property=pregnancyTest depends=requiredifgt; + lt;arg0 key=medicalStatusForm.pregnancyTest.label/gt; lt;vargt; lt;var-namegt;field[0]lt;/var-namegt; lt;var-valuegt;sexlt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-test[0]lt;/var-namegt; +lt;var-namegt;fieldTest[0]lt;/var-namegt; lt;var-valuegt;EQUALlt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-value[0]lt;/var-namegt; +lt;var-namegt;fieldValue[0]lt;/var-namegt; lt;var-valuegt;Flt;/var-valuegt; lt;/vargt; lt;vargt; @@ -735,15 +735,15 @@ lt;var-valuegt;sexlt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-test[1]lt;/var-namegt; +lt;var-namegt;fieldTest[1]lt;/var-namegt; lt;var-valuegt;EQUALlt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-value[1]lt;/var-namegt; +lt;var-namegt;fieldValue[1]lt;/var-namegt; lt;var-valuegt;flt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-joinlt;/var-namegt; +lt;var-namegt;fieldJoinlt;/var-namegt; lt;var-valuegt;ORlt;/var-valuegt; lt;/vargt; lt;/fieldgt; @@ -753,10 +753,10 @@ lt;arg0 key=medicalStatusForm.testResult.label/gt; lt;vargt; lt;var-namegt;field[0]lt;/var-namegt; -lt;var-valuegt;dateOfLastMamogramlt;/var-valuegt; +lt;var-valuegt;pregnancyTestlt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-test[0]lt;/var-namegt; +lt;var-namegt;fieldTest[0]lt;/var-namegt; lt;var-valuegt;NOTNULLlt;/var-valuegt; lt;/vargt; lt;/fieldgt; 1.31 +20 -20jakarta-struts/doc/userGuide/dev_validator.xml Index: dev_validator.xml === RCS file: /home/cvs/jakarta-struts/doc/userGuide/dev_validator.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- dev_validator.xml 20 Mar 2003 16:36:34 - 1.30 +++ dev_validator.xml 20 Mar 2003 16:42:11 - 1.31 @@ -502,26 +502,26 @@ non-null and field Y equals 'male'. /p - pLet's assume you have a medical information form with three fields, sex, dateOfLastMamogram, and testResult. - If sex is 'f' or 'F', dateOfLastMamogram is required. If dateOfLastMamogram is not blank, testResult is required. + pLet's assume you have a medical information form with three fields, sex, pregnancyTest, and testResult. + If sex is 'f' or 'F', pregnancyTest is required. If pregnancyTest is not blank, testResult is required. The entry in your validation.xml file would look like this: /p pre lt;form name=medicalStatusFormgt; lt;field -property=dateOfLastMamogram depends=requiredifgt; - lt;arg0 key=medicalStatusForm.dateOfLastMamogram.label/gt; +property=pregnancyTest depends=requiredifgt; + lt;arg0 key=medicalStatusForm.pregnancyTest.label/gt; lt;vargt; lt;var-namegt;field[0]lt;/var-namegt; lt;var-valuegt;sexlt;/var-valuegt; lt;/vargt; lt;vargt; -lt;var-namegt;field-test[0]lt;/var-namegt; +lt;var-namegt;fieldTest[0]lt;/var-namegt; lt;var-valuegt;EQUALlt;/var-valuegt; lt;/vargt; lt;vargt; -
DO NOT REPLY [Bug 16708] - I18N on ActionForwards
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16708. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16708 I18N on ActionForwards --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 16:45 --- I have some reservations about this, and I'm sure we'll discuss this later, so I'm just adding myself to the CC for now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml
Modified:doc/faqs newbie.xml doc/userGuide dev_validator.xml Log: Fixed new examples to use camelCase as per nightly build change made by David Graham, and changed examples because discussing female anatomy evidently made him blush :-) Thanks for saving this to CVS for a permanent reminder :-). David _ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: jakarta-struts/doc/userGuide dev_validator.xml
On Thu, 2003-03-20 at 11:45, David Graham wrote: Modified:doc/faqs newbie.xml doc/userGuide dev_validator.xml Log: Fixed new examples to use camelCase as per nightly build change made by David Graham, and changed examples because discussing female anatomy evidently made him blush :-) Thanks for saving this to CVS for a permanent reminder :-). LOL!!! David _ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Mitchell Software Developer/Struts Evangelist http://www.open-tools.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Interesting Bug Fact
I would like to add an observation to this 'fact'. The tags have taken a huge hit due to the complexity tomcat added with 'pooled' tags. The pooling broke all the tags resulting in a high level of bug reporting. IMO it highlights the importance of the tag library to struts, at least until JSF is ready for prime time. Edgar -Original Message- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 10:09 AM To: '[EMAIL PROTECTED]' Subject: Interesting Bug Fact I just did a quick bug search and roughly 35% of Struts' total bugs have been reported against the Custom Tags category. I think this highlights the difficulty of writing custom tags and supports a move to separate Struts distributions of Core and Custom Tags. David _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16117] - Html Link tag
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16117. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16117 Html Link tag --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 17:27 --- I think that this should be closed as INVALID or WON'T FIX. It's obvious that using a redirect will bypass the controller. So appropriate measures should be taken. If we allow the link tag to figure out which module was meant to be used, then we would have to overhaul every tag in the distribution to do the same. I don't understand why you need to redirect instead of forward. The only workaround I can think of would be to use the SwitchAction, but then you'd be forwarding from that too. Comments? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18194] - Enhance MessageResources to enable several definitions for the same ServletContext attribute key
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18194. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18194 Enhance MessageResources to enable several definitions for the same ServletContext attribute key --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 18:15 --- Created an attachment (id=5451) Jar bundle of the source code - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Interesting Bug Fact
Would recommend a whitepaper/guidelines doc from the core tag developers, so that we have certain patterns to follow for future tag development... --- David Graham [EMAIL PROTECTED] wrote: It is a fact. You can do the math yourself to verify. Tomcat pooling did not break the tags; the tags were always in violation of the JSP spec. I did not point this out to imply that the tags were not important, only to show that they make up a huge amount of our effort and the difficulty of writing fully compliant tags. It would benefit Struts to move the tags to a separate distro (there should probably still be an all-in-one distro too). David From: Edgar P. Dollin [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Subject: RE: Interesting Bug Fact Date: Thu, 20 Mar 2003 12:07:28 -0500 I would like to add an observation to this 'fact'. The tags have taken a huge hit due to the complexity tomcat added with 'pooled' tags. The pooling broke all the tags resulting in a high level of bug reporting. IMO it highlights the importance of the tag library to struts, at least until JSF is ready for prime time. Edgar -Original Message- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 10:09 AM To: '[EMAIL PROTECTED]' Subject: Interesting Bug Fact I just did a quick bug search and roughly 35% of Struts' total bugs have been reported against the Custom Tags category. I think this highlights the difficulty of writing custom tags and supports a move to separate Struts distributions of Core and Custom Tags. David _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tiles insert tag was Re: cvs commit: jakarta-struts/src/share/org/apache/...
The ignore attribute did solve my problem in WAS 5.0. David No. The parent definition only declare the attributes relevant to the parent. A child (extending a parent) can add some new attributes. If an attribute is not used in a parent, you don't need to declare it. In your case, the attribute is used by the associated layout, but you want the layout to ignore it (to show nothing). Ok, I'll try the ignore attribute. The change to insert tag has been removed. It's strange that the error only occurs in WAS 5 and not Tomcat. Yes, this is strange. I have already seen this problem with a server replacing the empty string with a null reference. In fact, the generated jsp code doesn't set the attribute at all if the string is empty, so the attribute is set to null ;-(. It is a kind of optimization that have a side effect. Maybe the same happen with WAS 5. For me, this is a bug. Also, maybe there is an option in WAS 5 to avoid such thing ... Cedric Cedric David _ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Interesting Bug Fact
Can you explain why? Having the JSP tags in the Struts distro doesn't seem to hurt you if you don't use JSPs. David From: Nathan Bubna [EMAIL PROTECTED] Reply-To: Struts Developers List [EMAIL PROTECTED] To: Struts Developers List [EMAIL PROTECTED] Subject: Re: Interesting Bug Fact Date: Thu, 20 Mar 2003 12:50:34 -0800 David Graham said: ... It would benefit Struts to move the tags to a separate distro (there should probably still be an all-in-one distro too). ... It would also *greatly* please those of us who prefer to use Struts without using JSPs. Nathan Bubna [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Interesting Bug Fact
David said: Can you explain why? Having the JSP tags in the Struts distro doesn't seem to hurt you if you don't use JSPs. well, i'm assuming that releases of the Struts core library would no longer have to wait on fixes and upgrades to the JSP tags. it would also help in dispelling the seemingly frequent perception that Struts is just for those using JSPs. Nathan said: ... It would also *greatly* please those of us who prefer to use Struts without using JSPs. Nathan Bubna [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Interesting Bug Fact
well, i'm assuming that releases of the Struts core library would no longer have to wait on fixes and upgrades to the JSP tags. it would also help in dispelling the seemingly frequent perception that Struts is just for those using JSPs. Yep, I agree. David _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
select is missing a readonly attribute
The html:select tag is missing a readonly attribute - is this as designed? http://jakarta.apache.org/struts/userGuide/struts-html.html#select Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: select is missing a readonly attribute
The Struts tags support, either directly or indirectly, the attributes supported in the underlying HTML 4.01 specification. The HTML select tag doesn't specify a readonly attribute, so neither does Struts. -Original Message- From: Raible, Matt [mailto:[EMAIL PROTECTED] The html:select tag is missing a readonly attribute - is this as designed? http://jakarta.apache.org/struts/userGuide/struts-html.html#select - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: select is missing a readonly attribute
On Thu, 2003-03-20 at 18:57, Karr, David wrote: The Struts tags support, either directly or indirectly, the attributes supported in the underlying HTML 4.01 specification. The HTML select tag doesn't specify a readonly attribute, so neither does Struts. -Original Message- From: Raible, Matt [mailto:[EMAIL PROTECTED] The html:select tag is missing a readonly attribute - is this as designed? http://jakarta.apache.org/struts/userGuide/struts-html.html#select Take a look at using disabled=true (although not all browsers support it). -- James Mitchell Software Developer/Struts Evangelist http://www.open-tools.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bug 16108 - Why is ActionForm a base class rather than an interface?
I noticed bug 16108 is high priority and has been in for a month with no action. I was wondering if I could go and tackle it although it has been previously assigned to Ted. Any thoughts? I-Shen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Interesting Bug Fact
+1 The misconception many people have in associating struts exclusively with JSP gets rather 'irritating' at times. As you all know struts is so much more than just a bunch of tags. :-) For example the app Im working on doesnt use a single JSP, but is very much a struts based app - my view still looks to the actionform bean for its field values etc... The way I see it (especially now we have the jstl) the struts custom tags are just a 'bonus' convenience for those (the majority alas!) who use JSP for their view rendering. Ideally they would be just a (more explicitly) optional component or extension for JSP users , similar to what the VelocityStruts Toolkit (is that what its called?) does for struts users who use velocity. If seperating the controller and the view (it sounds good just saying it!) components of struts will result in more frequent 'struts core' releases then please do it! -Original Message- From: David Graham [mailto:[EMAIL PROTECTED] Sent: Friday, 21 March 2003 06:04 To: [EMAIL PROTECTED] Subject: Re: Interesting Bug Fact well, i'm assuming that releases of the Struts core library would no longer have to wait on fixes and upgrades to the JSP tags. it would also help in dispelling the seemingly frequent perception that Struts is just for those using JSPs. Yep, I agree. David _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
