You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org> on 2009/01/15 13:07:59 UTC
[jira] Created: (QPID-1582) WS-Notifications
WS-Notifications
----------------
Key: QPID-1582
URL: https://issues.apache.org/jira/browse/QPID-1582
Project: Qpid
Issue Type: Sub-task
Components: Java Management : QMan
Affects Versions: M5
Environment: J2SE 1.5 or higher
Reporter: Andrea Gazzarini
Assignee: Andrea Gazzarini
Fix For: M5
JMX Notifications are already enabled on the JMX core.
Moreless the same thing must be implemented on the WS-DM adapter in order to enable management clients to subscribe and watch WS-Resources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1582) WS-Notifications
Posted by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Gazzarini updated QPID-1582:
-----------------------------------
Priority: Critical (was: Major)
> WS-Notifications
> ----------------
>
> Key: QPID-1582
> URL: https://issues.apache.org/jira/browse/QPID-1582
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Management : QMan
> Affects Versions: M5
> Environment: J2SE 1.5 or higher
> Reporter: Andrea Gazzarini
> Assignee: Andrea Gazzarini
> Priority: Critical
> Fix For: M5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> JMX Notifications are already enabled on the JMX core.
> Moreless the same thing must be implemented on the WS-DM adapter in order to enable management clients to subscribe and watch WS-Resources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-1582) WS-Notifications
Posted by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Gazzarini resolved QPID-1582.
------------------------------------
Resolution: Fixed
Hi all,
the last step (at the moment) of QMan is here : implementation on QMan of WS-Notification.
As first version there are only two topics : one for lifecycle events of object instances (create & remove) and one for lifecycle events (only create) of events.
That means:
1) There are two topics : qman:ObjectsLifeCycleTopic and qman:EventsLifeCycleTopic
2) QMan will publish on the first one the following message when (for example) a connection is created :
<wsnt:NotificationMessage
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
xmlns:qman="http://amqp.apache.org/qpid/management/qman"
xmlns:qman-wsa="http://amqp.apache.org/qpid/management/qman/addressing"
xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
<wsnt:SubscriptionReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://romagazzarini:8080/qman/services/SubscriptionManager</wsa:Address>
<wsa:ReferenceParameters xmlns:wsa="http://www.w3.org/2005/08/addressing">
<qman-wsa:ResourceId xmlns:qman-wsa="http://amqp.apache.org/qpid/management/qman/addressing">09c45414-1adf-4bf1-b855-71c9597176e0</qman-wsa:ResourceId>
</wsa:ReferenceParameters>
</wsnt:SubscriptionReference>
<wsnt:Topic
Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete" xmlns:qman="http://amqp.apache.org/qpid/management/qman">qman:EventsLifeCycleTopic</wsnt:Topic>
<wsnt:ProducerReference>
<wsa:ReferenceParameters xmlns:wsa="http://www.w3.org/2005/08/addressing"/>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://romagazzarini:8080/qman/services/adapter</wsa:Address>
</wsnt:ProducerReference>
<wsnt:Message>
<qman:LifeCycleEvent TimeMillis="1234295015000" Type="CREATED" xmlns:qman="http://amqp.apache.org/qpid/management/qman">
<qman:Resource>
<qman-wsa:ResourceId xmlns:qman-wsa="http://amqp.apache.org/qpid/management/qman/addressing">aff2f6ec-2e5c-4768-ae87-6da2c8a005ff</qman-wsa:ResourceId>
<qman:PackageName>org.apache.qpid.broker</qman:PackageName>
<qman:Name>connection</qman:Name>
</qman:Resource>
</qman:LifeCycleEvent>
</wsnt:Message>
</wsnt:NotificationMessage>
3) A similar notification (but with type="REMOVED") will be published when an object instance (a connection for example) is removed
4) For events there are only CREATE notification. So on the second mentioned topic a message will be published each time an "event" (for example a subscribe event) is created on QMan (and therefore on Qpid)
Further improvement will be made in order to meet (eventual) management client needs.
Best regards,
Andrea
> WS-Notifications
> ----------------
>
> Key: QPID-1582
> URL: https://issues.apache.org/jira/browse/QPID-1582
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Management : QMan
> Affects Versions: M5
> Environment: J2SE 1.5 or higher
> Reporter: Andrea Gazzarini
> Assignee: Andrea Gazzarini
> Priority: Critical
> Fix For: M5
>
> Original Estimate: 168h
> Time Spent: 72h
> Remaining Estimate: 0h
>
> JMX Notifications are already enabled on the JMX core.
> Moreless the same thing must be implemented on the WS-DM adapter in order to enable management clients to subscribe and watch WS-Resources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org