I think that JMX could be used there. The bigger issue, is that from some perspectives, having a JMX monitoring system already in place, makes it more easy to do it with JMX. From the other perspective, having a standard "Management/tuning/observing" ServiceUI roll makes it possible to trivially integrate lots of different things into a single desktop experience. If you have to solve the problem with JMX connectors "through the network", then Jini should be doable as well. Internally, we could suggest that JMX be used, but then provide a connector which is not remote, but proxied to, by a standard Jini service interface.
Gregg On Oct 29, 2012, at 3:12 AM, Dan Creswell <dan.cresw...@gmail.com> wrote: > Sounds more like a job for JMX to me.... > > On 29 October 2012 00:06, Gregg Wonderly <gr...@wonderly.org> wrote: > >> Well, perhaps some package private extensions could be put in place which >> could have "protected" access proxy methods which could allow you to get >> access? I've always wanted to more formally and fully instrument discovery >> in particular. I seem to always end up patching in lots of new/different >> debugging each time I end up with some odd network situation at my >> customers' sites. It seems that there are almost always some firewall >> issues or something. I'd like to see a serviceUI on reggie which would >> allow you to see all the registered notification listeners as well as the >> connections for each as well as failing notifications due to socket connect >> errors and what the related errors are for example. >> >> Gregg Wonderly >> >> On Oct 28, 2012, at 7:58 AM, Simon IJskes - QCG <si...@qcg.nl> wrote: >> >>> On 27-10-12 19:08, Gregg Wonderly wrote: >>>> What is your motivation to ask this question? >>>> >>>> Gregg >>>> >>>> On Oct 24, 2012, at 7:08 AM, Simon IJskes - QCG <si...@qcg.nl> wrote: >>>> >>>>> Does anybody have a problem with making com.sun.jini.reggie.Registrar >> public? >>>>> >>>> >>> >>> I wanted to build a monitor/prototype for some experimentation, around >> Registrar.notify(), and noticed i couldnt because of the package private >> access. >>> >>> >> >>
