[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-832) Develop CacheSPI impl for use in JBoss JMX microkernel

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-832?page=all ]

Brian Stansberry updated JBCACHE-832:
-------------------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.BETA2)

> Develop CacheSPI impl for use in JBoss JMX microkernel
> ------------------------------------------------------
>
>                 Key: JBCACHE-832
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-832
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.0.0.CR1
>
>
> If we want JBC 2.0 to work in AS 4.2, we'll need a way to construct a CacheSPI via the 4.x microkernel/SARDeployer.
> Initial thoughts:
> 1) Create class "CacheSPIWrapper" that implements CacheSPI, plus exposes all the configuration-related mbean attributes from JBC 1.4.  This is the class that's used for the "class" attribute of the mbean in the -service.xml file.
> 2) Class when instantiated also instantiates a Configuration object.  When SARDeployer invokes the setters on the legacy mbean attributes, the values are passed through to the Configuration object.
> 3) In createService(), the Configuration object is passed to DefaultCacheFactory, which returns an instance of the standard CacheSPI impl. CacheSPIWrapper holds a ref to this object for use as a delegate.
> 4) CacheSPIWrapper implements CacheSPI by delegation to the standard object.
> If we decide we don't want to support use of JBC 2.0 in 4.2, this task can be closed.

-- 
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