Document behavior of s:link and @DataModel ------------------------------------------ Key: JBSEAM-1734 URL: http://jira.jboss.com/jira/browse/JBSEAM-1734 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Christian Bauer Priority: Blocker This behavior in the Hotel Booking example: @DataModel private List<Hotel> hotels; <h:dataTable id="hotels" value="#{hotels}" var="hot" rendered="#{hotels.rowCount>0}"> <s:link id="viewHotel" value="View Hotel" action="#{hotelBooking.selectHotel(hot)}"/> is becoming an FAQ. To counter that, explain in the documentation section about s:link that it can detect if it is rendered in a datatable, and that the URL for the resulting GET request (no form, no POST, no tree) contains a magic token that is used to pull the value out of the datamodel in the next INVOKE_APPLICATION phase. The whole procedure, from rendering, to request, to processing, needs to be explained in detail. Explain why it doesn't work in general and why you can't pass "objects as arguments" in EL across requests. Add this explanation also to the section in the "EL Enhancements" chapter, which already mentions this issue. Since this is the most important master/detail navigation concept, this is a blocker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira