Event Scope Example: In Request x the user visits the page which references an outjected DataModel initialized by a Factory method. The user then clicks on a link (e.g. a detail view for a particular entity) at their leisure. In Request x + 1the state is lost and so information (e.g. entity id) must be propogated using a request parameter to allow the detail to be displayed Page Scope example: In Request x the user visits the page which references an outjected DataModel initialized by a Factory method. The user then clicks on a link (e.g. a detail view for a particular entity) at their leisure. In Request x + 1the state (of the datamodel at least) is still present in the page scope. The row clicked can then be retrieved using e.g. DataModelSelection This is why in the manual it says PAGE scope allows easy implementation of clickable lists. Though LIEs can occur if you work directly with the PAGE scope object in a further conversation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971038#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...