todo
h2. Send a JBI message to an external Web Service
todo
h3. Service Unit descriptor
todo
h2. Send a JBI message from an incoming SOAP message
todo
h3. Service Unit descriptor
todo
h1. REST Services
todo
h2. Introduction
todo
h2. Configuration
todo
h3. Provide mode : Provide access to external REST Service
todo
h3. Consume mode : Expose JBI Service as as REST Service
todo
h2. Samples
todo
h3. Provide mode
todo
h3. Consume mode
todo
h1. Web Service Notifications
todo
h2. Intoduction
todo
h2. Create a WS-N topic
todo
h2. Subscribe to WS-N producer
todo
h2. Send a WS notification from a JBI message
When the petals-bc-soap component receives a JBI message on a topic-activated endpoint, it is transformed into a WS-notification message and published on the linked topic.
As an example of SOAP notification message, if the JBI message payload is :
{code:lang=xml}
<text>This is a sample of JBI message payload...</text>
{code}
and if it is published on the *'TopicSample'* topic, the SOAP body payload of the notification message will be :
{code:lang=xml}
<wsnt:Notify>
<wsnt:NotificationMessage>
<wsnt:SubscriptionReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">
http://127.0.0.1:8084/wsn-consumer/services/consumer
</wsa:Address>
</wsnt:SubscriptionReference>
<wsnt:Topic Dialect="xsd:anyURI">TopicSample</wsnt:Topic>
<wsnt:ProducerReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">
http://127.0.0.1:8084/wsn-producer/services/producer
</wsa:Address>
</wsnt:ProducerReference>
<wsnt:Message>
<text>This is a sample of JBI message payload...</text>
</wsnt:Message>
</wsnt:NotificationMessage>
</wsnt:Notify>
{code}
h1. Security
h2. Introduction
The SOAP binding component provides WS security features through the Axis2 rampart module ([http://ws.apache.org/rampart/|http://ws.apache.org/rampart/]).
This module is based on Apache WSS4J ([http://ws.apache.org/wss4j/|http://ws.apache.org/wss4j/]), an implementation of the OASIS WS-security specification ([http://www.oasis-open.org/committees/wss|http://www.oasis-open.org/committees/wss]).
This module is natively provided by the binding component since the 3.0 release.
h2. Securing JBI Services
h3. Configuration
todo
h3. Client side
todo
h2. Using WS-Policy
The [Apache Rampart|http://ws.apache.org/rampart/] module is used to apply policies when calling an external Web Service (ie in consumer mode). The current section explains how to configure the component to use this feature.
h3. Configuration
todo
h3. Usage
Once the Service Unit is deployed on the SOAP Binding Component, all the JBI messages sent to the new activated endpoint are transformed into SOAP messages and the Web Service client will use the Service Unit defined policy to call the Web Service. The Web Service client behaviour is exactly the same as a policy-enabled Axis2 based Web Service client.
An example of WS policy with PEtALS is provided in the PEtALS SOAP usecases at : [http://websvn.ow2.org/listing.php?repname=petals&path=/trunk/configurations/petals-soap/petals-soap-policy/|http://websvn.ow2.org/listing.php?repname=petals&path=/trunk/configurations/petals-soap/petals-soap-policy/].
h1. Samples
The SOAP binding component samples are available as packaged use cases. You can find them on {{trunk/configurations/petals-soap}} directory of the [Petals ESB forge|http://forge.ow2.org/plugins/scmsvn/index.php?group_id=213].
h1. Know problems
h2. "Transport out has not been set"
If the exception message "Transport out has not been set" occurs when invoking an external web-service, using the petals-bc-soap, it can be due to a wrong URL of the external web-service. Please check it and retry your test.
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
E-mail
...