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?
6 days ago, 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.
2 days ago, 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.
Custom DB-queries as connector? 1 Answer
Connector icon template 1 Answer