Ok i also recognized this, but still no detail filled as far as i can see. I will attach these two generated classes to this thread.
Thanks in advance. Daniel http://www.nabble.com/file/p25076143/ForetagServiceInterface.java ForetagServiceInterface.java http://www.nabble.com/file/p25076143/Systemfel.java Systemfel.java Lukasz Lichota wrote: > > You use data binding server implementation (not @WebServiceProvider) > right? > so you should have three classes generated that extends > java.lang.Exception (one per fault) and your operation will declare them > (throws), these classes are annotated with @WebFault (i'm not sure it this > annotation needs to be repeated on the interface), > so in your interface implementation class you just throw the exception of > the certain type and details in soap message are properly filled (at least > it worked for me with one exception), is that what is not working? > > can you show generated exception class and interface/portType? > > > forda wrote: >> >> Have anyone looked at this. Or do i need to have a complete testcase >> first? >> Or clearify anything ? >> >> Thanks in advance >> >> Daniel >> >> > > -- View this message in context: http://www.nabble.com/Custom-Fault-defined-in-WSDL-not-assigned-to-SOAPFault-detail-tp24954475p25076143.html Sent from the cxf-user mailing list archive at Nabble.com.
