On 20 Mar 2013, at 09:44, Tristan Tarrant <ttarrant(a)redhat.com> wrote:
On 03/19/2013 06:55 PM, Dennis Reed wrote:
> This is an invalid use of the MBean names.
>
> The keys in an ObjectName are unordered. It is a bug to depend on a
> specific ordering of the keys.
Thanks Dennis, I was about to write that.
As in, the JMX spec does not guarantee the order of ObjectName components?
> On 03/19/2013 10:07 AM, Manik Surtani wrote:
>>
>> On 27 Feb 2013, at 15:54, James Strachan <james.strachan(a)gmail.com> wrote:
>> I also wondered if folks fancied adding a few more operations to the
>> Cache mbean so that we could build a little console in hawtio for
>> Infinispan; to view/update contents of the caches or flush them etc?
This is actually trickier than you think: Infinispan can theoretically
use any kind of data for keys/values (including custom Java classes).
Furthermore these keys/values may be wrapped by service-specific
containers making it very difficult to implement some kind of CRUD
interface.
You could probably latch on to the Infinispan CLI server component
(which incidentally is also exposed as an MBean) and provides solutions
for most of the above problems.
Does this mean that [1] is solved by an existing MBean?
[1]
https://issues.jboss.org/browse/ISPN-2926
Tristan
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid