E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (44)
View Page History{section}
[petals-se-notification wsdl|^component.wsdl] {column}
{column}
h1. Abstract
...
{note}Note : these two components are only "template component" and can help you to implement your own ones.{note}
...You can test Petals ESB WS-Notification features using the webconsole test section or you can deploy and start petals-se-Wsn Producer/Consumer components that will automatically process Notification Requests("Subscribe" and "RegisterPublisher requests on start;"Notify" request each 30 seconds) when their services assemblies are deployed and started.
h3. using petals-se-Wsn{Producer/Consumer} componentsInstalling petals-se-Wsn {Producer/Consumer} components and their service assemblies will automatically launch usecases. No interactions are needed. On Service assembly start, the petals-se-WsnProducer sends a RegisterPublisher request to the petals-se-notification and the petals-se-WsnConsumer do the same by sending a "Subscribe" request to the petals-se-notification component. Its Subscribe request is then forwarded to the petals-se-WsnProducer as soon as the petals-se-WsnProducer is registered.
h3. using petals-se-WsnProducer, petals-se-WsnConsumer components
Installing petals-se-WsnProducer and petals-se-WsnConsumer components and their service assemblies will automatically launch usecases. No interactions are needed. On Service assembly start, the petals-se-WsnProducer sends a RegisterPublisher request to the petals-se-notification and the petals-se-WsnConsumer do the same by sending a "Subscribe" request to the petals-se-notification component. Its Subscribe request is then forwarded to the petals-se-WsnProducer as soon as the petals-se-WsnProducer is registered.
To run the usecase you must :
... name="WS-BrokeredNotification" targetNamespace="http://petals.ow2.org/petals-se-notification">
<\!-\- ================================================== \-->
<\!-\- ================== imports ======================= \-->
<\!-\- ================================================== \-->
<wsdl:import location="brw-2.wsdl"
namespace="http://docs.oasis-open.org/wsn/brw-2" />
<wsdl:import location="bw-2.wsdl" namespace="http://docs.oasis-open.org/wsn/bw-2" />
namespace="http://docs.oasis-open.org/wsn/brw-2" />
<wsdl:import location="bw-2.wsdl" namespace="http://docs.oasis-open.org/wsn/bw-2" />
<\!-\- ========================================================= \-->
<\!-\- ========= Extended or Custom Types Definitions ========== \-->
<\!-\- \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\~ \-->
<\!-\- this section describes some custom types used in child \-->
<\!-\- nodes where allowed element type - see associated \-->
<\!-\- XML schema - is "anyType". For example "QueryExpressionType" \-->
<\!-\- defined in the "b-2.xsd" XML schema file - which is a part of \-->
<\!-\- "WS-BaseNotification" specification - allowed "anyType" child \-->
<\!-\- node. In this specific case a simple "string" child node \-->
<\!-\- called "xpath" is used. Of course, this choice is not \-->
<\!-\- restrictive and "any other type" child node can still be used instead \-->
<\!-\- \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\~ \-->
<\!-\- ========================================================= \-->
... </wsdl:types>
<\!-\- ================================================== \-->
<\!-\- ========= Message part definition ================ \-->
<\!-\- ================================================== \-->
<wsdl:message name="EmptyMessage"/>
<wsdl:message name="EmptyMessage"/>
... </wsdl:message>
<\!-\- =============================================== \-->
<\!-\- ========= PortType definition ================ \-->
<\!-\- =============================================== \-->
<wsdl:portType name="SupportedTopicsSet">
<wsdl:portType name="SupportedTopicsSet">
... </wsdl:portType>
<\!-\- ============================================= \-->
<\!-\- ========== Binding definition =============== \-->
<\!-\- ============================================= \-->
<\!-\- NotificationBroker binding definition \-->
<wsdl:binding name="NotificationBrokerBinding" type="wsn-brw:NotificationBroker">
<soap:binding style="document"
<soap:binding style="document"
... <wsdl:operation>
</wsdl:binding>
</wsdl:binding>
<\!-\- PublisherRegistrationManager binding definition \-->
<wsdl:binding name="PublisherRegistrationManagerBinding"
type="wsn-brw:PublisherRegistrationManager">
type="wsn-brw:PublisherRegistrationManager">
... </wsdl:operation>
</wsdl:binding>
</wsdl:binding>
<\!-\- SubscriptionManager binding definition \-->
<wsdl:binding name="SubscriptionManagerBinding" type="wsn-bw:SubscriptionManager">
<soap:binding style="document"
<soap:binding style="document"
... </wsdl:binding>
<\!\-- SupportedTopicsSet portType Service binding definition \-->
<wsdl:binding name="SupportedTopicsSetBinding"
type="tns:SupportedTopicsSet">
type="tns:SupportedTopicsSet">
... <\!-\- ============================================= \--v
<\!-\- =========== Service part definition ========= \-->
<\!-\- ============================================= \-->
<wsdl:service name="NotificationBrokerService">
<wsdl:port name="NotificationBrokerServiceEndpoint" binding="tns:NotificationBrokerBinding">
<wsdl:port name="NotificationBrokerServiceEndpoint" binding="tns:NotificationBrokerBinding">
... </wsdl:definitions>{code}
h2. Ws-Notification requests templates
Subscribe Request Payload template :
Subscribe Request Payload template :
...</wsnt:Subscribe>{code}
Unsubscribe Request Payload template :
... </ebm:ResourceUuidList>
</wsnt:Unsubscribe>{code}
</wsnt:Unsubscribe>{code}
RegisterPublisher Request Payload template :
... <wsn-br:InitialTerminationTime>2009-12-25T00:00:00.00000Z</wsn-br:InitialTerminationTime>
</wsn-br:RegisterPublisher>{code}
</wsn-br:RegisterPublisher>{code}
DestroyRegistration Request Payload template :
... </ebm:ResourceUuidList>
</wsn-br:DestroyRegistration>{code}
</wsn-br:DestroyRegistration>{code}
Notify Request Payload template :
...</wsnt:Notify>{code}
{code}
{column}
{column:width=350px}
{column:width=350px}
...