commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SCXML-30) Better handling of parent/child relationsships
Date Wed, 04 Oct 2006 17:31:22 GMT
     [ http://issues.apache.org/jira/browse/SCXML-30?page=all ]

Rahul Akolkar updated SCXML-30:
-------------------------------

    Fix Version/s: 1.0

Makes good sense to do this. One can think of two "views" of state machines from a Commons
SCXML perspective:

(a) A document-centric view: This is the n-ary tree represented by the SCXML document. The
top-down relationships from document root are important
(b) A engine-centric view: This is an intricate graph with all the wires between transition
targets and initials and histories drawn out on top of the n-ary tree in (a)

For version 0.5, the focus has been to take (a) and the wiring needed to transform it into
(b) was done as a separate step. While this will continue to hold to some extent, the consistency
and conveniences needed for procedural tweaking of the object model (such as setting symmetric
references) are definitely desirable, though it might mean we lose the side-effect free setters
in some cases. While it may not be obvious, SCXML-23 has the beginnings of such an effort.

I am setting the fix version to 1.0 primarily because, on a strict prioritization basis, this
lags behind other things I want to do. However, if anyone fancies a tested patch, there is
no reason not to apply it immediately.


> Better handling of parent/child relationsships
> ----------------------------------------------
>
>                 Key: SCXML-30
>                 URL: http://issues.apache.org/jira/browse/SCXML-30
>             Project: Commons SCXML
>          Issue Type: Improvement
>    Affects Versions: 0.5
>            Reporter: Hallvard Trætteberg
>             Fix For: 1.0
>
>
> The nice thing about Statecharts is its hierarchical structure. However, it is far too
easy to build incomplete models, e.g. use addChild but forget setParent. I notice that some
add methods automatically set the parent (opposite relation), and I suggest that this is done
consistently throughout the model classes. This also goes for methods like State.setParallel
and Parallel(TransitionTarget).setParent.

-- 
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


Mime
View raw message