ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexis Midon (JIRA)" <j...@apache.org>
Subject [jira] Created: (ODE-328) PartnerRoleMessageExchange#replyWithFault must receive fault name
Date Wed, 09 Jul 2008 23:17:31 GMT
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.2, 1.1.1
            Reporter: Alexis Midon
            Priority: Critical
             Fix For: 1.3


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.


Mime
View raw message