shale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <rahul.akol...@gmail.com>
Subject Re: [dialog] Using SCXML to describe Shale dialogs
Date Thu, 24 Aug 2006 23:04:57 GMT
On 8/24/06, Craig McClanahan <craigmcc@apache.org> wrote:
> On 8/24/06, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
> >
> > [1] http://marc.theaimsgroup.com/?l=struts-dev&m=112900158004770&w=2
> > [2]
> > http://jakarta.apache.org/commons/scxml/usecases/scxml-in-shale-dialogs.html
> > [3] http://wiki.apache.org/shale/DialogManagerFeature
> >
>
>
> Rahul,
>
> In the two diagrams, most of the transitions are labelled "faces.outcome[xxx]"
> but a few are just "xxx".  Was that intentional?
>
<snip/>

Yes, the UML notation on a transition is:

event[guard_condition]

Simply put, the states that have faces.outcome listed as the event are
view states (wait for the postback "event") and the others are action
states.

You can skip the event, the guard condition or both on a transition.
Eventless transitions get evaluated as soon as executable content
"onentry" for that state is done. The symbol and text label under the
"checkCookie" state label implies execute that method binding
expression on entering the state (which gives us the logical outcome
to choose the outbound transition).

-Rahul


> Craig
>
>

Mime
View raw message