| Anonymous | Login | Signup for a new account | 12-18-2025 06:59 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002804 | [Resin] | minor | always | 07-24-08 10:39 | 08-21-08 09:22 | ||||
| Reporter | bregnvig | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.1.7 | Product Version | 3.1.6 | ||||
| Product Build | |||||||||
| Summary | 0002804: c:forEach deletes the request scoped variable | ||||||||
| Description |
In a struts action I set the following: request.setAttribute("child", child); In my JSP I can now use my child object using ${child.firstName}. But after I've executed a forEach with the following statement: <c:forEach var="child" items="${pageScope.children}"> .... </c:forEach> I can no longer use ${child.firstName} as the attribute has been removed. The JSTL spec says: Name of the exported scoped variable for the current item of the iteration. This scoped variable has nested visibility. Its type depends on the object of the underlying collection. So I assume the forEach should not have removed the request scoped attribute only the page scope attribute from the forEach loop. |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | It works as expected on 3.0.x | ||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |