commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ingmar Kliche (JIRA)" <>
Subject [jira] Created: (SCXML-94) <assign> does not support non-XML datamodels
Date Wed, 26 Nov 2008 22:13:44 GMT
<assign> does not support non-XML datamodels

                 Key: SCXML-94
             Project: Commons SCXML
          Issue Type: Bug
    Affects Versions: 0.8
            Reporter: Ingmar Kliche

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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message