Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2184

SOAP 1.2 Endpoint - Faults Marshalled as SOAP 1.1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • jbossws-2.0.1.SP2
    • jbossws-native
    • None

      For a JAX-WS endpoint deployed with a @BindingType to specify SOAP 1.2 the request and response are marshalled as SOAP 1.2, however faults are marshalled as SOAP 1.1 e.g.

      Request: -

      <env:Envelope xmlns:env='http://www.w3.org/2003/05/soap-envelope'>
      <env:Header/>
      <env:Body>
      <ns3:lookup xmlns:ns2='http://www.jboss.org/support/phonebook/types' xmlns:ns3='http://www.jboss.org/support/phonebook'>
      <ns2:arg0>
      <firstName>Darran</firstName>
      <surname>Lofthouse</surname>
      </ns2:arg0>
      </ns3:lookup>
      </env:Body>
      </env:Envelope>

      Response: -

      <env:Envelope xmlns:env='http://www.w3.org/2003/05/soap-envelope'>
      <env:Header/>
      <env:Body>
      <ns3:lookupResponse xmlns:ns2='http://www.jboss.org/support/phonebook/types' xmlns:ns3='http://www.jboss.org/support/phonebook'>
      <ns2:return>
      <areaCode>12345</areaCode>
      <number>123456</number>
      </ns2:return>
      </ns3:lookupResponse>
      </env:Body>
      </env:Envelope>

      Fault: -

      <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
      <env:Header/>
      <env:Body>
      <env:Fault xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
      <faultcode>env:Server</faultcode>
      <faultstring>Oops!</faultstring>
      <detail>
      <ns2:PhoneBookException xmlns:ns2='http://www.jboss.org/support/phonebook'>
      <message>Oops!</message>
      </ns2:PhoneBookException>
      </detail>
      </env:Fault>
      </env:Body>
      </env:Envelope>

              darran.lofthouse@redhat.com Darran Lofthouse
              darran.lofthouse@redhat.com Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: