1 Reply Latest reply on Mar 29, 2006 11:06 AM by Robert

    Is this possible with JBoss Web services?

    Net Web Newbie

      Hi I am busy with a systems integration project.

      I have he following problem. Calling a SOAP web service running in jboss returns a raw roap response from the web service that contain"soapenv" xml tags and xml attributes as well as xmlns and xsi attributes. This is a proper SOAP response.

      My problem is this. The 3rd party software (which i can't change) has the facility to call soap calls and make the XML available to that 3rd party application. However that application can't understand the returned SOAP tags and xml descriptive attributes received with the XML data after calling a SOAP web service running in JBoss I described above.

      Is there a way to exclude the soap headers and/or those extra descriptive tags in a JBoss SOAP web service response in a config file or somewhere else?

      What I basically want is the plain xml returned like this:


      instead of this Code:

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Body soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
       <ns1:WSTransactionResponse xmlns:ns1="urn:SoapEsocket">
       <result href="#id0"></result>
       <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:WSTransactionMessage" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:SoapEsocket">
       <Field1> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xsd:string">1</Field1>

      Is this possible in XML?

      The SOAP call use to only return the simple XML data as given in the first example above (I wasn't working on the project at the time) so I have to figure out if the fact that it's not returning the non simple XML (with the SOAP headers and descriptive attributes) anymore is the fault of the
      a) Web Service
      b) JBoss change?
      c) 3rd party application change.

      Running JBoss 4.0.3