So, it seems this is a classic JSF gotcha - backing bean calls are made more than once (to a Seam component in this case). Once for the render, and then during the next web request, to reconstruct the component tree. The component is already destroyed by the time the second call is made, so a new instance of the component is created. This second instance will perform all kinds of bijection & business processing mischief, like killing off the @DataModel
For immediate needs, I could outject nextPage/previousPage Booleans so that the component is never referenced from the view for value bindings. As well as this having been a problem for me within Seam, I also see Seam as being ideally placed to solve this more general JSF issue. Would it be possible to extend the life of Seam components to cover the needed calls for component tree rebuilding? Looks like people in the straight managed bean environment are resorting to session scope backing beans, as request won't work and there's few alternatives, but Seam could be more clever. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933752#3933752 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3933752 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
