OSB - Handling multiRef responses?

Question

I have to connect to an Axis webservice which forces multiRef.
Does anyone have suggestions for working with the response? Is there any Oracle tools which will help here so I can properly use XPath?
(I've also noticed behavior difference between Service Callout and Route, shown below)
*Here is what OSB gets in the body coming back from Proxy Service Route to the business service:*
<ns1:getHeaderResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://bd.ews.xxxxx.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<getHeaderReturn href="#id0"/>
</ns1:getHeaderResponse>
*Yet here is the SOAP response when I test the Business Service directly or call it via Proxy Service Service Callout*:
     <soapenv:Body>
     <ns1:getHeaderResponse      soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://bd.ews.xxxxx.com">
     <getHeaderReturn      href="#id0"/>
     </ns1:getHeaderResponse>
     <multiRef      id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:DealHeader" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ews-structs">
     <agent_deal_fl      xsi:type="xsd:string">N</agent_deal_fl>
     <attach_fl      xsi:type="xsd:string">N</attach_fl>
     <bd_id      xsi:type="xsd:string">5449DDF</bd_id>
     <bd_version_nr      xsi:type="xsd:int">1</bd_version_nr>
     <beg_dt      xsi:type="xsd:string">16-Jul-2010 00:00</beg_dt>
     <end_dt      xsi:type="xsd:string">30-Sep-2011 00:00</end_dt>
<!---- snip --->
</multiRef>
</soapenv:Body>
I also found this thread stating SOA/BPEL team does not support it -- hoping Aqualogic did provide some type of support...
About multiRef

Answer 1

Anuj Dwivedi wrote:
I could successfully get the value of bd_version_nr using below expression -
Assign [ $body/multiRef/bd_version_nr/text() ] to [ var1 ]The limitation and problem here is if I had multiple multiRef responses. I don't want to hard-code id0 as its dynamic. See below for example. It would be easiest if OSB would sort out appropriate multiRef structures since it knows the schema already.
example:
+<soapenv:Body>+
+<ns1:getHeaderResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://bd.ews.xxxxx.com">+
*+<getHeaderReturn href="#id0"/>+*
*+<getHeaderExtensions href="#id1"/>+*
+</ns1:getHeaderResponse>+
+<*multiRef id="id0"* soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:DealHeader" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ews-structs">+
+<agent_deal_fl xsi:type="xsd:string">N</agent_deal_fl>+
+<attach_fl xsi:type="xsd:string">N</attach_fl>+
+<bd_id xsi:type="xsd:string">5449DDF</bd_id>+
*+<bd_version_nr xsi:type="xsd:int">1</bd_version_nr>+*
+<beg_dt xsi:type="xsd:string">16-Jul-2010 00:00</beg_dt>+
+<end_dt xsi:type="xsd:string">30-Sep-2011 00:00</end_dt>+
+<!---- snip --->+
+<*multiRef id="id1"* soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:DealHeader" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ews-structs">+
*+<bd_version_nr xsi:type="xsd:int">1</bd_version_nr>+*
+<extra elements />+
+<!---- snip --->+
+</multiRef>+
+</soapenv:Body>+
Anuj Dwivedi wrote:
As far as I know, you can convert the multiref xml to normal structure using XSLT or similar conversion technologies but I have never tried this. It's an interesting use case and I would at least try it once at my end.I will try it when I get time. Are you saying that you are also going to try it yourself?
Edited by: jjhowey on Oct 7, 2010 10:25 AM
Edited by: jjhowey on Oct 7, 2010 10:28 AM
Edited by: jjhowey on Oct 7, 2010 10:29 AM