For the first issue, yes, I would say the errors should have separate namespaces even if they mean the same thing--if you're doing WSDL-first each of their WSDL's should have separate target namespaces anyway.
For the second issue, this article[1] has both a wsdl-defined fault and a generic SOAPFaultException, as well as service providers and clients handling both of them. It may give you a little bit of coding guidance. HTH, Glen [1] http://www.jroller.com/gmazza/date/20080308 On Thu, 2008-07-17 at 15:01 -0700, Sven Haiges wrote: > Hi all, > > I realize something similar was just asked but still some of my issues are > not solved. > > My SOAP service may throw a few exceptions and as far as I understand, these > Exception object will be converted automatically by CFX. I created a java > client with wsdl2java and I can see the Exception classes automatically being > generated. Now two issues: > > - got 4 services, some of those service inerfaces share the same Exception > class. Still, after generating 4 clients for the services, each client > service package will have its own Exception class. This causes some confusion > and will confuse the users later. Can I fix this with changeing the > targetNameSpace or similar? > > - I read about outFaultInterceptors, but could not find more documentation in > the CXF user guide. Can someone point me to a really good resource about how > to map java exceptions to soap faults? > > Thanx > Sven > > --- > Sven Haiges > Y! Messenger / Skype: hansamann >
