If you're using the JAX-WS frontend, then you do need to use the @WebFault annotation per the JAX-WS spec. With the simple frontend there were some bugs in 2.0, but I believe this is fixed in 2.0.1 which will be released in the next few days (fingers crossed - we're voting on it right now). In the mean time you can try a SNAPSHOT build if you want.
Cheers, - Dan On 8/3/07, Zarar Siddiqi <[EMAIL PROTECTED]> wrote: > > > The solution was to specify a name attribute for the @WebFault annotation. > Once I specified @WebFault(name="WSException"), it appeared in the WSDL. > > Wouldn't it be better if it defaulted to the class name? It would me more > inline with how XFire rendered the WSDL. > > Zarar > > > > Zarar Siddiqi wrote: > > > > I'm using the Aegis binding and all is well except that the Exception > > (Fault) is not showing up in the WSDL. > > > > Here's my Spring config. > > > > <bean id="aegisBean" > > class="org.apache.cxf.aegis.databinding.AegisDatabinding"/> > > > > <bean id="aegisServiceFactoryBean" > > class="org.apache.cxf.aegis.databinding.AegisServiceFactoryBean"/> > > > > <bean class="org.apache.cxf.frontend.ServerFactoryBean" > > init-method="create"> > > <property name="serviceBean" ref="personSoapService"/> > > <property name="address" value="/PersonService"/> > > <property name="dataBinding" ref="aegisBean"/> > > <property name="serviceFactory" ref="aegisServiceFactoryBean"/> > > </bean> > > > > My interface and implementation classes have methods called: > > > > public Email getEmail() throws WSException; > > public Address getAddress() throws WSException; > > > > The Email and and Address objects get translated to <complexType > > name="Email"> and <complexType name="Address"> but the WSException never > > shows up in the WSDL. > > > > I'm migrating from XFire and this was never a problem there. There's a > > <xsd:complexType name="WSException"> missing from the WSDL that is > > generated through CXF which was present in XFire. > > > > I tried annotating WSException with the @WebFault annotation but that > > didn't help. > > > > Is this is a bug or am I missing something? Any help is appreciated. > > > > Thanks, > > Zarar > > > > -- > View this message in context: > http://www.nabble.com/Exception-not-showing-up-in-WSDL-with-Aegis-binding-tf4208423.html#a11977298 > Sent from the cxf-user mailing list archive at Nabble.com. > > -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
