[SM-156] SOAP Binding component

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0-M1
• Component/s: servicemix-components
• Assignee: Guillaume Nodet
• Reporter: Guillaume Nodet
• Created: 05/Nov/05 16:42
• Updated: 21/Mar/06 22:12
• Resolved: 21/Mar/06 22:12

Description

Standard JBI component that handle different MEPs/

• in-only provider = invoke an external web service
• in-only consumer = receive a soap request and invoke a jbi endpoint
• in-out provider = perform a request / response to an external web service
• in-out consumer = perform a request / response to a jbi endpoint and send the response back

How to handle inbound requests: use an internal http server or use the http server when deployed in a JEE server ?
How ws-addressing and other related ws-*specs can fit in this model ? When the component is the consumer, the wsa infos can be used to specify the endpoint to send the exchange to, but how we could then specify a wsdl ? If wsa is not used, where will the component send the request, and what will be the difference between the wsdl deployed on the soap component and one the service engine ?

Issue Links

• is depended upon by: SM-153 Create JBI compliant bindings and ServiceEngine