You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Lance Waterman (JIRA)" <ji...@apache.org> on 2006/10/18 08:54:34 UTC
[jira] Created: (ODE-69) Assign does not appear to be working when
variable is an element type.
Assign does not appear to be working when <to> variable is an element type.
----------------------------------------------------------------------------
Key: ODE-69
URL: http://issues.apache.org/jira/browse/ODE-69
Project: Apache Ode
Issue Type: Bug
Components: BPEL Runtime
Affects Versions: Incubator
Reporter: Lance Waterman
Fix For: Incubator
Created a unit-test "TestSubTreeAssign" which appears to be failing at line 74 of the BPEL source. The <copy> at line 65 causes the invocation of ASSIGN.replaceElement(). It seems strange to me that this method appears to have no impact on the lvalue that is pushed back into the context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (ODE-69) Assign does not appear to be working when variable is an element type.
Posted by Maciej Szefler <mb...@intalio.com>.
JIRA is down, but this issue was fixed in the last couple of days. The test
case did not have the proper assertion, so I fixed it and it passes.
On 10/18/06, Lance Waterman (JIRA) <ji...@apache.org> wrote:
>
> Assign does not appear to be working when <to> variable is an element
> type.
>
> ----------------------------------------------------------------------------
>
> Key: ODE-69
> URL: http://issues.apache.org/jira/browse/ODE-69
> Project: Apache Ode
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: Incubator
> Reporter: Lance Waterman
> Fix For: Incubator
>
>
> Created a unit-test "TestSubTreeAssign" which appears to be failing at
> line 74 of the BPEL source. The <copy> at line 65 causes the invocation of
> ASSIGN.replaceElement(). It seems strange to me that this method appears
> to have no impact on the lvalue that is pushed back into the context.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
[jira] Closed: (ODE-69) Assign does not appear to be working when
variable is an element type.
Posted by "Lance Waterman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/ODE-69?page=all ]
Lance Waterman closed ODE-69.
-----------------------------
Resolution: Fixed
Unit test passes.
> Assign does not appear to be working when <to> variable is an element type.
> ----------------------------------------------------------------------------
>
> Key: ODE-69
> URL: http://issues.apache.org/jira/browse/ODE-69
> Project: Apache Ode
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: Incubator
> Reporter: Lance Waterman
> Fix For: Incubator
>
>
> Created a unit-test "TestSubTreeAssign" which appears to be failing at line 74 of the BPEL source. The <copy> at line 65 causes the invocation of ASSIGN.replaceElement(). It seems strange to me that this method appears to have no impact on the lvalue that is pushed back into the context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira