"bstansberry(a)jboss.com" wrote : | | 1) Store pojos under the session that first passes them to setAttribute. | | Pros: solves above problems | | Cons: if webapp stores the same pojo under two different sessions, PC will support this. But if the first session is removed, the underlying pojo will be removed with it and if the second session tries to use it they will get an exception. | | Are you just referring to making every session a region? This would still have problems with gravitation, since a shared pojo would either bounce back and forth if we always force gravitation, or if we don't might not be accessable . Unless of course you can gaurantee that all sessions associated with a web app are all located on the same node. anonymous wrote : | 2) Make it configurable via a pojo-scope element in jboss-web.xml, valus are APPLICATION or SESSION, default is session. | | Basically, still support the existing behavior. Log a WARN if user specifies ATTRIBUTE with a buddy replication cache. | IMO if we are going to share pojos and bind them to a special region, then we should make that region not use buddy replication (if possible). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146607#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...