Yes, Sergey, Should I manually give/define every mbean an indexer which is accumulated as you mentioned? > > http://localhost:8080/services/jmx/mbean/0 > > http://localhost:8080/services/jmx/mbean/1 > > http://localhost:8080/services/jmx/mbean/2 ... > > http://localhost:8080/services/jmx/mbean/*** Thank you.
Regards: Shenglin Qiu > Date: Thu, 19 May 2011 15:03:03 +0100 > Subject: Re: Expose MBeans in CXF > From: sberyoz...@gmail.com > To: dev@cxf.apache.org > > HI Shenglin > > On Thu, May 19, 2011 at 2:54 PM, Shenglin Qiu <dabaip...@hotmail.com> wrote: > > > > Yes Sergey, will have these following pattern: > > > > http://localhost:8080/services/jmx/mbean/0 -> CXF Bus > > > > http://localhost:8080/services/jmx/mbean/01 -> UserService > > > > http://localhost:8080/services/jmx/mbean/0123 -> CustomerService > > > > http://localhost:8080/services/jmx/mbean/01234 -> GreeterService (Soap) > > > > http://localhost:8080/services/jmx/mbean/012 -> JMXServer will be hidden > > to user. > > > > That looks better, but do you think it would make sense to avoid the > concatenation ? > We can get hundreds of CXF MBeans in the production environment, so > IMHO it would be simpler > to have /mbean/199 identifying a particular MBean, > > Cheers, Sergey > > > > > Regards: > > > > Shenglin Qiu > > > > > >
