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/28 01:57:38 UTC

[jira] [Commented] (SCXML-190) Check and enforce required scxml element attributes as defined by the specification

    [ https://issues.apache.org/jira/browse/SCXML-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883583#comment-13883583 ] 

Ate Douma commented on SCXML-190:
---------------------------------

Required attributes check for foreach element now implemented with SCXML-191

> Check and enforce required scxml element attributes as defined by the specification 
> ------------------------------------------------------------------------------------
>
>                 Key: SCXML-190
>                 URL: https://issues.apache.org/jira/browse/SCXML-190
>             Project: Commons SCXML
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.0
>
>
> The SCXMLReader currently doesn't (directly) check and enforce specific element attributes as required by the specification, like:
> - scxml element: attribute 'version' is required AND must have value "1.0"
> - raise element: 'id' is required
> - if/elseif element: attribute 'cond' is required
> - foreach element: attributes 'array' and 'item' are required
> - data element: attribute 'id' is required
> - param element: attribute 'name' is required
> - assign element: attribute 'location' is required
> It doesn't make much sense 'delaying' checking/enforcing these required attributes until execution time so I'll add required checks during reading the document, and throw a ModelException if undefined (or incorrect value like for the SCXML version attribute)
> Note:
> - for the assign element we currently also support the custom 'name' attribute as alternative, so this needs some conditional handling
> - the foreach and raise element aren't implemented at all yet but shouldn't be difficult to add, for which I'll create separate issues shortly



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)