OSB input payload with characters ' ' ' ' fails service invoke

Question

Hi,
In OSB I am calling a USM service to search the contents. Created a Business Service out of USM Search WSDL and then a proxy service which calls the business service. When I am trying to test the service through SOAP UI with the below payload I get an error: *<faultstring>Error parsing the XML resource. The tag 'contains' has not been properly closed. Instead, the tag 'sear:queryText' was encountered.</faultstring>*
and when I run the same payload through OSB test console get an error:
The XML document is not well-formed:
error: </sear:queryText> does not close tag <contains>.
The same works in SOA Process but in OSB
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.stellent.com/Search/">
   <soapenv:Header/>
   <soapenv:Body>
      <ns1:AdvancedSearch>
         <ns1:queryText>(xIdcProfile<matches>`xxAB`)<AND>(x_ID<contains>`13-AZXX001-TST`)</ns1:queryText>
         <ns1:sortField>dInDate</ns1:sortField>
         <ns1:sortOrder>DESC</ns1:sortOrder>
      </sear:AdvancedSearch>
   </soapenv:Body>
</soapenv:Envelope>Now if I replaced *<* with *&lt;* and *>* with *&gt;* it works fine.
the below payload just works fine
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.stellent.com/Search/">
   <soapenv:Header/>
   <soapenv:Body>
      <ns1:AdvancedSearch>
         <ns1:queryText>(xIdcProfile&lt;matches&gt;`xxAB`)&lt;AND&gt;(x_ID&lt;contains&gt;`13-AZXX001-TST`)</ns1:queryText>
         <ns1:sortField>dInDate</ns1:sortField>
         <ns1:sortOrder>DESC</ns1:sortOrder>
      </sear:AdvancedSearch>
   </soapenv:Body>
</soapenv:Envelope>But the consumers of this service pass the data in this format *(xIdcProfile<matches>`xxAB`)<AND>(x_ID<contains>`13-AZXX001-TST`)* only. How do I make sure OSB takes in this format payload and executes it properly.
As the same thing works in Oracle SOA Process but in OSB it just chokes out. Any help is appreciated.
Thanks

Answer 1

Like others mentioned, the XML which your service consumer is sending is not a valid XML because of the special characters and you need to escape them.
1. The best way is to ask the service consumer to send a proper XML with any special characters put in a CDATA section or escaped.
2. If above is not possible, then you need to make sure that your first Proxy service which receives the message from service consumer is of Messaging type with text as input message format. AnyXML,AnySOAP or WSDL based services will error out because these types of services expect a proper valid XML document as input.
So in the messaging type service, you read the input message as text and then use the fn-bea:inlined-XML() and fn-bea:serialize() functions or CDATA to create a valid XML from the text input and pass this XML to your business service.