Dear all, Could anybody give some help with returning a soap fault with custom fault details (in the <details> tag in the SOAP Fault response) filled in? After browsing the fora and trying for some time, we are still trying to fill the details tag with some xml that is also used in one of our other webservices - thus we are trying to make things work by passing a cxf-generated class (wsdl2java) to the cxf fault handling code. JAXB throws an exception complaining that the passed in class nor any of its super classes is known to this context. To make things more clear:
Our customized interceptor that modifies the soap message: The passed in DetailFault class that wraps the bean containing the info to render the <detail> tag: Part of the stacktrace: I'm using JRebel to speed things up (thus changing classes and annotations on the fly) but there doesn't appear to be any caching involved so I don't think it is giving trouble. cxf 2.3.6 spring 3.0.5 java 1.5.0.22 JBoss 4.2.3 Things tried: - The FoutBerichtType is just a bean with two more beans with several fields in it, without using generics. Returning just an enum generated by wsdl2java caused the same error. - replacing @WebFault by @WebFault(name = "FoutberichtType", targetNamespace="http://ns.fazont.nl/operations/fout/v1";) caused the same error. - returning a java.lang.Object by getFaultInfo(). This caused the same error. I'm pretty sure I also saw something like, object not annotated with with @XmlRootElement which makes me wonder whether that may give trouble too, because FoutberichtType doesn't have @XmlRootElement on it. Your help is very much appreciated, Marc -- View this message in context: http://cxf.547215.n5.nabble.com/Throwing-a-custom-SOAP-Fault-tp5595222p5595222.html Sent from the cxf-user mailing list archive at Nabble.com.
