THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Run the examples/wsn-http-binding example per the README.txt.
In this simple scenario an HttpProducer produces notification messages, and an HttpConsumer receives notification messages. Both HttpProducer and HttpConsumer will interact with ServiceMix via the HTTP endpoints exposed in the standard example configuration.
The sequence consists of 4 primary messages: 1) createPullPoint, 2) subscribe (pullPoint), 3) notify and 4) getMessages. The following high level sequence diagram captures some important interactions:
The SOAP messages are as follows:
1) createPullPoint
>>>>>
<!--
Sample CreatePullPoint request
sent to http://localhost:8192/CreatePullPoint/
note: trailing slash required due to smx bug
-->
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
<env:Body>
<wsnt:CreatePullPoint
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" />
</env:Body>
</env:Envelope>
<<<<<
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Body>
<ns4:CreatePullPointResponse
xmlns:ns2="http://www.w3.org/2005/08/addressing"
xmlns:ns4="http://docs.oasis-open.org/wsn/b-2"
xmlns:ns3="http://docs.oasis-open.org/wsrf/bf-2"
xmlns:ns5="http://docs.oasis-open.org/wsn/t-1">
<ns4:PullPoint>
<ns2:Address>
http://servicemix.org/wsnotification/PullPoint/ID-some-host-38972-1188922931357-6-0
</ns2:Address>
</ns4:PullPoint>
</ns4:CreatePullPointResponse>
</env:Body>
</env:Envelope>