You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "William McCusker (JIRA)" <ji...@apache.org> on 2009/01/20 19:14:59 UTC
[jira] Created: (ODE-496) UndeclaredPartnerLink incorrectly thrown
for OnEvent
UndeclaredPartnerLink incorrectly thrown for OnEvent
----------------------------------------------------
Key: ODE-496
URL: https://issues.apache.org/jira/browse/ODE-496
Project: ODE
Issue Type: Bug
Components: BPEL Compilation/Parsing
Affects Versions: 1.2, 2.0
Reporter: William McCusker
According to BPEL 2.0 spec section 12.7.1, for OnEvent the partnerLink reference must resolve to a partner link declared in the process in the following order: the associated scope first and then the ancestor scopes, where associated scope is the scope directly defined within the OnEvent or OnAlarm. In both the trunk and 1.X branch this is not the case. Currently only the ancestor scopes are used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-496) UndeclaredPartnerLink incorrectly thrown
for OnEvent
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-496:
---------------------------------
Fix Version/s: 1.3.5
> UndeclaredPartnerLink incorrectly thrown for OnEvent
> ----------------------------------------------------
>
> Key: ODE-496
> URL: https://issues.apache.org/jira/browse/ODE-496
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2, 2.0
> Reporter: William McCusker
> Fix For: 1.3.5
>
> Attachments: accumulator.zip, BpelCompilerImpl.java.patch
>
>
> According to BPEL 2.0 spec section 12.7.1, for OnEvent the partnerLink reference must resolve to a partner link declared in the process in the following order: the associated scope first and then the ancestor scopes, where associated scope is the scope directly defined within the OnEvent or OnAlarm. In both the trunk and 1.X branch this is not the case. Currently only the ancestor scopes are used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ODE-496) UndeclaredPartnerLink incorrectly thrown
for OnEvent
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William McCusker updated ODE-496:
---------------------------------
Attachment: accumulator.zip
Process and WSDL that when compiled demonstrate the incorrect UndeclaredPartnerLink error.
> UndeclaredPartnerLink incorrectly thrown for OnEvent
> ----------------------------------------------------
>
> Key: ODE-496
> URL: https://issues.apache.org/jira/browse/ODE-496
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2, 2.0
> Reporter: William McCusker
> Attachments: accumulator.zip
>
>
> According to BPEL 2.0 spec section 12.7.1, for OnEvent the partnerLink reference must resolve to a partner link declared in the process in the following order: the associated scope first and then the ancestor scopes, where associated scope is the scope directly defined within the OnEvent or OnAlarm. In both the trunk and 1.X branch this is not the case. Currently only the ancestor scopes are used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-496) UndeclaredPartnerLink incorrectly thrown
for OnEvent
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William McCusker updated ODE-496:
---------------------------------
Attachment: BpelCompilerImpl.java.patch
Possible patch for trunk. If the associated scope is complied before OnEvent partner links are resolved then it is possible to push the associated scope into the structure stack before resolving.
> UndeclaredPartnerLink incorrectly thrown for OnEvent
> ----------------------------------------------------
>
> Key: ODE-496
> URL: https://issues.apache.org/jira/browse/ODE-496
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2, 2.0
> Reporter: William McCusker
> Attachments: accumulator.zip, BpelCompilerImpl.java.patch
>
>
> According to BPEL 2.0 spec section 12.7.1, for OnEvent the partnerLink reference must resolve to a partner link declared in the process in the following order: the associated scope first and then the ancestor scopes, where associated scope is the scope directly defined within the OnEvent or OnAlarm. In both the trunk and 1.X branch this is not the case. Currently only the ancestor scopes are used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-496) UndeclaredPartnerLink incorrectly thrown
for OnEvent
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-496:
---------------------------------
Fix Version/s: 2.0-beta3
> UndeclaredPartnerLink incorrectly thrown for OnEvent
> ----------------------------------------------------
>
> Key: ODE-496
> URL: https://issues.apache.org/jira/browse/ODE-496
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2, 2.0
> Reporter: William McCusker
> Fix For: 1.3.5, 2.0-beta3
>
> Attachments: accumulator.zip, BpelCompilerImpl.java.patch
>
>
> According to BPEL 2.0 spec section 12.7.1, for OnEvent the partnerLink reference must resolve to a partner link declared in the process in the following order: the associated scope first and then the ancestor scopes, where associated scope is the scope directly defined within the OnEvent or OnAlarm. In both the trunk and 1.X branch this is not the case. Currently only the ancestor scopes are used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira