SOAP client support

[hodrigohamalho]

Update: Getting support from the Product Side: https://issues.jboss.org/browse/ENTESB-12062

This is a Feature Request

Description

I think this is an always expected question in a customer meeting about Integration.
"How I can do SOAP to REST using low code Integration?" It would be nice to have this on Syndesis.

[KurtStam]

Thanks @hodrigohamalho. What would be the 80% use case for SOAP support?

0. No support and document how to wrap SOAP services like: http://redhatgov.io/workshops/agile_integrations_dev/lab04/
1. Would it be a SOAP connector so that you call into a SOAP service, and if so what authentication scenarios would we need to support
2. Do we also need to be able to support exposing as a SOAP service, or could this wait till later.
3. Support SOAP as a payload in Syndesis and AtlasMap. (This would be a lot more involved..)
4. ?

Finally, Syndesis support extensions (https://github.com/syndesisio/syndesis-extensions) so I could see the community contribute a soap connector that we could add the project. Would you be interested to help out on this? We can obviously help you with this. Most likely it would use the Camel CXF component (https://camel.apache.org/components/latest/cxf-component.html)

[gaughan]

IMHO,
Not 0
Yes to 1
Not 2
3 maybe but not in the first version

[hodrigohamalho]

Hi @KurtStam,
0. No

1. Yes, about the authentication I think it could be implemented on-demand, right now the customers that I have been talking isn't using any authentication (internal WS).
2. Nice to be but not a must right now.

I can contribute but not lead this extension.

[christophd]

If it is just 1. for the moment without any WS specific authentication mechanism I wonder if we could just use the existing Http connector.

SOAP is nothing but Http POST requests with some specific SOAP envelope payload and some SOAP action header eventually. That should be doable with plain Http connector.

[KurtStam]

@christophd I think what we is being asked here something similar as the api-connector, where you give it a openapi document (in this case a soap-schema) like this: https://github.com/syndesisio/syndesis-quickstarts/tree/master/db-2-api-connector

[KurtStam]

@hodrigohamalho

I can contribute but not lead this extension.

Cool - we divi up the tasks once we identify them

[gaughan]

Yes similar to api client connector.
Auth should be included.

[zregvart]

So when we say authentication should be included, what do we mean by that? WS-Security support?

I think in the first go we should disregard any security means other than TLS and then see from the feedback what authentication mechanisms are used so we know what to implement.

[gaughan]

WS-Security username and password at a minimum I would think.

[heiko-braun]

@hodrigohamalho What use cases do you have in mind?

• Fuse Online SOAP Clients talking to external SOAP endpoints?
• External SOAP Clients invoking on Fuse Online?

[dhirajsb]

@tdiesler built a SOAP to REST bridge a little while ago for Camel. Perhaps we can leverage it here.