Hi Andrea, That's excellent thank you for that. I have started the process for QPID-1357 and if there isn't any objection I'll commit your patch by tomorrow.
Thanks Arnaud ----- "Andrea Gazzarini (JIRA)" <[email protected]> wrote: > [ > https://issues.apache.org/jira/browse/QPID-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Andrea Gazzarini updated QPID-1357: > ----------------------------------- > > Attachment: qman_17102008_events_handling.patch > > Hi All, This is the latest QMan patch. > Accroding to this issue description, QMan is able to handle events. > Some little changes are occurred in the existing design in order to > collect incoming event instances. Those include : > > - A new layer supertype has been added, QpidEntity, which is parent > class for QpidClass and QpidEvent; > - A new message handler responsible to deal with event indication > messages (opcode = 'e') > - JMX namespace has been changed too, according to what suggested by > Ted. Now class instances are under type=Object while event instances > are under type=Event so basically the screenshot attatched with this > issue still remain valid in order to understand the structure of the > domain model. > > Regards, > Andrea > > > QMan events handling > > -------------------- > > > > Key: QPID-1357 > > URL: > https://issues.apache.org/jira/browse/QPID-1357 > > Project: Qpid > > Issue Type: Improvement > > Components: Java Client > > Affects Versions: M4 > > Environment: J2SE 5 or higher, any OS that is supporting > Java > > Reporter: Andrea Gazzarini > > Priority: Minor > > Fix For: M4 > > > > Attachments: jconsole_showing_qman_events.JPG, > qman_17102008_events_handling.patch > > > > > > According to new features of QMF introduced with QPID-1327, QMan > will be improved for events handling. > > The improvement will be done without any change on the preexisting > features. > > Technically speaking, two new entities will be added on QMan domain > : > > 1) QpidEvent : the entity which is encapsulating the event > definition (and therefore the collected event instances). This is very > similar to preexisting QpidClass entity (for classes). > > 2) EventMessageResponseHandler : message handler responsible to deal > with event content messages (opcode = 'e') > > Regards, > > Andrea > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online.
