[ http://issues.apache.org/jira/browse/SCXML-26?page=all ]
Rahul Akolkar updated SCXML-26:
-------------------------------
Fix Version/s: 1.0
Conceptually, there is a 1:1 mapping between contexts and targets, as
established by the executor instance, which picks the target for the new
context.
This is a major change request (anytime a change is requested to an interface
which is part of the component's public API), so it definitely won't happen
before a 1.0 release (and even if it happens at a 1.0, might require a
subinterface and fancy footwork in code) -- so we'll need to have quite a
compelling argument, thats unclear to me at the moment.
> Add parameter to Evaluator.newContext
> -------------------------------------
>
> Key: SCXML-26
> URL: http://issues.apache.org/jira/browse/SCXML-26
> Project: Commons SCXML
> Issue Type: Improvement
> Affects Versions: 0.5
> Reporter: Hallvard Trætteberg
> Fix For: 1.0
>
>
> The Evaluator.newContext method currently takes one argument, the parent
> context. However, to make it easier for the context to link to relevant
> application data, it would be nice if it also took a TransitionTarget
> argument, i.e. have the signature public Context
> newContext(TransitionTarget target, Context parent); By including the target
> in the context, it becomes easier for expressions to refer to contextual
> data. In my case, SCXML is used together with data bindings, and expressions
> are used to refer to data in the context of states and transitions. I had to
> modify SCXML as suggested above, to provide the link between state and data
> bindings.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
