I wouldn't advise exposing entities as Seam components. I find it much neater
to manage through a CONVERSATION scoped bean (be it a Seam JavaBean or a SFSB)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054168#4054168
Reply to the post :
http://www.jboss.
Never mind - it looks like (after reviewing in detail the documentation) that
conversation is not really a good scope for entities. Instead, it looks like a
solution based on private state in an SFSB and using the manager pattern
(@Unwrap) may be a better way of doing this.
Thanks,
Brad Smith
