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) acts as a central component in application integration, offering a scalable architecture for seamless communication between disparate systems without requiring modifications to existing applications.ESB is essential for streamlining the interaction between multiple applications in an organization, acting as a middleware to connect and manage data exchanges effectively. Its architecture decouples systems, allowing integration across platforms, technologies, and...
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.