[
http://jira.jboss.com/jira/browse/EJBTHREE-930?page=all ]
Andrew Lee Rubinger updated EJBTHREE-930:
-----------------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4102748#...
Assignee: Andrew Lee Rubinger (was: Brian Stansberry)
Combine into one annotation, ignore "replicationIsPassivation" in non-clustered
implementations.
Simplify use of @CacheConfig
----------------------------
Key: EJBTHREE-930
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-930
Project: EJB 3.0
Issue Type: Feature Request
Affects Versions: AS 4.2.0 GA
Reporter: Brian Stansberry
Assigned To: Andrew Lee Rubinger
There are two separate @CacheConfig impls -- one for the simple cache and one for the
clustered. We should support something like:
@Stateful
@org.jboss.annotation.ejb.cache.simple.CacheConfig(maxSize=200000,
idleTimeoutSeconds=500)
@Remote(Test.class)
public class TestBean implements Test.....
where clustering is enabled via <clustered>true</clustered> in jboss.xml.
Similarly,
@Stateful
@org.jboss.annotation.ejb.cache.tree.CacheConfig(maxSize=200000, idleTimeoutSeconds=500,
replicationIsPassivation=false)
@Remote(Test.class)
public class TestBean implements Test.....
where clustering is disabled via <clustered>false</clustered> in jboss.xml.
Basically, the StatefulCache impls should check for the existence of the other
@CacheConfig if the standard one isn't present. Then use the common values between
the two, and the default values for any missing configurations (e.g.
replicationIsPassivation).
Probably the @CacheConfig annotations themselves as well as the impls should be
refactored into a type hierarchy.
--
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