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

Missing fault detail in messages from SLSB Provider

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jbossws-2.0.2
    • None
    • None
    • None

      Hello!

      I can't get the detail element of the SOAPFault. Is there a magic way to do this. I have a Provider< SOAPMessage > implementation. When I do the following ...
      Code:

      @Local
      @Stateless
      @WebServiceProvider(
      serviceName = "MyService",
      portName = "MyServiceSoap11Port",
      targetNamespace = "http://my.service.com/something",
      wsdlLocation = "META-INF/wsdl/my-service.wsdl")
      @ServiceMode(value = Service.Mode.MESSAGE)
      public class MyServiceEndpointProvider implements Provider<SOAPMessage> {

      public SOAPMessage invoke(SOAPMessage requestSoapMessage)

      { ... SOAPFault theSOAPFault = SOAPFactory.newInstance().createFault(); Detail soapFaultDetail = soapFault.addDetail(); SOAPElement myFaultElement = soapFaultDetail.addChildElement(new QName("http://my.service.com/common-ws/types", "myFault")); SOAPElement myCodeElement = myFaultElement.addChildElement(new QName("http://my.service.com/common-ws/types", "code")); myCodeElement.setNodeValue("SC_BAD_REQUEST"); SOAPElement myMessageElement = myFaultElement.addChildElement(new QName("http://my.service.com/common-ws/types", "message")); myMessageElement.setNodeValue("This is a faked error"); throw new SOAPFaultException(theSOAPFault) ... }

      }

      ... the detail part of the fault is missing, i.e. the serialized response does not contain my detail information, just the top fault element. Am I missing something obvious here or is it a bug. I'm using JBoss 4.2.1.GA with JBossWS 2.0.1.GA. And yes, my wsdl points out a fault element specifying the detail above.

              rhn-support-asoldano Alessio Soldano
              tdiesler@redhat.com Thomas Diesler
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: