[jboss-user] [JBoss Seam] - Re: Seam & clustering
"[EMAIL PROTECTED]" wrote : anonymous wrote : As I understood, seam is not intended to work in clustered environment? | | Huh Of *course* Seam is meant to work in a cluster! Which way? All Seam demo applications massively use session and conversation contexts. If some user starts conversation and his next request comes to another cluster node, there is no 'his' conversation context. User's conversation will just break? If so, what should developer do, if there is no possibility to replicate the context? It's also a logical willing to replicate sessions between cluster nodes. How can it be done in terms of Seam? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979307#3979307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979307 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam & clustering
Gavin, thank you for replying. As I understood, seam is not intended to work in clustered environment? Are you planning to do something about it in the future seam versions? So, currently we can replicate entities only if they are not bound to any seam context, which, in turn, means that these entities become a non-seam components, which means that we are loosing a lot of features provided by seam. Did I get it right? It also would be nice, if you think about providing an ability of replicating seam contexts between different cluster nodes (for some future Seam releases). At least session context should somehow be replicated. For example, currently, I don't have an idea how to implement the Single Sign On feature using Seam in clustered environment. I think, that using statefull session beans will not solve all clustering issues. Clustering support should somehow be transparent to Seam users. I mean, it should be configurable on Seam level. Perhaps using additional Seam annotations or xml.. it doesn't matter. I'm new to Seam, but it is clear from the first sight, that this framework is quite powerfull and developers get a lot of benefits from using it. Currently, a lot of applications are deployed in clustered environment, so, I guess, it's quite critical to do something with seam about clustering. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977929#3977929 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977929 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam & clustering
Hello, There are some questions about clusterization of Seam contexts and entitiy beans. Let's say I have an entity bean, which is scoped to be in Session Context. 1) If i configure cluster cache on entity level (EJB3EntityTreeCache + @Cache annotations in entities), will it be working if I access the same entity from other cluster node? As I understand, when referencing seam component by component's name, Seam looks for the component instance in the context first of all. So, does seam replicates instance of the component between contexts in different cluster nodes? 2) Is there a way to make the whole context to be replicated across all cluster nodes? Let's say I want to replicate session context (assuming that this context contains minimal set of information in order to avoid locks in TreeCache), is it possible? 3) If it is possible to use both approaches, which of them is more efficient and correct? 4) Is there any documentation on clustering approaches in Seam? Thank you in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977502#3977502 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977502 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
