how does path mapping work in xml-to-domain ?

I have a microflow with a '├žall webservice' action. When activating tracing/debugging I found out that the request was build perfectly, and I even received the soap-response. In the microflow I implemented an error handling on the CWS, but this is never called. But after the CWS action, my entities are never filled with data. When I activate WSDL/XSD validation, a runtime error is raised Error occurred while parsing xml: cvc-elt.1: Cannot find the declaration of element 'SOAP-ENV:getSignalsResponse'. org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'SOAP-ENV:getSignalsResponse'. at The strange thing is, if I take a look at the XML-2-DOMAIN mapping, in the property pane you can see the path mapping. When I test the same XML-result in XMLSpy and the XPATH evaluation, XMLSpy returns the expected values. Eg. XPATH evaluation /Body/getSignalsResponse/getSignalsReturn/Signalen/Oversluitingen/Oversluiting/Naam At the end of this message there is a snippet of the response Questions - if the X2D mapping did not find anywhing, why is n't there an error raised in the CWS ? - According the WSDL/XSD validation SOAP-ENV:getSignalsResponse can not be found. It is in the response, but within the WSDL/XSD it is not mapped to any namespace. Does the X2D mapping use namespaces ? Or does the mapping only search to element-names like mentioned in the property pane of the entities mapping. - Does anybody have a tric or solution to solve this issue ? I'm in uregent need of this data in the app Response message received in Tube [ MesageDumpingTube ] Instance [ 1 ] Engine [ Metro/2.1 (branches/2.1-6728; 2011-02-03T14:14:58+0000) JAXWS-RI/2.2.3 JAXWS/2.2: Stub for ] Thread [ ]: <?xml version='1.0' encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:ns1=""> <SOAP-ENV:Header> <ns1:loginHeader xmlns:SOAP-ENV="" xmlns:ns1="">Login als m.dbokx</ns1:loginHeader> </SOAP-ENV:Header> <SOAP-ENV:Body> <SOAP-ENV:getSignalsResponse> <getSignalsReturn> <ns1:Signalen> <ns1:Oversluitingen> <ns1:Oversluiting> <ns1:HypotheekbondId>9376402</ns1:HypotheekbondId> <ns1:ExternId /> <ns1:AdviseurNaam>de Bokx</ns1:AdviseurNaam> <ns1:Naam>Testpersoon</ns1:Naam> <ns1:Hoofdsom>225000</ns1:Hoofdsom> <ns1:Boete>25680.61</ns1:Boete> <ns1:VerschilPerMaand>-284.11</ns1:VerschilPerMaand> <ns1:VerschilRvp>-3392.06</ns1:VerschilRvp> <ns1:Terugverdientijd>59</ns1:Terugverdientijd> <ns1:Flags /> </ns1:Oversluiting> <ns1:Oversluiting> <ns1:HypotheekbondId>9376436</ns1:HypotheekbondId> <ns1:ExternId /> <ns1:AdviseurNaam>de Bokx</ns1:AdviseurNaam> <ns1:Naam>testrelatie</ns1:Naam> <ns1:Hoofdsom>225000</ns1:Hoofdsom> <ns1:Boete>5509.91</ns1:Boete> <ns1:VerschilPerMaand>-120.49</ns1:VerschilPerMaand> <ns1:VerschilRvp>-3192.18</ns1:VerschilRvp> <ns1:Terugverdientijd>36</ns1:Terugverdientijd> <ns1:Flags /> </ns1:Oversluiting> </ns1:Oversluitingen> snippet of WSDL/WSD <xsd:element name="getSignalsResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="getSignalsReturn"> <xsd:complexType> <xsd:sequence> <xsd:element name="Signalen"> <xsd:complexType> <xsd:sequence> <xsd:element name="Oversluitingen" minOccurs="0"> <xsd:complexType> <xsd:sequence> <xsd:element name="Oversluiting" minOccurs="1" maxOccurs="unbounded"> <xsd:complexType> <xsd:sequence> <xsd:element name="HypotheekbondId" type="xsd:integer"/> <xsd:element name="ExternId" type="xsd:string"/> <xsd:element name="AdviseurNaam" type="xsd:string"/> <xsd:element name="Naam" type="xsd:string"/> <xsd:element name="Hoofdsom" type="xsd:double"/> <xsd:element name="Boete" type="xsd:double"/> <xsd:element name="VerschilPerMaand" type="xsd:double"/> <xsd:element name="VerschilRvp" type="xsd:double"/> <xsd:element name="Terugverdientijd" type="xsd:integer"/>
1 answers

Does your request body validate against the WSDL and is the WSDL mapping valid? Try using SoapUI to validate both like Dirk Blaauw suggested.