I have a set of exceptions in package org.foo.exceptions which I'm using in a Service residing in package org.foo.bar.Service.
I generated exception beans and placed them in package org.foo.exceptions.jaxws. When I use the @WebFaultAnnotation to point to these fault beans, cxf throws the following error: org.apache.cxf.interceptor.ClientFaultConverter - Exception occurred while creating exception: org.foo.exceptions.DoesNotExistException.<init>(java.lang.String, org.foo..exceptions.jaxws.DoesNotExistExceptionBean) java.lang.NoSuchMethodException: org.foo.exceptions.DoesNotExistException.<init>(java.lang.String, org.foo.exceptions.jaxws.DoesNotExistExceptionBean) I don't understand why this constructor is necessary in the exception class? Using @WebFault with jaxws metro implementation did not require this constructor. If I get rid of the @WebFault, CXF is happy. Metro, however, dynamically generates org.foo.bar.jaxws.DoesNotExistExceptionBean rather than using org.foo.exceptions.jaxws.DoesNotExistExceptionBean. I could not determine if CXF was also dynamically generating an exception bean in this scenario. -- View this message in context: http://www.nabble.com/Exception-Beans-and-%40WebFault-tp21838049p21838049.html Sent from the cxf-user mailing list archive at Nabble.com.
