What do you mean by initializing the parameter in the first place ? isn't that what the page parameter does ? I'm a seam newbie having a similar problem, if I select an entity from a h:dataTable using <s:link id="editUser" action="#{userSearch.editUser(user)}" propagation="join" >Edit</s:link> then display the create/update form, it displays creation form, if I manually set in the url the " userId " parameter then it shows the update form, even if I leave page, and come back again using conversation begin, it still shows update page with old selected entity, until I hit update or delete, I also have <page> | <restrict>#{identity.loggedIn}</restrict> | <param name="userId" value="#{userHome.id}" converterId="javax.faces.Long" /> | <begin-conversation join="true" /> | <navigation from-action="#{userHome.persist}"> | <end-conversation /> | <redirect view-id="/registered.xhtml"> | <param name="userId" value="#{userHome.id}" /> | </redirect> | </navigation> | <navigation from-action="#{userHome.update}"> | <end-conversation /> | <redirect view-id="/registered.xhtml"> | <param name="userId" value="#{userHome.id}" converterId="javax.faces.Long" /> | </redirect> | </navigation> | </page> ... if I select one entity on the dataTable, and the form displays creation form, with already filled in fields of selected entity, and press create, it throws lots of exceptions of null values for not-null fields wich are not handled by seam, warning me not to have two phase listeners, wich I don't. We kind of need some further examples on documentation about using Home objects, that would be nice, they seem to rule, if they work of course. I'm guessing we have similar problems propagating id's to home objects, if page parameters in pages.xml does not do this, then where do we have to ? A Seam Newbie wandering for enlightenment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020886#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...