Skip to Content
author's profile photo Former Member
Former Member

Error receiving XML

Hi gurus:

When I send the XML below using a SOAP communication Channel, XI server doesn't receive it well:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="" xmlns:soapenc="" xmlns:tns="urn:" xmlns:types="urn:" xmlns:xsi="" xmlns:xsd="">
	<soap:Body soap:encodingStyle="">
			<SolicitudCancelacionCitaType_1 href="#id1"></SolicitudCancelacionCitaType_1>
		<tns:SolicitudCancelacionCitaType id="id1" xsi:type="tns:SolicitudCancelacionCitaType">
			<cita href="#id2"></cita>
			<contexto href="#id3"></contexto>
			<paciente href="#id4"></paciente>
		<soapenc:Array id="id2" soapenc:arrayType="tns:CitaType[1]">
			<Item href="#id5"></Item>
		<tns:ContextoType id="id3" xsi:type="tns:ContextoType">
			<aplicacion href="#id6"></aplicacion>
			<mensajeID xsi:type="xsd:string">2957</mensajeID>
			<mensajeRaizID xsi:type="xsd:string">2955</mensajeRaizID>
			<origen href="#id7"></origen>
		<tns:PacienteType id="id4" xsi:type="tns:PacienteType">
			<CIP xsi:type="xsd:string">556041699</CIP>
		<tns:CitaType id="id5" xsi:type="tns:CitaType">
			<id xsi:type="xsd:string">1103886</id> 
			<sujeto href="#id8"></sujeto>
		<tns:ContextoType.AplicacionType id="id6" xsi:type="tns:ContextoType.AplicacionType">
			<nombre xsi:type="xsd:string">TELECITA</nombre>
			<version xsi:type="xsd:string">1.0</version>
		<tns:ContextoType.OrigenType id="id7" xsi:type="tns:ContextoType.OrigenType">
			<centro href="#id9"></centro>
		<tns:CitaType.SujetoType id="id8" xsi:type="tns:CitaType.SujetoType">
			<CIP xsi:type="xsd:string">125041699</CIP>
		<tns:ContextoType.OrigenType.CentroType id="id9" xsi:type="tns:ContextoType.OrigenType.CentroType">
			<codigo xsi:type="xsd:string">9912023710</codigo>
			<nombre xsi:type="xsd:string">C.S. SAN SEBASTIAN G.</nombre>
			<sistemaCodificacion xsi:type="xsd:string">TELECITA</sistemaCodificacion>

Using Altova XMLSpy, previous XML code is valid and well-formed, but XI server only receives next XML code (in SXMB_MONI):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Inbound Message -->
<tns:cancelaCitas xmlns:tns="urn:" xmlns:xsd="" xmlns:soapenc="" xmlns:types="urn:" xmlns:xsi="" xmlns:soap="">
	<SolicitudCancelacionCitaType_1 href="#id1"></SolicitudCancelacionCitaType_1>

The structure of the XML code that I send to server is a little peculiar, with references to items that appear below.

Any idea?

Thanks to all in advance and regards,

Alejandro Gomez.

Edited by: Alejandro Gómez on Mar 17, 2009 10:19 AM

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Mar 17, 2009 at 11:46 AM

    Hi Alejandro Gomez,

    Double check if your XML is valid.

    I doubt if you need to have the first line of your payload.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 17, 2009 at 11:46 AM

    This format is not supported.

    The SOAP adapter only supports one body root node.

    As work around, you can use the flag "Du not use SOAP envelope" and do

    mapping based on the full SOAP message (including envelope)

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 17, 2009 at 11:47 AM


    You had used the imported the wsdl as External defination with sender SOAP adapter.

    plesae can you check the referece available in the imported wsdl are fine or not.

    Just try to again use the same wsdl in mapping object and see if you are able to all fields.

    The namespace reference seems to be missing.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.