[
https://issues.apache.org/jira/browse/ODE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612612#action_12612612
]
alexismidon edited comment on ODE-328 at 7/10/08 12:46 PM:
------------------------------------------------------------
This issue has remained dormant so far because in all test cases fault message
and fault type are the same.
To reproduce the issue:
1. edit these 2 files:
axis2-war/src/test/resources/TestStructuredFault/HelloWorld2.bpel
axis2-war/src/test/resources/TestStructuredFault/dummy-service.wsdl
2. rename the DummyException message into DummyExceptionMessage
org.apache.ode.axis2.ServiceFaultCatchTest should now fail.
was (Author: alexismidon):
This issue has remained dormant so far because in all test cases fault
message and fault type are the same.
> 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.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.
