You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2014/01/27 22:41:43 UTC
[jira] [Updated] (SCXML-94) does not support non-XML
datamodels
[ https://issues.apache.org/jira/browse/SCXML-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated SCXML-94:
---------------------------
Fix Version/s: (was: 0.10)
2.0
> <assign> does not support non-XML datamodels
> --------------------------------------------
>
> Key: SCXML-94
> URL: https://issues.apache.org/jira/browse/SCXML-94
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Ingmar Kliche
> Fix For: 2.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)