[
https://issues.apache.org/jira/browse/ODE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612685#action_12612685
]
Alexis Midon commented on ODE-328:
----------------------------------
Fix commited for trunk and branch:
replyWithFault must receive faultName, not faultType no matter what the method
signature says
Step 2 would be to get ride of this dirty trick an refactor APIs so that fault
type is not mentionned anymore
> PartnerRoleMessageExchange#replyWithFault must receive fault name
> -----------------------------------------------------------------
>
> Key: ODE-328
> URL: https://issues.apache.org/jira/browse/ODE-328
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Alexis Midon
> Priority: Critical
> Fix For: 1.2
>
>
> org.apache.ode.bpel.iapi.PartnerRoleMessageExchange#replyWithFault(QName
> faultType, Message outputFaultMessage)
> The faultType is actually used as the fault name. If you actually pass the
> fault type, fault management will fail because FaultData#_faultName is a the
> fault type.
> See org.apache.ode.bpel.runtime.INVOKE, line 168.
> Fault Management has been working fine so far because this bug is masked by
> another one: SoapExternalService already provides the fault name instead of
> the fault type.
> See org.apache.ode.axis2.soapbinding.SoapMessageConverter#parseSoapFault
> The fix is to change replyWithFault signature to accept the fault name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
