[
https://issues.apache.org/jira/browse/ODE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou resolved ODE-289.
-------------------------------
Resolution: Fixed
Added the missing outgoing link reference setup in the compiler. Also a bit
more logging on links that are dpe at runtime, for the next time.
> Compiler doesn't properly flag outgoing links from structured activities
> ------------------------------------------------------------------------
>
> Key: ODE-289
> URL: https://issues.apache.org/jira/browse/ODE-289
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.1.1
> Reporter: Matthieu Riou
> Assignee: Matthieu Riou
> Fix For: 1.2
>
>
> When a link is nested within a structured activity, the compiler doesn't
> properly register it on said activity. As a result the runtime dpe doesnt't
> work. For example:
> <bpel:if name="TransitionResolver" suppressJoinFailure="yes">
> <bpel:targets>
> <bpel:target linkName="transition3" />
> </bpel:targets>
> <bpel:condition> true() </bpel:condition>
> <bpel:empty>
> <bpel:sources>
> <bpel:source linkName="should-be-dpe" />
> </bpel:sources>
> </bpel:empty>
> <bpel:else>
> <bpel:empty />
> </bpel:else>
> </bpel:if>
> Here the link "should-be-dpe" will not be eliminated simply because the
> runtime doesn't know the "TransitionResolver" if activity has such an
> outgoing link.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
