#1 Can be implemented using a Hibernate Filter, which we have special support for in Seam.
#2 or #3 Can be implemented using multiple SessionFactories, or EntityManagerFactories. You would need to do a little trick when the user logs in, to map the SessionFactory you are interested in for this user to the context variable that your Seam-managed persistence context uses. But this is trivial to implement and will work well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049123#4049123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049123
No, its not. Seam keeps the conversation id in the UIViewRoot, so if you want to change the conversation context from a partial render, you would need to render the whole f:view (which is not really a partial render!).
This is definitely a limitation of the current design (closely related to our limitation that there may be only one conversation per page), but I believe it's perfectly fine for almost all purposes.
However, this should be documented, since it is not at all intuitive unless you happen to know how Seam in implemented. So please create in issue in JIRA, asking for documentation, and assign it to me. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049118#4049118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049118