[
https://issues.apache.org/jira/browse/AXIS2-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841867#action_12841867
]
apache bug rep commented on AXIS2-4645:
---------------------------------------
Adding some more clarification ...section 6.4.1 of th jaxws spec says that a
SOAPFaultException thrown form a server should be transferred by the
implementation to the client as is(ie along with the inherent SOAPFault info
object) so that client can extract the SOAPFault info out of it to understand
the error.
I get a SOAPFault object on the client side but it somehow seems to leave out
the details section ..its almost like only the message part of the exception
has been extracted and transferred to the client but the other details that I
added to the SOAPFault like actor,role,details are not showing on the client
side.
The way Iam throwing the SOAPFaultException is like an unchecked exception (
that is not declared in the wsdl ).
> SOAPFault Exception not getting transferred completely to client side
> ---------------------------------------------------------------------
>
> Key: AXIS2-4645
> URL: https://issues.apache.org/jira/browse/AXIS2-4645
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.4.1
> Environment: wondows 7 jdk 1.5 axis 1.4.1
> Reporter: apache bug rep
> Priority: Minor
>
> I saw a couple of issues around the same lines in 2007 ...that were resolved
> but Iam seeing the same issue again ..I was just trying to throw a
> SOAPFaultException with a dummy fault detail object and my fault detail
> object does not get transferred to the client side. I only get the message
> that I set in the fault reason code ( this comes as the exception message on
> the client side ).
> Iam able to catch and handle the SOAPFaultException in the client side but
> the SOAPFaultException does not have the SOAPFault object that I populated in
> it from the server side.
> Is this a know and open issue by any chance ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]