B) Use Oracle Service Bus or BPEL Process Manager and utilize the REST binding that is available for both. The REST binding will automatically translate a REST payload from JSON or XML to SOAP/XML for processing in the middleware layer.
A) Oracle Service Bus must be used. An HTTP proxy service is created and a pipeline is added with a conditional branch for each HTTP verb that the interface will serve. If there is any non-XML payload, such as JSON, an external parser service must be used to translate it to XML.
Haha, I bet the poor developer who has to implement this REST interface is going to feel like they're doing some serious 'SOA Suite-ing' to get it all working.
A) Oracle Service Bus must be used. An HTTP proxy service is created and a pipeline is added with a conditional branch for each HTTP verb that the interface will serve. If there is any non-XML payload, such as JSON, an external parser service must be used to translate it to XML.
I'm going with option D. Using the HTTP transport in OSB and then leveraging nXSD to handle the payload translation sounds like a clean, well-supported approach.
I agree, using the HTTP transport in Oracle Service Bus for REST interaction is a common practice. nXSD can definitely help with the JSON to XML translation.
I think option B is the best choice here. Using the REST binding in either Oracle Service Bus or BPEL Process Manager seems like the most straightforward way to handle the REST interface without having to worry about the payload translation.
Roslyn
1 months agoGearldine
5 days agoJutta
6 days agoCassie
17 days agoMozell
21 days agoWillow
1 months agoIvette
23 hours agoJerilyn
1 months agoJeanice
2 months agoRosendo
11 days agoAnissa
15 days agoLucina
22 days agoBlair
2 months agoStevie
16 days agoHayley
19 days agoRikki
26 days agoCaitlin
2 months agoHoney
4 days agoJunita
12 days agoAmina
15 days agoChristiane
1 months agoElin
2 months agoKristin
2 months agoElin
2 months agoErnie
2 months agoHui
2 months agoErnie
3 months ago