Within a conversation, this kind of code is unnecessary, because you can used a conversation-scoped extended persistence context. But if you want to pass an object from one conversation to another, you have to do something like this.
One alternative approach is instead of passing the entity object around, just pass the id in a request parameter and use something like the ManagedEntity component (in Seam CVS) to auto-load the entity instance and expose it via a context variable. I love this approach and the new Seam crud framework will use this heavily. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974003#3974003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974003 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
