[jbosscache-dev] Use of isStandalone field in TreeCache

[Brian Stansberry]

Ahh, I understand now.  This is legacy stuff.  The serviceName property
in 1.x was not a config attribute, but rather was set by the JMX server
via a callback when the cache was registered in JMX.  So testing if it
was null was a way of testing whether the cache was already registered.
That's no longer the way it works, so I'm going to remove this logic.

jbosscache-dev-bounces at lists.jboss.org wrote:
> The isStandalone field in TreeCache is giving me a bit of trouble in
> TreeCache. 
> 
> It's usage seems to be "check if the
> Configuration.serviceName property is null/empty. If it's
> not, don't register the cache with JMX".
> 
> I'm not sure what the use case for this behavior is, but it's
> causing hassles for me.  With the MC, objects are no longer
> registered automatically with JMX.  So, I'm counting on the
> cache registering itself. (Actually, I have no choice -- the
> API leaves no other clean way to get it registered.)  But, I
> don't want to use the default ObjectName JBC uses, so I need
> to set the serviceName property.  But if I do that, the cache
> is no longer getting registered.
> 
> Brian Stansberry
> Lead, AS Clustering
> JBoss, a division of Red Hat
> Ph: 510-396-3864
> skype: bstansberry
> 
> IT executives: Red Hat still #1 for value
> http://www.redhat.com/promo/vendor/