To expose a SOAP web service, an interface is typically created and implemented by a Java class containing the business logic. However, this document shows that a SOAP service can be exposed without implementing an interface by deleting the "method" invocation property in Mule, allowing the Java class to function without directly implementing the interface. Testing in SOAPUI confirms the service runs successfully.

1. Expose Web Service

2. To expose a SOAP web service we generally create an interface and then implement the interface
with a JAVA class.
The JAVA class is responsible for implementing the web service with the business logic

3. Let us consider we have exposed our SOAP web service in the following way:-

4. The corresponding Mule flow will be as follows:-
Now, you can see that I have used delete-message-property key="method“
This is the main trick .. To delete the invocation scoped property method
This will lead to expose a SOAP service without implementing the interface

5. Let’s check our interface Test :-

6. Now, we will also check our JAVA class implementing the business rules in the web service, You can
see that this JAVA class is not implementing the interface Test:-

7. Now, if we test the web service in SOAPUI we will see that the service is running successfully and
generating the response !!!-

8. In my next slide I will bring some other techniques in Mule implementation .
Hope you have enjoyed this simpler version.
Keep sharing your knowledge and let our Mule community grow 