You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2006/07/17 20:58:16 UTC

[jira] Updated: (SCXML-4) [scxml] More Explicit Instructions on core-engine.html

     [ http://issues.apache.org/jira/browse/SCXML-4?page=all ]

Rahul Akolkar updated SCXML-4:
------------------------------

    Fix Version/s: 0.5

> [scxml] More Explicit Instructions on core-engine.html
> ------------------------------------------------------
>
>                 Key: SCXML-4
>                 URL: http://issues.apache.org/jira/browse/SCXML-4
>             Project: Commons SCXML
>          Issue Type: Bug
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Tim O'Brien
>             Fix For: 0.5
>
>
> Similar issue on core-engine.html as core-digester.html.  While we show the
> end-user a clear path towards getting the Executor to work, we use placeholders
> for the Evaluator, EventDispatcher, and ErrorReporter.  
> The document needs sections on all three objects, how to create them, what they
> do.  The document could also use a more general discussion of the components
> that are involved in the execution.  
> "An engine, once initialized, should be cached till the state machine reaches a
> terminal or "final" state, and no more." - That sentence especially needs a
> little more definition.  
> Page needs to explain all of the methods on the Executor, for example, while the
> code uses SuperStep, it doesn't explain what that particular call accomplishes.
>   Also, the documentation should be clear about when the Executor starts to
> dispatch events.

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org