=SoapPort
soap:address
location=http://localhost:9000/SoapContext/SoapPort; /
/wsdl:port
/wsdl:service
/wsdl:definitions
--
View this message in context:
http://www.nabble.com/Generated-Faults-and-Inheritance
://www.nabble.com/Generated-Faults-and-Inheritance-tp16133913p16197927.html
Sent from the cxf-user mailing list archive at Nabble.com.
-Faults-and-Inheritance-tp16133913p16197927.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/Generated-Faults-and-Inheritance-tp16133913p16200381.html
Sent from the cxf-user mailing list archive at Nabble.com.
I don't think so using normal looking java exception. You could do it
if you model your exceptions exactly like the exceptions would look like
if you generated code from wsdl. Basically, put the data in JAXB Beans
that implement the heiarchy you want to see in the wsdl, then add Bean
://localhost:9000/SoapContext/SoapPort; /
/wsdl:port
/wsdl:service
/wsdl:definitions
--
View this message in context:
http://www.nabble.com/Generated-Faults-and-Inheritance-tp16133913p16133913.html
Sent from the cxf-user mailing list archive at Nabble.com.
