Databases
StackOverflow2013
Postsdbo
POError Invalid content was found starting with element . No child element is expected at this point
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError Invalid content was found starting with element . No child element is expected at this point
    primarykey
    data
    text
    <p>I have an error with my web service. The error is :</p> <blockquote> <p>Invalid content was found starting with element 'callerNumber'. No child element is expected at this point.</p> </blockquote> <p>The service send the object RelationCARO contains 3 strings : caName, roName and callerNumber (optional).</p> <p>When callerNumber is NULL, it works, and when callerNumber is not NULL, I have the above error.</p> <p>When I try to call the service with soapUI, it works even with callerNumber.</p> <p>The WSDL :</p> <pre><code>&lt;?xml version='1.0' encoding='UTF-8'?&gt;&lt;wsdl:definitions name="RMDManagementService" targetNamespace="http://ws.mom.rmd.atos.net/ws" xmlns:ns1="http://cxf.apache.org/bindings/xformat" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ws.mom.rmd.atos.net/ws" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt; &lt;wsdl:types&gt; &lt;xs:schema elementFormDefault="unqualified" targetNamespace="http://ws.mom.rmd.atos.net/ws" version="1.0" xmlns:tns="http://ws.mom.rmd.atos.net/ws" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt; &lt;xs:element name="createRelationCaRo" type="tns:createRelationCaRo" /&gt; &lt;xs:element name="createRelationCaRoResponse" type="tns:createRelationCaRoResponse" /&gt; &lt;xs:complexType name="createRelationCaRo"&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="relationCaRo" type="tns:relationCaRo" /&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="relationCaRo"&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="caName" type="xs:string" /&gt; &lt;xs:element minOccurs="0" name="roName" type="xs:string" /&gt; &lt;xs:element minOccurs="0" name="callerNumber" type="xs:string" /&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="createRelationCaRoResponse"&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="return" type="tns:relationCaRoFeedback" /&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:complexType name="relationCaRoFeedback"&gt; &lt;xs:sequence&gt; &lt;xs:element minOccurs="0" name="caName" type="xs:string" /&gt; &lt;xs:element minOccurs="0" name="roName" type="xs:string" /&gt; &lt;xs:element minOccurs="0" name="statusReturnCode" type="tns:statusReturnCodeEnum" /&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;xs:simpleType name="statusReturnCodeEnum"&gt; &lt;xs:restriction base="xs:string"&gt; &lt;xs:enumeration value="CDE_RMD000" /&gt; &lt;xs:enumeration value="CDE_RMD001" /&gt; &lt;xs:enumeration value="CDE_RMD300" /&gt; &lt;xs:enumeration value="CDE_RMD303" /&gt; &lt;xs:enumeration value="CDE_RMD304" /&gt; &lt;/xs:restriction&gt; &lt;/xs:simpleType&gt; &lt;/xs:schema&gt; &lt;/wsdl:types&gt; &lt;wsdl:message name="createRelationCaRo"&gt; &lt;wsdl:part element="tns:createRelationCaRo" name="parameters"&gt; &lt;/wsdl:part&gt; &lt;/wsdl:message&gt; &lt;wsdl:message name="createRelationCaRoResponse"&gt; &lt;wsdl:part element="tns:createRelationCaRoResponse" name="parameters"&gt; &lt;/wsdl:part&gt; &lt;/wsdl:message&gt; &lt;wsdl:portType name="RMDManagement"&gt; &lt;wsdl:operation name="createRelationCaRo"&gt; &lt;wsdl:input message="tns:createRelationCaRo" name="createRelationCaRo"&gt; &lt;/wsdl:input&gt; &lt;wsdl:output message="tns:createRelationCaRoResponse" name="createRelationCaRoResponse"&gt; &lt;/wsdl:output&gt; &lt;/wsdl:operation&gt; &lt;/wsdl:portType&gt; &lt;wsdl:binding name="RMDManagementServiceSoapBinding" type="tns:RMDManagement"&gt; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt; &lt;wsdl:operation name="createRelationCaRo"&gt; &lt;soap:operation soapAction="" style="document" /&gt; &lt;wsdl:input name="createRelationCaRo"&gt; &lt;soap:body use="literal" /&gt; &lt;/wsdl:input&gt; &lt;wsdl:output name="createRelationCaRoResponse"&gt; &lt;soap:body use="literal" /&gt; &lt;/wsdl:output&gt; &lt;/wsdl:operation&gt; &lt;/wsdl:binding&gt; &lt;wsdl:service name="RMDManagementService"&gt; &lt;wsdl:port binding="tns:RMDManagementServiceSoapBinding" name="RMDManagementSOAPPort"&gt; &lt;soap:address location="http://...../RMDManagementService" /&gt; &lt;/wsdl:port&gt; &lt;/wsdl:service&gt; &lt;/wsdl:definitions&gt; </code></pre> <p>On the client side, I generated all classes with wsdl2java.</p> <p>I don't understand the problem, because there are only 3 strings, and no children in parameter.</p> <p>Thank you for your help.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USuser2007861
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload