On 9/15/05, Holshausen, Ron <[EMAIL PROTECTED]> wrote: > > Hi Geeta, > > Just to let you know that one of the changes that was made to the JSF > spec was to integrate the JSTL and JSF, so you could use c:forEach with > JSF UI components. So using JSTL is still ok, I do. And I think it will > be around for a while.
Ron's comments with respect to JSF 1.2 and JSTL interoperability are correct ... but they only address part of the overall issue. If all you care about is *rendering* output based on an iteration over a collection of model tier objects, the JSF 1.2 integration strategy will work fine. If, on the other hand, you want to have *input* fields inside your <c:forEach> tag, you're going to run into more problems. The right answer there is to use an outer "grouping" component (such as, but not limited to, <h:dataTable>) that deals with the iteration issues during the postback processing phases (Apply Request Values through Process Validations) as well as during rendering. Solutions based on JSTL *only* work during rendering, because the JSP page itself is *not* involved in actually performing a postback. Or, if you want a shorter version of the answer, depending on <c:forEach> is still going to limit what you can actually do inside the iterations, even in a JSF 1.2 world. The right answer is smarter components that do iterations for you, not forcing the page developer to manually code iteration loops. Craig
