Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: commons-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 38274]  - [scxml] Add another use case that isn't
 Voice (RDC) or MVC (Shale)
In-Reply-To: <bug-38274-7685@http.issues.apache.org/bugzilla/>
Message-Id: <20060118051223.333B6E0@ajax.apache.org>
Date: Wed, 18 Jan 2006 06:12:23 +0100 (CET)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38274>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38274


------- Additional Comments From rahul@apache.org  2006-01-18 06:12 -------
Definitely, simpler usecases might go a long way in getting the concept of the 
component across to our development community. Potential suggestions we've 
seen so far:

1) Microwave example from spec (version without parallel states)
2) Stephen's stopwatch example from his Javapolis talk
3) Tim's suggestion about the document lifecycle in a CMS

We have (1) in the src/test subtree. If you guys have SCXML documents for (2) 
and (3), feel free to add them under the obvious places (xdocs/ as a usecase 
for the website, under src/test or even to this ticket, however you see fit).

I don't mean to be shy towards doing the work, just making sure I wasn't 
coming off as gate-keeping SCXML in any way :-)


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org