commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SCXML-94) <assign> does not support non-XML datamodels
Date Sat, 15 Nov 2014 03:35:34 GMT

     [ https://issues.apache.org/jira/browse/SCXML-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ate Douma resolved SCXML-94.
----------------------------
    Resolution: Fixed

This should now be fixed by SCXML-213

> <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
>            Assignee: Ate Douma
>             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.3.4#6332)

Mime
View raw message