[ http://nagoya.apache.org/jira/browse/BEEHIVE-133?page=comments#action_56805 ] Jongjin Choi commented on BEEHIVE-133: --------------------------------------
I tested this case and found that there is no corresponding complexType for service specific exception is not generated in the WSDL. This prevents the Axis client stub to generate the service specific exception from the SOAP fault message. I patched the AxisHook.java, adding additional information for FaultDesc. The service specific exception is now propagated to Axis client. > JSR-181 compliance: Exceptions not propagated correctly > ------------------------------------------------------- > > Key: BEEHIVE-133 > URL: http://nagoya.apache.org/jira/browse/BEEHIVE-133 > Project: Beehive > Type: Bug > Components: Web Services (181) > Versions: V1Beta > Reporter: Michael Merz > Assignee: Jongjin Choi > Fix For: V1Beta > > User exceptions (subclasses of java.lang.Exception) are not properly > propagated to the client. "soapenv:Server.generalException" show up on the > client side instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
