July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBCACHE-450) Create a pure pojo-based eviction policy

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-450?page=comments#action_12340065 ] Ben Wang commented on JBCACHE-450: ---------------------------------- For case #3 above regarding to object identity, actually we can't serialize PojoInstance becuse otherwise, we will serializae the actual POJO reference (and therefore the whole POJO!). This would defeat the whole purpose of PojoCache. So looks like we will have to accept the discrepancy there unless we have a lookup table that matches pojo instance to id. But again this will be strongly referenced and pojo instance will never gc-ed. > Create a pure pojo-based eviction policy > ---------------------------------------- > > Key: JBCACHE-450 > URL: http://jira.jboss.com/jira/browse/JBCACHE-450 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: POJOCache > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The eviction policy module has been refactored in 1.3. We will need to refactor the pojo-based evitction policy as well. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-450) Create a pure pojo-based eviction policy

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-450?page=comments#action_12340064 ] Ben Wang commented on JBCACHE-450: ---------------------------------- I have created a passivation test package to test out the POJO passivation/activation. > Create a pure pojo-based eviction policy > ---------------------------------------- > > Key: JBCACHE-450 > URL: http://jira.jboss.com/jira/browse/JBCACHE-450 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: POJOCache > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The eviction policy module has been refactored in 1.3. We will need to refactor the pojo-based evitction policy as well. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-450) Create a pure pojo-based eviction policy

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-450?page=all ] Ben Wang resolved JBCACHE-450. ------------------------------ Resolution: Won't Fix > Create a pure pojo-based eviction policy > ---------------------------------------- > > Key: JBCACHE-450 > URL: http://jira.jboss.com/jira/browse/JBCACHE-450 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: POJOCache > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The eviction policy module has been refactored in 1.3. We will need to refactor the pojo-based evitction policy as well. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-341) Refactor pojo cache eviction policy

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-341?page=all ] Ben Wang resolved JBCACHE-341. ------------------------------ Resolution: Duplicate Issue Assignee: Ben Wang (was: Daniel Huang) > Refactor pojo cache eviction policy > ----------------------------------- > > Key: JBCACHE-341 > URL: http://jira.jboss.com/jira/browse/JBCACHE-341 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: POJOCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: POJOCache > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > After refactoring of eviction policy in TreeCache, we will also need to do that in TreeCacheAop of which is pojo-based eviction. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-673) Refactor PojoCache to use TreeCache as a delegate

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-673?page=all ] Ben Wang updated JBCACHE-673: ----------------------------- Fix Version/s: 2.0.0 (was: POJOCache) > Refactor PojoCache to use TreeCache as a delegate > ------------------------------------------------- > > Key: JBCACHE-673 > URL: http://jira.jboss.com/jira/browse/JBCACHE-673 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > In release 2.0, we will use the underlying cache as a delegate instead of sub-classing. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-700) PojoCache api to throw PojoCacheException

by Ben Wang (JIRA)

PojoCache api to throw PojoCacheException ----------------------------------------- Key: JBCACHE-700 URL: http://jira.jboss.com/jira/browse/JBCACHE-700 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: POJOCache In 2.0 release, PojoCache Apis will throw PojoCacheException of which is a subclass of RuntimeException. -- 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

19 years, 10 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBCACHE-685) Integration using the new Cache2.0 API and SPI

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-685?page=all ] Ben Wang updated JBCACHE-685: ----------------------------- Component/s: PojoCache > Integration using the new Cache2.0 API and SPI > ---------------------------------------------- > > Key: JBCACHE-685 > URL: http://jira.jboss.com/jira/browse/JBCACHE-685 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > Currently, PojoCache 2.0 development is still using the old TreeCache API. It would be nice to migrate to 2.0 API when it is completed. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-588) Refactor PojoCache implementation to use interceptor-based architecture

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-588?page=all ] Ben Wang updated JBCACHE-588: ----------------------------- Component/s: PojoCache Fix Version/s: 2.0.0 (was: POJOCache) > Refactor PojoCache implementation to use interceptor-based architecture > ----------------------------------------------------------------------- > > Key: JBCACHE-588 > URL: http://jira.jboss.com/jira/browse/JBCACHE-588 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > In 2.0, we will refactor PojoCache to use interceptor based archticture. The interceptors in mind now inlcude eviction, locking (object level), etc. > There are two levels where interception can happen: api calls and field dynamic interceptor chains (for fine-grained operation). > We can opt for AOP to provide easier user customization, a la, ejb3 style of pointcut specification. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-173) Locking model when pojo is multiple referenced

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-173?page=all ] Ben Wang resolved JBCACHE-173. ------------------------------ Resolution: Done > Locking model when pojo is multiple referenced > ---------------------------------------------- > > Key: JBCACHE-173 > URL: http://jira.jboss.com/jira/browse/JBCACHE-173 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: POJOCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Under the new PojoCache, when a pojo is multiple referenced (let's say a pojo, Joe), it will be located under JBOSS_INTERANL node while leaving the original with a fqn/id reference. > In terms of locking, there are various implications. > 1. If we are modifying Joe under a tx context directly, the locking will be done under the JBoss_INTERNAL node. As a result, consistency is warranted. > 2. If Joe is part of a sub-object, say, a UserState object that has a Person Joe reference. Then, a tx context under that UserState obejct is not locking on Joe (since it has been moved to under JBOSS_INTERNAL, and therefore not under the same fqn sub-tree). -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-173) Locking model when pojo is multiple referenced

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-173?page=all ] Ben Wang updated JBCACHE-173: ----------------------------- Fix Version/s: 2.0.0 (was: POJOCache) > Locking model when pojo is multiple referenced > ---------------------------------------------- > > Key: JBCACHE-173 > URL: http://jira.jboss.com/jira/browse/JBCACHE-173 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: POJOCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Under the new PojoCache, when a pojo is multiple referenced (let's say a pojo, Joe), it will be located under JBOSS_INTERANL node while leaving the original with a fqn/id reference. > In terms of locking, there are various implications. > 1. If we are modifying Joe under a tx context directly, the locking will be done under the JBoss_INTERNAL node. As a result, consistency is warranted. > 2. If Joe is part of a sub-object, say, a UserState object that has a Person Joe reference. Then, a tx context under that UserState obejct is not locking on Joe (since it has been moved to under JBOSS_INTERNAL, and therefore not under the same fqn sub-tree). -- 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

19 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006