[
https://issues.apache.org/jira/browse/ODE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Yu updated ODE-950:
------------------------
Summary: scope's name can't be as same as Invoke Activity's name. (was:
Not distinguish the scope's name and Invoke Activity's name.)
> scope's name can't be as same as Invoke Activity's name.
> --------------------------------------------------------
>
> Key: ODE-950
> URL: https://issues.apache.org/jira/browse/ODE-950
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.5
> Reporter: Jeff Yu
> Fix For: 1.4
>
>
> In the Invoke Activity, the runtime actually generated a scope around that
> Invoke. The problem is that if users create a scope, and then having the
> Invoke's name, which inside that scope, as same as the scope name, it will
> have unexpected issues, as the scope's name should be unique. For example, if
> I defined a scope variable in the scope, it has been initialised, but it will
> throw the 'variable not been initialized properly' error.
> Following is two approaches for this issue:
> 1) updating the compiler's validation rule to enforce that the scope's and
> the Invoke activity's name should stay unique. This approach has least impact
> with current codebase.
> 2) adding the 'Invoke' string to those scopes name, which were generated in
> Invoke activity. In another word, the scope's name for those Invoke activity
> would be like 'InvokeCallingExternalService', whose invoke name is
> 'CallingExternalService'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
