[ http://nagoya.apache.org/jira/browse/BEEHIVE-133?page=comments#action_56729 ] Jongjin Choi commented on BEEHIVE-133: --------------------------------------
Axis' SOAP fault code does not follow WS-I BP now. But "soapenv:Server.generalException" fault code does not matter between Axis and Axis communication. (I think Axis should follow WS-I BP style for fault code.) But Axis' service specific exception implementation lacks of JAX-RPC 1.1 compatibility. This can be a cause for this issue. I wonder whether fault serialization (server-side) or fault deserialization (client-side) fails. Can you to upload a test case? > 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 > 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
