[SCXML-94] <assign> does not support non-XML datamodels

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8
• Fix Version/s: 2.0
• Assignee: Ate Douma
• Reporter: Ingmar Kliche
• Created: 26/Nov/08 22:13
• Updated: 15/Nov/14 03:35
• Resolved: 15/Nov/14 03:35

Description

The current impl of <assign> still supports "name" and "location" attributes, which is not in line with the SCXML WD. SCXML only defines the "location" attribute.

The impl of <assign> uses the evalLocation() function of the evaluator to determine the location and evalLocation() has to return a Node. But this does not work for non-XML datamodels.

Non-XML datamodels worked using the "name" atribute (which used the set() function of the context). But the "name" attribute is no longer standardized. Thus <assign> only has the "location" attribute and it needs to support XML and non-XML data models.

The question is, whether <assign> should manipulate the DOM tree or whether it is the responsibility of the context to manipulate the data.

Issue Links

• is superceded by: SCXML-213 Fixing the datamodel handling - reimplement xpath processing, the Data() function and the <assign> action
• relates to: SCXML-213 Fixing the datamodel handling - reimplement xpath processing, the Data() function and the <assign> action