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=18343>. 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=18343 Nested tags cannot find bean in any scope in included JSP ------- Additional Comments From [EMAIL PROTECTED] 2003-04-01 13:00 ------- Try this... ...remove all the name attributes. The nested tags have always managed this aspect for free. A nested tag inside an iterate will naturally pick up on what the parent is setting. For example, in BranchAdmin.jsp the first few nested tags can become... <html:form action="/sysadmin/branchAdmin.do" enctype="application/x-www-form-urlencoded"> <nested:iterate property="branches" indexId="branchIndex"> <nested:define id="srchBranchId" property="branchId" /> <nested:notEqual property="isNew" value="true" > .... ...all the name attributes aren't required, because the nested tags know their position in life, and what they're nesting against. This could be the problem in itself. Some people asked for the ability to be able to specify a different bean in a parent tag (like an iterate), and have their children reference that new reference. This means, that while you can view all the data, it wont relate to the same root bean, and hence the server will not be updated correctly. If you look at other examples of nested tags, you'll notice the name attribute isn't supplied in the tags. It is true that with the big update of the tags to get Tomcat 4.1.18 working, the behaviour has changed to make use of a supplied name attribute. The older tags simply ignored the supploed name. It's on my cards to update the package documentation with more complete description of these changes. In the mean time, can you try removing all of the name attributes (for all nested tags except for any <nested:root> tags that are starting the nest for the tags), and give it another spin. Hopefully the problems will disappear. If not, get back to me and I'll go about setting up a complete test app to work against your JSP's markup. This an OK plan of action?... With any luck, it will simply be a case of the scenario outlined above, and all our woes will disappear... :P --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
