[
https://issues.apache.org/jira/browse/SCXML-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar updated SCXML-51:
-------------------------------
Fix Version/s: 0.7
Assignee: Rahul Akolkar
Affects Version/s: 0.6
This has to do with the fact that we do not remove existing child nodes before
adding new ones in the above usage scenario. I tend to agree that this doesn't
match the semantics of assignment, and furthermore, in situations like the
above (where the only children are text nodes) this definitely leads to
unexpected results. I'll look into this, setting fix version to next release
(v0.7).
Thanks for illustrating how to reproduce the issue. Since you have most of what
is needed, it'd be great if you could submit JUnit testcase(s) with the report
(for example, see tests in Commons SCXML codebase) -- that'd save a bit of time
in having to reconstruct these, so would be very helpful.
> <assign> with location and expr both containing datamodel expressions
> concatenates old and new values
> -----------------------------------------------------------------------------------------------------
>
> Key: SCXML-51
> URL: https://issues.apache.org/jira/browse/SCXML-51
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Chris Nack
> Assignee: Rahul Akolkar
> Fix For: 0.7
>
>
> If you have the following datamodel:
> <datamodel>
> <data name="RAD">
> <rad:timeout>10</rad:timeout>
> </data>
> <data name="CONFIG">
> <rad:short>20</rad:short>
> </data>
> </datamodel>
> and execute this assign:
> <assign location="Data(RAD, 'rad:timeout')" expr="Data(CONFIG,
> 'rad:short')"/>
> you end up with the data value of "2010" stored in rad:timeout. The correct
> data value should be "20".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
