ansaurus

Question

Answer 1

+3 A:

Did you try to annotate your exception with @WebFault? Also, do you implement getFaultInfo()?

EDIT: I realize my answer was maybe not detailed enough. As reminded in this thread (for example):

The JAX-WS 2.0 specification demands that the exception annotated with @WebFault must have two constructors and one method [getter to obtain the fault information]:
WrapperException(String message, FaultBean faultInfo)
WrapperException(String message, FaultBean faultInfo, Throwable cause)
FaultBean getFaultInfo()
The WrapperException is replaced by the name of the exception, and FaultBean is replaced by the class name that implements the fault bean. The fault bean is a Java bean that contains the information of the fault and is used by the Web service client to know the cause for the fault.

This is detailed in section 2.5 Fault of the JAX-WS specification. Does your exception conform to this? Can you post the code?

The OP is right. As per specification 2.1, section 3.7 Service Specific Exception, it is not required to use the @WebFault annotation, JAX-WS can generate the wrapper beans dynamically for exceptions that do not match the pattern described in section 2.5 (just provide a getter for the information you want to be present in the fault). For exceptions that match the pattern described in section 2.5 (i.e. exceptions that have a getFaultInfo method and @WebFault annotation), the FaultBean is used as input to JAXB when mapping the exception to XML Schema.

So the solution suggested above (matching the pattern described in section 2.5) is only a workaround. The generation of wrapper beans should just work for other exceptions. And I don't know why this fails here.

Pascal Thivent 2010-01-14 14:22:24

I did not. I tried that now, but I get the same error. But do I need to specify @WebFault's properties name, targetNameSpace and faultBean as well?

waxwing 2010-01-14 14:55:17

Thanks for the hint, I will look into it. No, I did not implement the constructors you indicated. I read (misread?) that part of the specification as the JAX WS implementation would *automatically generate* the exception wrapper itself with those constructors. I am beginning to think I am doing something backwards...

waxwing 2010-01-14 16:14:11

It turns out that conforming to the Exception style you wrote above means that JAX-WS will *not* create a wrapper bean for the exception, which it otherwise should. So that works as a workaround for me. However, it *should* work with all exceptions without annotations, according to "3.7 Service Specific Exception" in the spec.

waxwing 2010-01-14 17:05:00

Answer 2

A:

An addition to the answer above. I ended up with this as my InvalidInputException implementation:

@WebFault(faultBean = "com.mypackage.ws.exception.FaultBean")
public class InvalidInputException extends Exception {

    private static final long serialVersionUID = 1L;

    private FaultBean faultBean;

    public InvalidInputException() {
        super();
    }

    public InvalidInputException(String message, FaultBean faultBean, Throwable cause) {
        super(message, cause);
        this.faultBean = faultBean;
    }

    public InvalidInputException(String message, FaultBean faultBean) {
        super(message);
        this.faultBean = faultBean;
    }

    public FaultBean getFaultInfo() {
        return faultBean;
    }
}

And FaultBean is just a simple POJO with currently no data at all. Now, according to the JAX-WS specification (see 3.7 Service Specific Exception), it conforms to what is required of an exception annotated with @WebFault, so it will not create a wrapper bean for it, which probably is what was failing.

This is a decent workaround, but it does not explain the error in the question.

waxwing 2010-01-14 17:10:47

ansaurus

tags:

views:

answers:

JAX-WS - Map Exceptions to faults

related questions