[ http://jira.jboss.com/jira/browse/JBCACHE-726?page=all ] Ben Wang updated JBCACHE-726: ----------------------------- Priority: Major (was: Minor) -- 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

[ http://jira.jboss.com/jira/browse/JBCACHE-726?page=comments#action_12346434 ] Ben Wang commented on JBCACHE-726: ---------------------------------- Also how do we intercept the static field variable in the class scope? E.g., if I do: SomeClass.staticVar = 4; how do I intercept it? -- 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

[ http://jira.jboss.com/jira/browse/JBCACHE-726?page=comments#action_12346577 ] Ben Wang commented on JBCACHE-726: ---------------------------------- Couple points here: 1. It is possible for JBoss Aop to intercept static fields, e.g., class POJO{ static int field; } <bind pointcut="field(int POJO->field)"> <interceptor class="xxxx"> </bind> or <bind pointcut="field(static int POJO->*)"> <...> </bind> or with annotation <bind pointcut="field(static int POJO->@XXX)"> <...> </bind> 2. Static field's lifecycle is global scope, meaning, once it is initialized, it won't get GC-ed. So along this line, we can say, if a static field needs replication, during a write access, we put the static field into a global region in the PojoCache. Once it is in, any further read access will be intercepted. And during startup, JBoss Aop will introduce a StaticFieldInterceptor to perform interception. This is at the class level. 3. The global region can be located outside of any region. Note that this approach won't work with buddy replication where sub-region scope is required. -- 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

[ http://jira.jboss.com/jira/browse/JBCACHE-726?page=comments#action_12346970 ] Ben Wang commented on JBCACHE-726: ---------------------------------- Related forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985706#... -- 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

[ http://jira.jboss.com/jira/browse/JBCACHE-726?page=all ] Ben Wang updated JBCACHE-726: ----------------------------- Priority: Major (was: Critical) Fix Version/s: (was: 2.0.0.ALPHA2) PojoCache 2.1.0 -- 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

[ http://jira.jboss.com/jira/browse/JBCACHE-726?page=all ] Jason T. Greene updated JBCACHE-726: ------------------------------------ Fix Version/s: POJO Cache 3.0.0 (was: PojoCache 2.1.0) -- 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