[ http://issues.apache.org/jira/browse/SCXML-26?page=comments#action_12439566 ] Rahul Akolkar commented on SCXML-26: ------------------------------------
Indeed we're aware that SCXML will be at its productive best when its used in particular contexts, not in isolation. In terms of the two options from your last comment, #1 (query an SCXMLExecutor instance for the context corresponding to a target) is feasible, and I think would be a useful addition. For #2, its true that Evaluators may need more, but the interface provides the bare minimum (anything else should be part of the implementation). > 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]
