commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <>
Subject [jira] Updated: (SCXML-94) <assign> does not support non-XML datamodels
Date Fri, 28 Nov 2008 14:49:44 GMT


Rahul Akolkar updated SCXML-94:

    Fix Version/s: 0.10

The location attribute value is supposed to be a 'location expression'. We could collapse
the two attribute semantics , so if evalLocation() doesn't return a Node, we can apply the
same semantics that the name attribute currently has (look for an existing 'variable' in the
context to set). Will need some verification that we've covered all the 'name' cases before
we remove it.

Setting fix version to v0.10.

> <assign> does not support non-XML datamodels
> --------------------------------------------
>                 Key: SCXML-94
>                 URL:
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Ingmar Kliche
>             Fix For: 0.10
> 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