Difficulty in a Oracle SOA web-service with 2 message parts

Question

Hi,
I am developing a web-service which should take 2 inputs - a string and a datetime. Also I have an xsd which I am importing into the wsdl to define the message elements.
I have 2 options to do this:
Option-1: Bundle these 2 input parameters into a single complex type in the xsd and then expose this complex-type as a single message part in the input message element. The wsdl operation tag then looks something like this:
+<wsdl:message name="RetrieveLoVRecordsRequest">+
+<wsdl:part name="part1" element="inp1:LoVInput"/>
+</wsdl:message>+
Option-2: Put these both these simple-types (the string & datetime inputs) in separate message parts. So wsdl operation looks like:
+<wsdl:message name="RetrieveLoVRecordsRequest">+
+<wsdl:part name="part1" element="inp1:LoVName"/>+
+<wsdl:part name="part2" element="inp1:LoVEffectiveDate"/>+
+</wsdl:message>+
I need 2 wsdl interfaces with one with option-1 & other with option-2
The web-service works fine in option-1. But for strange reason does not work correctly for option-2.
In option-2 the 1^st^ difficulty was that after I coded the wsdl in jdeveloper and did not attach an explicit binding to it, the message-part part2 does not show-up at all in the enterprise manager when I go to the web-service test page. When opened the WSDL URL in the browser it indicated that the SOAP sytle/encoding as Document/literal. Perhaps that's what it dafults to when no explicit binding is specified. I got around this problem by explicitly specifying a RPC/literal binding in the WSDL in jdeveloper. This then showed-up the 2 parts distinctly in the EM test console.
The 2^nd^ problem (which the main problem now) was that the web-service now started failing complaining about xsl transformation in the mediator
+ORAMED-01201:[Error in transform operation]Error occurred while transforming payload using "{0}" for target part "{1}".Possible Fix:Review the XSL or source payload. Either the XSL defined does not match with the payload or payload is invalid.+
Strangely I have correctly mapped the input & output parameters and the xsl is very simple having the 2 input parameters on the left being mapped to 2 corresponding parameters for the SQL where clause.
And when I went to the EM dashboard to inspect the failure, the input payload did not show any input being passed to the xsl transform in the mediator. This is how the input looks
+<message>+
+<properties>+
+<property name="tracking.compositeInstanceId" value="80053"/>+
+<property name="tracking.ecid" value="f2d97d6a53d56c9f:-58326bb8:13e15e68aab:-8000-000000000000113d"/>+
+<property name="transport.http.remoteAddress" value="10.110.173.159"/>+
+</properties>+
+<parts/>+
+</message>+
As you see above, the parts tag is blank; where it should contain part1 & part2
To summarise, when I add an RPC/literal binding to the WSDL the input to the wsdl seems to get chopped off !
Looking fwd to your help.
-Sudripta
Edited by: Sudripta on Apr 17, 2013 8:55 PM
Edited by: Sudripta on Apr 17, 2013 9:05 PM

Answer 1

Hi Boatseller,
I will put this in simple way.
Can we set properties in biztalk wcf_custom adaptor like 
1. <security authenticationMode="UserNameOverTransport" 
2. enableUnsecuredResponse="True" 
or 
 includeTimestamp="false"
3. <textMessageEncoding
messageVersion="Soap11"/>
<httpsTransport/>
I am unable to find these properties in BizTalk wcf_custom adaptor properties. It will be great help if you could guide me in right direction . My problem is to receive response message into orchestration which is not having header. But the response is coming
from web service. I saw that in fiddler.
Also, If there is any steps to make these properties available in machine config, please share 
Thanks in advance
Vivek