[
https://issues.apache.org/jira/browse/ODE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739300#action_12739300
]
Rafal Rusin commented on ODE-634:
---------------------------------
I believe OutstandingRequestManager needs improvements. But I think we should
focus more on doing it right, like WS-BPEL says about IMAs and also related
faults: conflictingReceive and conflictingRequest.
I think it would be better to do a bigger patch at once, or at least work on
trunk and then migrate, because OutstandingRequestManager is serializable and
needs special handling in 1.X for backward compatibility.
There is a couple of issues here:
-as I understand, BPEL Engine should trigger conflictingRequest when
partnerLink+operation+correlationSet becomes non unique during instance
execution. Now OutstandingRequestManager validates only In-Outs.
-handling Open IMAs separately from IMAs, which William's patch does, adds
possibility of implementing conflictingRequest semantics, which isn't now in
ODE, but could be added here.
-opening IMA ("associate" method) actually needs selectorIndex, because in case
of pick with branches, we want to associate only one selector to handle
conflictingRequests well. Also for example, we want to do in-out receive inside
one branch in pick on the same plink+op+correlationSet as the other brach of
pick has. I believe current OutstandingRequestManager will cause
conflictingReceive fault in such case.
-now OutstandingRequestManager validates selectors by RID tuple. It includes
mex as well, which is not what Spec says.
-the last thing less important, but cool is to have implemented are
messageExchanges declarations in scopes. They could for example throw faults
for in-out operations on scope completion instead of process completion only
way (releaseAll method). Now mex'es are global and not resolved like variables.
> Event Handles not working
> -------------------------
>
> Key: ODE-634
> URL: https://issues.apache.org/jira/browse/ODE-634
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2, 1.3.3, 2.0
> Reporter: William McCusker
> Attachments: account-sa.zip, account-soapui-project.xml,
> event_handler_1x.patch, event_handler_trunk.patch
>
>
> When attempting to send a message to an event handler one of two
> possibilities occur:
> 1.) Event Handler fails to receive message.
> 2.) message is receive but conflicting receive fault triggered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
