]
Manik Surtani reopened JBCACHE-328:
-----------------------------------
Assignee: (was: Manik Surtani)
Move attributes and getters/setters to interceptors
---------------------------------------------------
Key: JBCACHE-328
URL:
http://jira.jboss.com/jira/browse/JBCACHE-328
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Bela Ban
Fix For: 2.0.0.GA
Example: currently IsolationLevel is an attribute of TreeCache. Goal is to make it an
attribute of PessimisticLockingInterceptor.
Advantage:no unneeded methods in TreeCache, cluttering up the TreeCache class
#1 Implicit Configuration (conceptual)
--------------------
<TreeCache>
<Replication>
<config> ... </config>
<mode>ASYNC</mode>
</Replication>
<IsolationLevel>
REPEATABLE-READ
</IsolationLevel>
</TreeCache>
This configures the interceptor chain
#2 Explicit configuration
------------------------------------
<TreeCache>
<Interceptor name="PessimisticLockingInterceptor"
class="xxxx"
level="REPEATABLE-READ" />
<Interceptor>...</Interceptor>
</TreeCache>
The chain is defined explicitly, attributes are defines per interceptor
#3 JMX
If JMx is used, JBossCache is registered with the MBeanServer, and all interceptors are
registered under JBossCache, e.g.
type=cache;name=JBossCache1
type=cache;name=JBossCache1;interceptor_name=PessimisticLockingInterceptor
type=cache;name=JBossCache1;interceptor_name=CacheLoaderInterceptor
type=cache;name=JBossCache1;interceptor_name=ReplicationInterceptor
#4 Programmatic access
Can be done through JMX, but is not nice
cache.getIsolationLevel() -->
((PessimisticLockingInterceptor)cache.getInterceptor("PessimisticLockingInterceptor")).getIsolationLevel()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: