Seems we maybe could use a number of JMX stuff from Felix in Radman,
related to JMX?

/peter

On 11/4/06, Manuel Santillán <[EMAIL PROTECTED]> wrote:
> Well, Until recently I was not very fond of open mbeans, since they are
> way to cumbersome to create. You had to handcraft the serialization of
> data. It was really SNMP-ish. Recent support of open mbeans in Java 6
> simplifies it significantly, though...
> Didier Donsez escribió:
> > Manuel Santillán wrote:
> >
> >> Hi Francesco,
> >>
> >> Notifications in JMX can embed custom data if you like. Take a look
> >> at the javax.management.Notification#setUserData(Object o) and its
> >> related getter. One thing to take into account is that  you need to
> >> have knowledge of the type in the client. Hope it helped!!
> >>
> > Hum, JMX best practices recommend to reuse open mbean types
> > So you can display your notified user data in off-the-shelves JMX
> > consoles (JConsole, ...)
> > You can have also a look on
> > http://java.sun.com/products/JavaManagement/best-practices.html#mozTocId199275
> >
> > Didier
> >
> >> Cheers
> >>
> >>
> >> //manuel
> >>
> >> Manuel Santillán
> >> Francesco Furfari escribió:
> >>
> >>> Dear Stephan , Manuel,
> >>> I need some hint about the notification mechanism in JMX.
> >>> I've figured out that mbean notifications allow to send only simple
> >>> messages.
> >>> If  a client needs to receive complex data it has to pull the data
> >>> using, for example, the sequence number obtained in a previous
> >>> notification message.
> >>> Is this correct or I'm missing something?
> >>>
> >>> thanks in advance
> >>> francesco
> >>>
> >>>
> >>
> >
> >
>
>

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to