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 Cannot find bean in any scope in included JSP Summary: Cannot find bean in any scope in included JSP Product: Struts Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: Custom Tags AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This bug occurs after I upgraded from Struts 1.1 b2 to 1.1 RC, then to 1.1 Nightly build 3-20 and 3-25 because I need the nightly build to fix the problem in 1.1 RC (Bug # 18066). Apparently, the nested:define issue in Bug # 18066 is resolved in the nightly builds. However, I ran into the exception below: javax.servlet.jsp.JspException: Cannot find bean OverviewForm in any scope at org.apache.struts.util.RequestUtils.lookup(RequestUtils.java:863) at org.apache.struts.taglib.logic.IterateTag.doStartTag (IterateTag.java:277) at org.apache.struts.taglib.nested.logic.NestedIterateTag.doStartTag (NestedIterateTag.java:116) at /jsp/overview/Borrowers.jsp._jspService (/jsp/overview/Borrowers.jsp.java:381) (JSP page line 23) After spending sometime on the problem, I noticed that the exception occured when the collection or bean using nested tag is referenced inside a included jsp page. If I move all included jsp into the main jsp (yes, I have a long jsp page), the problem seems to go away, meaning that the page can be displayed. However, the page won't be able to capture the newly entered information online, that is I cannot save the new information into database. Struts seems to not be able to identify the session information inside the nested tags. My trace shows the session keeps the old information even I change it online, so it simply saves in the old information. We heavily use nested tag in our application. This release has caused a major issue for us. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
