You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2008/09/15 18:29:44 UTC
[jira] Resolved: (AXIS2-4031) JAXWS:Provider with SOAPFault is not
working correctly
[ https://issues.apache.org/jira/browse/AXIS2-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4031.
-----------------------------------
Resolution: Fixed
Committed: 695531
Kudos to Nick for working with me on this change.
> JAXWS:Provider with SOAPFault is not working correctly
> ------------------------------------------------------
>
> Key: AXIS2-4031
> URL: https://issues.apache.org/jira/browse/AXIS2-4031
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Background:
> A customer may use a JAXWS Provider for the service implementation. The provider exposes a generic representation of either the message or payload (i.e. Provider<Source>).
> Problem:
> If a Provider returns a representation of a SOAP Fault in the outbound message, the JAXWS engine should detect the fault and to normal fault outbound processing. Currently this is broken.
> Solution:
> Nicholas Gallardo and I are working on a solution so that the Provider correctly detects the returned SOAPFault and triggers the correct outbound handler (etc.) processing.
> The solution is coded up and we are in the last day of testing.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org