Yes, JMX should be for reporting only. Not as a registry to obtain a component instance. Operations like starting and stopping a cache should be exposed though, perhaps via a Cache MBean (by annotating CacheDelegate?)

On 24 Jul 2009, at 09:55, Galder Zamarreno wrote: > Hi, > > Re: https://jira.jboss.org/jira/browse/ISPN-118 > > It turns out that since rev.454, DefaultCacheManager has already been > marked as an MBean > (http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i...) > > > Currently, none of the getCache() methods are marked as MBean operations > and I wanted to get confirmation on whether it should leave as it is. I > mean, in AS6, I suppose people will be able to use the JNDI method to > get access to the CacheManager and get the cache from there > (http://tinyurl.com/lq688t section 11.2). Anyone running standalone can > simply instantiate the cache manager. > > Thoughts? > -- > Galder Zamarreño > Sr. Software Engineer > Infinispan, JBoss Cache > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani manik(a)jboss.org Lead, Infinispan Lead, JBoss Cache http://www.infinispan.org http://www.jbosscache.org

On Sep 9, 2009, at 5:55 PM, Galder Zamarreno wrote: > </snip> > > Thoughts? Wouldn't it be simpler to only have one way of starting the cache (through CM)?

IMO, after the cache is stopped the system should be in the same state as before starting it: no jmx registered. This would keep things clearer. >> >> >> On 24 Jul 2009, at 09:55, Galder Zamarreno wrote: >> >>> Hi, >>> >>> Re: https://jira.jboss.org/jira/browse/ISPN-118 >>> >>> It turns out that since rev.454, DefaultCacheManager has already >>> been >>> marked as an MBean >>> (http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... >>> ) >>> >>> >>> Currently, none of the getCache() methods are marked as MBean >>> operations >>> and I wanted to get confirmation on whether it should leave as it >>> is. I >>> mean, in AS6, I suppose people will be able to use the JNDI method >>> to >>> get access to the CacheManager and get the cache from there >>> (http://tinyurl.com/lq688t section 11.2). Anyone running >>> standalone can >>> simply instantiate the cache manager. >>> >>> Thoughts? >>> -- >>> Galder Zamarreño >>> Sr. Software Engineer >>> Infinispan, JBoss Cache >>> _______________________________________________ >>> infinispan-dev mailing list >>> infinispan-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >> >> -- >> Manik Surtani >> manik(a)jboss.org >> Lead, Infinispan >> Lead, JBoss Cache >> http://www.infinispan.org >> http://www.jbosscache.org >> >> >> >> > > -- > Galder Zamarreño > Sr. Software Engineer > Infinispan, JBoss Cache > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

On 09/10/2009 04:42 PM, Mircea Markus wrote: > > On Sep 9, 2009, at 5:55 PM, Galder Zamarreno wrote: > >> </snip> >> >> Thoughts? > Wouldn't it be simpler to only have one way of starting the cache > (through CM)? It would be simpler in the sense that there's only one way to start it but I'm not sure from an ease of use point of view. Let me explain. Let's say you wanna a cache called "galdercache" for the 1st time. You'd call DefaultCacheManager.start("galdercache"), correct? Now, let's say you stop it, so there's no trace of galdercache any more. How do you restart it? You have to go and call DefaultCacheManager.start("galdercache"). So now, to restart a cache, you have to type something and you have to remember the cache name you gave it to it. Wouldn't be easier, from an usability perspective, to go to galdercache MBean and call start() on the MBean directly? This is why I think keeping the MBean around would improve usability.

> IMO, after the cache is stopped the system should be in the same > state > as before starting it: no jmx registered. This would keep things > clearer. >>> >>> >>> On 24 Jul 2009, at 09:55, Galder Zamarreno wrote: >>> >>>> Hi, >>>> >>>> Re: https://jira.jboss.org/jira/browse/ISPN-118 >>>> >>>> It turns out that since rev.454, DefaultCacheManager has already >>>> been >>>> marked as an MBean >>>> (http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... >>>> ) >>>> >>>> >>>> Currently, none of the getCache() methods are marked as MBean >>>> operations >>>> and I wanted to get confirmation on whether it should leave as it >>>> is. I >>>> mean, in AS6, I suppose people will be able to use the JNDI method >>>> to >>>> get access to the CacheManager and get the cache from there >>>> (http://tinyurl.com/lq688t section 11.2). Anyone running >>>> standalone can >>>> simply instantiate the cache manager. >>>> >>>> Thoughts? >>>> -- >>>> Galder Zamarreño >>>> Sr. Software Engineer >>>> Infinispan, JBoss Cache >>>> _______________________________________________ >>>> infinispan-dev mailing list >>>> infinispan-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> >>> -- >>> Manik Surtani >>> manik(a)jboss.org >>> Lead, Infinispan >>> Lead, JBoss Cache >>> http://www.infinispan.org >>> http://www.jbosscache.org >>> >>> >>> >>> >> >> -- >> Galder Zamarreño >> Sr. Software Engineer >> Infinispan, JBoss Cache >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

FWIW, in management tools like JON/RHQ etc, its not really that much fun for Mbeans to suddenly disappear... often nicer to change some value on them and leave them around for the console/tools to deal with. On Fri, Sep 11, 2009 at 3:44 AM, Mircea Markus&lt;mircea.markus(a)jboss.com&gt; wrote: > > On Sep 10, 2009, at 6:27 PM, Galder Zamarreno wrote: > >> >> >> On 09/10/2009 04:42 PM, Mircea Markus wrote: >>> >>> On Sep 9, 2009, at 5:55 PM, Galder Zamarreno wrote: >>> >>>> </snip> >>>> >>>> Thoughts? >>> Wouldn't it be simpler to only have one way of starting the cache >>> (through CM)? >> >> It would be simpler in the sense that there's only one way to start it >> but I'm not sure from an ease of use point of view. Let me explain. >> >> Let's say you wanna a cache called "galdercache" for the 1st time. >> You'd >> call DefaultCacheManager.start("galdercache"), correct? Now, let's say >> you stop it, so there's no trace of galdercache any more. How do you >> restart it? You have to go and call >> DefaultCacheManager.start("galdercache"). So now, to restart a cache, >> you have to type something and you have to remember the cache name you >> gave it to it. >> >> Wouldn't be easier, from an usability perspective, to go to >> galdercache >> MBean and call start() on the MBean directly? >> >> This is why I think keeping the MBean around would improve usability. > I see your point. After all, in an non-JMX world, one can do exactly > the same thing with a Cache.start *OR* CM.start. >> >>> IMO, after the cache is stopped the system should be in the same >>> state >>> as before starting it: no jmx registered. This would keep things >>> clearer. >>>>> >>>>> >>>>> On 24 Jul 2009, at 09:55, Galder Zamarreno wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Re: https://jira.jboss.org/jira/browse/ISPN-118 >>>>>> >>>>>> It turns out that since rev.454, DefaultCacheManager has already >>>>>> been >>>>>> marked as an MBean >>>>>> (http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... >>>>>> ) >>>>>> >>>>>> >>>>>> Currently, none of the getCache() methods are marked as MBean >>>>>> operations >>>>>> and I wanted to get confirmation on whether it should leave as it >>>>>> is. I >>>>>> mean, in AS6, I suppose people will be able to use the JNDI method >>>>>> to >>>>>> get access to the CacheManager and get the cache from there >>>>>> (http://tinyurl.com/lq688t section 11.2). Anyone running >>>>>> standalone can >>>>>> simply instantiate the cache manager. >>>>>> >>>>>> Thoughts? >>>>>> -- >>>>>> Galder Zamarreño >>>>>> Sr. Software Engineer >>>>>> Infinispan, JBoss Cache >>>>>> _______________________________________________ >>>>>> infinispan-dev mailing list >>>>>> infinispan-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>>>> >>>>> -- >>>>> Manik Surtani >>>>> manik(a)jboss.org >>>>> Lead, Infinispan >>>>> Lead, JBoss Cache >>>>> http://www.infinispan.org >>>>> http://www.jbosscache.org >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Galder Zamarreño >>>> Sr. Software Engineer >>>> Infinispan, JBoss Cache >>>> _______________________________________________ >>>> infinispan-dev mailing list >>>> infinispan-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> >>> >>> _______________________________________________ >>> infinispan-dev mailing list >>> infinispan-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >> >> -- >> Galder Zamarreño >> Sr. Software Engineer >> Infinispan, JBoss Cache >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev >