2:38 p.m.
Consider adding a method to expose lifecycle state
--------------------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
Project: JBoss Cache
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.BETA1
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
7:35 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-928) Consider adding a method to expose lifecycle state
[ http://jira.jboss.com/jira/browse/JBCACHE-928?page=all ]
Manik Surtani updated JBCACHE-928:
----------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.0.BETA1)
Consider adding a method to expose lifecycle state
--------------------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
Project: JBoss Cache
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
7:39 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-928) Consider adding a method to expose lifecycle state
[ http://jira.jboss.com/jira/browse/JBCACHE-928?page=comments#action_12350670 ]
Manik Surtani commented on JBCACHE-928:
---------------------------------------
See email:
http://lists.jboss.org/pipermail/jbosscache-dev/2007-January/000661.html
Consider adding a method to expose lifecycle state
--------------------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
Project: JBoss Cache
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
12:17 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-928) Consider adding a method to expose lifecycle state
[ http://jira.jboss.com/jira/browse/JBCACHE-928?page=all ]
Brian Stansberry updated JBCACHE-928:
-------------------------------------
Fix Version/s: 2.0.0.CR2
(was: 2.1.0.GA)
Assignee: Brian Stansberry (was: Manik Surtani)
I need to do this for 2.0.0.CR2 to resolve JBCACHE-1058, which needs to be done in 2.0.0.
Consider adding a method to expose lifecycle state
--------------------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
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.CR2
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
1:04 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-928) Consider adding a method to expose lifecycle state
[ http://jira.jboss.com/jira/browse/JBCACHE-928?page=comments#action_12362762 ]
Brian Stansberry commented on JBCACHE-928:
------------------------------------------
Clarification -- I don't need to expose the lifecycle state, just track it. Exposing
it seems like a logical thing to do though once we go to the effort of tracking.
Consider adding a method to expose lifecycle state
--------------------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
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.CR2
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
2:31 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-928) Add a method to expose lifecycle state
[ http://jira.jboss.com/jira/browse/JBCACHE-928?page=all ]
Brian Stansberry updated JBCACHE-928:
-------------------------------------
Summary: Add a method to expose lifecycle state (was: Consider adding a method to
expose lifecycle state)
Add a method to expose lifecycle state
--------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
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.CR2
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
2:33 p.m.
New subject: [JBoss JIRA] Closed: (JBCACHE-928) Add a method to expose lifecycle state
[ http://jira.jboss.com/jira/browse/JBCACHE-928?page=all ]
Brian Stansberry closed JBCACHE-928.
------------------------------------
Resolution: Done
Method is public CacheStatus getCacheStatus(). Added to Cache, CacheJmxWrapperMBean and
PojoCacheJmxWrapperMBean. The 2 MBean interfaces also expose getState, which is the
legacy name for the concept. That is done to ease integration with the AS JSR-77 layer,
which checks for an attribute of that name in order to decide if an mbean is manageable.
Add a method to expose lifecycle state
--------------------------------------
Key: JBCACHE-928
URL: http://jira.jboss.com/jira/browse/JBCACHE-928
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.CR2
In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the
inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is
created/started/stopped/destroyed. We should consider adding this, perhaps as a method in
the Cache interface.
--
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
6923
days inactive
7057
days old
6 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Brian Stansberry (JIRA) -
Manik Surtani (JIRA)