DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34511>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34511 Summary: html:select saves itself in page scope rather than request scope Product: Struts Version: 1.2.4 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Custom Tags AssignedTo: dev@struts.apache.org ReportedBy: [EMAIL PROTECTED] The <html:select> tag saves a reference to itself in the page scope so that a nested <html:optionsCollection> or <html:option> or <html:options> tag will know how to retrieve it to do some processing. This presents a problem when the <html:options> tag is embedded in an included jsp such as through a <tiles:insert>. Would it be better practice to save the select object in request scope this way the options object would still know how to find the enclosing select object across jsp fragment pages? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]