[jboss-jira] [JBoss JIRA] Created: (JBCACHE-823) Refactor eviction configuration away from EvictionConfiguration interface

Refactor eviction configuration away from EvictionConfiguration interface ------------------------------------------------------------------------- Key: JBCACHE-823 URL: http://jira.jboss.com/jira/browse/JBCACHE-823 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA The EvictionConfiguration interface presumes that objects that represent a policy configuration should be able to parse their XML config themselves. We don't want that; parsing of the legacy XML configs should be handled by XmlConfigurationParser and policy config objects should be configurable by the MC without their having any internal expectation of being passed a DOM element. To do this: 1) Create interface EvictionPolicyConfig. This is used internally (e.g. in the RegionManager and Region classes) in place of EvictionConfiguration. 2) All of the config classes for the standard eviction policies now implement EvictionPolicyConfig instead of EvictionConfiguration. To support old custom policies: 1) EvictionConfiguration still exists but is deprecated. 2) EvictionConfiguration now extends EvictionPolicyConfig. So, custom impls *will* need to be modified to implement EvictionPolicyConfig's 2 methods. 3) XmlConfigurationParser when trying to configure a policy config object will check if it implements EvictionConfiguration. If it does, the legacy parseXmlConfig(Element) method will be called. Otherwise it will be configured via reflection. Need to decided exactly how to handle the old public EvictionConfiguration Region.getEvictionConfiguration() method. -- 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