[jira] Resolved: (ODE-328) PartnerRoleMessageExchange#replyWithFault must receive fault name

["Alexis Midon (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexis Midon resolved ODE-328.
------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.3)
                   1.2

A proper fix for this bug would imply to rename the BPEL_MESSAGE_EXCHANGE.FAULT_TYPE into BPEL_MESSAGE_EXCHANGE.FAULT_NAME to make the data model in line.

This change is not harmless and may have side-effects, the workaround (fault type and fault name must the same) will do for 1.2.

> 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
>    Affects Versions: 1.1.1, 1.2
>            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.