You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Ingmar Kliche (JIRA)" <ji...@apache.org> on 2008/11/26 23:22:44 UTC

[jira] Created: (SCXML-95) profile attribute of

profile attribute of <scxml>
----------------------------

                 Key: SCXML-95
                 URL: https://issues.apache.org/jira/browse/SCXML-95
             Project: Commons SCXML
          Issue Type: New Feature
    Affects Versions: 0.8
            Reporter: Ingmar Kliche


SCXML defines a profile attribute. This should be reflected in the model. The profile attribute could be used in two ways:

1) check profile name within parsed document against registered context/evaluator and throw error in case of mismatch

2) allow registration of multiple context/evaluators and executor should instantiate context/evaluator based on profile attribute of parsed document.

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

[jira] Updated: (SCXML-95) profile attribute of

Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.

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

Rahul Akolkar updated SCXML-95:
-------------------------------

    Fix Version/s: 0.10

I think we should start with (1). Something like (2) would be good if there is some sort of SCXMLExecutor 'factory' that the application maintains, so its more an application concern I think.

Setting fix version to v0.10.


> profile attribute of <scxml>
> ----------------------------
>
>                 Key: SCXML-95
>                 URL: https://issues.apache.org/jira/browse/SCXML-95
>             Project: Commons SCXML
>          Issue Type: New Feature
>    Affects Versions: 0.8
>            Reporter: Ingmar Kliche
>             Fix For: 0.10
>
>
> SCXML defines a profile attribute. This should be reflected in the model. The profile attribute could be used in two ways:
> 1) check profile name within parsed document against registered context/evaluator and throw error in case of mismatch
> 2) allow registration of multiple context/evaluators and executor should instantiate context/evaluator based on profile attribute of parsed document.

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