[
http://jira.jboss.com/jira/browse/JBAS-4049?page=all ]
Brian Stansberry closed JBAS-4049.
----------------------------------
Fix Version/s: (was: JBossAS-5.0.0.Beta2)
Resolution: Done
Decided to implement the cache listener approach due to JBAS-4067. For now
Subject/Observer logic remains to make it technically possible to share pojos across
sessions (which is not advised) but if users don't add the Subject mixin FIELD
granularity repl will still work.
Consider removing Subject mixin from FIELD granularity session Pojos
--------------------------------------------------------------------
Key: JBAS-4049
URL:
http://jira.jboss.com/jira/browse/JBAS-4049
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-4.2.0.CR1
FIELD granularity replication uses a Subject mixin to the pojo to notify the session when
an attribute is changed.
Consider dropping this in place of having the CacheListener detect the cache change and
notify the session (via the JBossCacheManager).
Pro:
1) Simpler instrumentation. Classes instrumented a la the PojoCache examples (which
don't add the Subject mixin) will work. The PojoCache examples can be the sole
reference point for how to instrument classes.
2) For sure detects all changes in the pojo. Not sure if the Subject thing catches
changes to collections of non-pojos.
Con:
Perhaps a bit slower, as the mechanism to look up and notify the session is more
cumbersome.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira