Oracle FMW - Exposing a SOAP WS with explicit header (multiple parts) as REST

SOAP messages may have multiple parts, located either in the SOAP message body or in the SOAP message headers.

Oracle FMW supports exposing SOAP WS with a single part as REST, but does not support exposing SOAP WS with multiple parts as REST.
In the latter case, JDeveloper BPM Studio recommends to use some mediator component which will be used to transform the multipart SOAP message into a single part one, then exposing this single part service.

This is of course not as elegant as to immediately expose the multipart service, yet it provides a not too complex technical solution to an issue which is probably due to concepts mismatch.

I guess the real issue lies in the fact that a message part may have arbitrary complex contents, may be placed inside the SOAP header and that there is no real corresponding header-place in HTTP for such complex structures as a SOAP message part.  Thus Oracle probably decided not to decide how to handle this situation, and to let the developers choose by themselves, which is also good.

Nevertheless, I believe the ideal solution would have been to support two ways to do it:

• The current one, where the developer chooses how to handle multiple SOAP message parts
• A second one, where Oracle would by default create a list of JSON parts in the HTTP payload, so that the developer would not be obliged to handle each single case using an additional mediator component.