Yes, of course you can publish services with both a REST Connector and a SOAP Connector. It is not difficult, as Radhey and Scott say-
It can be problematic if you have a REST service that you want to use with SOAP and vice versa.
Why is this?
Simply because REST is tightly coupled with HTTP in its current implementations. Also, error handling with Rest is often associated with an HTTP return code (400, 401...), while SOAP ignores this kind of code.
I advise you to be careful when developing services and not to rely on the properties of the protocol.
Here is the advice I can give you to welcome you,
Paul
Search for a product comparison in Enterprise Service Bus (ESB)
Enterprise Service Bus (ESB) is a middleware solution facilitating the integration of various applications and services within an enterprise, promoting seamless data exchange and process automation.ESB serves as a communication backbone, providing a scalable and flexible architecture that integrates disparate systems, whether on-premises, in the cloud, or in hybrid environments. It enables standardized messaging across a multitude of platforms, reducing system complexity and improving...
Hello Sarasika,
Yes, of course you can publish services with both a REST Connector and a SOAP Connector. It is not difficult, as Radhey and Scott say-
It can be problematic if you have a REST service that you want to use with SOAP and vice versa.
Why is this?
Simply because REST is tightly coupled with HTTP in its current implementations. Also, error handling with Rest is often associated with an HTTP return code (400, 401...), while SOAP ignores this kind of code.
I advise you to be careful when developing services and not to rely on the properties of the protocol.
Here is the advice I can give you to welcome you,
Paul
Yes, we can expose and call REST and SOAP both using Oracle OSB service or EBS.
Yes, with webMethods it is fairly trivial. I would think the same would apply to other offerings as well.