URGENT: SOAP 1.1 and 1.2 Support in OSB Proxy

Question

Gurus,
My OSB proxy services should support SOAP 1.1 and 1.2 versions. However, WSDL based Proxy service has only one endpoint. (This is the limitation as per an Oracle document.) This endpoint is one which you select while creating a proxy service from WSDL.
Now, as a result, the service is not able to serve both the 1.1 and 1.2 requests.
As a workaround, I've created two proxy services from the same WSDL (which has both the endpoints/bindings).
And, i publish two endpoints to the user.
Is there any way to trick the proxy WSDL (effective WSDL) to have two ports (endpoints) in it ?
If not, what are the best practices to tackle this situation?
Thanks in advance for your help on this.
With regards-
Ashish
Edited by: user570355 on 2012. 9. 24 오후 3:47

Answer 1

Hi Ashish,
I don't think there's a way to trick the proxy but, as you know, soap 1.1 and 1.2 have slightly different envelope formats (e.g. fault handling) so you'll probably need some kind of specific message processing or transformation, sometime in the future, for handling both soap 1.1 and soap 1.2 requests. This makes your approach correct, in my opinion.
Do you have a local proxy for handling service logic?
I think you should follow something similar to this: http://docs.oracle.com/cd/E23943_01/dev.1111/e15866/local.htm#i1075772.
Your minimum configuration - 3 proxies:
SOAP 1.1 Proxy, SOAP 1.2 proxy and a Local Proxy
Using this approach:
*1 -* The Local Proxy should handle Business Service calls, additional logic, etc. You'll probably have to configure this as "Any XML" proxy and use some kind of internal message format (your own schema) because, if you configure it as "Any SOAP", you'll be forced to choose between SOAP 1.1 and SOAP 1.2.
- routes responses from Business Services to the correct SOAP 1.x Proxy
*2 -* For each SOAP 1.x Proxy
- receives soap 1.x messages and transforms them to some kind of internal schema -> routes them to the Local Proxy for processing
- transforms any kind of responses coming from the Local Proxy back to soap 1.x format and routes responses to the client
I hope this can be of any help to you,
Regards,
Filipe