Why do we have SOAP connect option while creating a connector when we already have a Web Service Consumer connector? We can configure a wsdl with Web Service Consumer and access a web service. What is the difference between the two options?
Feb 22 at 09:53 AM, George Jeffcock answered with:
Adding to Swapnil answers I would say Nehe you might be missing the use cases of SOAP connect and bespoke connectors in general
SOAP Connect allow an architect/lead/developer to take the drudgery out of consuming a service by filtering operations for example.
This is why: https://www.mulesoft.com/exchange/#!/?types=WSDL which will have been created by DevKit.
You can look at SOAP Connect as a method of re-use..site best practice...knowledge transfer...speed of development...reduce bugs on consumption...
When to Use DevKit - mule-cookbook-tutorial Here are several scenarios in which you may want to build your own connector:
You need to consume an API in one or more applications and you want to make sure everyone uses the same component.
You have an API and want to add strategic value to your business by providing a connector and telling the world "I am part of Mule Platform".
You want to facilitate integration with SaaS and on-premise Web services, applications, and data sources.
The API you consume supports Pagination, Batch, and/or has a SQL capability.
The API you consume has different entity types and/or its structure can change.
You want to extend Mule core.
Feb 18 at 07:50 AM, Swapnil Sahu answered with:
Hi, With Web Service Consumer we have to call each API separately in separate flows. With SOAP Connect, you can package multiple WSDL files and API versions into a single connector, making the process of creating, maintaining and using a connector for SOAP APIs much faster and easier.
Mar 06 at 06:38 AM, Jitendra Bafna answered with:
SOAP connect is used to turn your WSDL into connector quickly. You can achieve re usability out of that.
CXF is a Java web services framework used for SOAP (Simple Object Access Protocol) messaging. It handles all serialization and deserialization as well as SOAP envelope and namespace processing.
Web Service Consumer is used to consume Soap based web service or WSDL.
For more details on consuming Rest and Soap Web service you can find on below articles.
https://dzone.com/articles/consuming-soap-based-web-service-and-raml-based-re https://dzone.com/articles/how-to-consume-restful-web-service-with-mulesoft-a https://dzone.com/articles/how-to-add-raml-based-api-to-anypoint-exchange-and
May 09 at 06:07 PM, Divya Chandaluru answered with:
"Why do we have SOAP connect option" because MuleSoft want to provide a method for ISV to provide connectors to new and existing endpoints without Mulesoft themselves having to create them. Mulesoft Anypoint Platform success is built on the premise of connecting to anything and therefore SOAP Connect helps this.
Secondly connecting to a using WSDL location for consuming a soap web service involves a developer to know the service pretty well and therefore allowing error and interpretation errors but if you internally create a connector you can reduce implementation time and errors.
Thirdly on WSDL there are often many methods not applicable or and an enterprise does not want to consume and therefore a connector can filter these methods.
Connectors = Re-Use
Web Service Consumer connector = manual process
Custom DB-queries as connector? 1 Answer
Connector icon template 1 Answer