[NOTE] Adding xsi type to SOAP messages

Question

Here is a quick 2.0.10 note.
Some older SOAP stack require xsi type information embedded in the SOAP message to unmarshall the XML message into the appropriate object representation.
Most customers do no want the overhead of xsi type definition into the SOAP message given that most modern SOAP stack perform the unmarshalling based on the WSDL/XML Schema.
To address both requirements, we now by default do not add the xsi:type information to the SOAP traffic that the BPEL PM server generates.
But we have added a new configuration property to the partnerLinkBinding element of the bpel.xml deployment descriptor so that you can ask the BPEL PM server to selectively decorate the SOAP messages targeted at a specific partnerLink. Here is how this looks like:
<partnerLinkBinding name="XXXXX">
<property name="sendXSIType">true</property>
</partnerLinkBinding>
Note: the challenge here is that if you invoke a service that requires XSI type information and you forget to set that flag in the deployment descriptor you will get a BindingFault with no detail :-( We are very aware of this limitation and are working very diligently towards addressing this problem with a much nicer error message in the 2.1 (aka end of September release).
Edwin

Answer 1

Hi,
thanks for the quick answers.
The Werbservice is MS CRM Dynamics. The "GUI" is still working. so the webservice is active and alive.
I want to query the CRM, so i sent a fetch statement to file, which is being picked up and sent as SOAP message to the webservice.
With point 6 in the mentioned blog the error message in the rwb is gone now, but the message in SXMB_MONI is flagged red and i'm struggling to finfd out what the next error is....may be someone can point out where to look at