You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Nestor Urquiza <ne...@yahoo.com> on 2006/04/20 19:42:05 UTC
[SCXML] extracting info from FSM states
Hello guys,
Having an Executor and therefore having a current
state I would like to have the current-state-id, the
last-state-id, the last-transition-made.
The purpose of this is not only logging that important
information for future DataMining/CRM but also because
I think in a web service infrastructure some clients
would love to have as response what I would call
"current-node" and "last-node" I evem would say that
besides storing in cvs the scxml file
I would log also the possible transitions the current
state has because of course they can change in the
future and I would have then stored that valuable
information.
Thanks
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [SCXML] extracting info from FSM states
Posted by Nestor Urquiza <ne...@yahoo.com>.
Done! I didn't need getCurrentStatus() so far. Let us
see if the requirements for this project are
fullfilled. The Listener was enough ... so far
Thanks,
Nestor
--- Rahul Akolkar <ra...@gmail.com> wrote:
> On 4/20/06, Nestor Urquiza <ne...@yahoo.com>
> wrote:
> > Hello guys,
> > Having an Executor and therefore having a current
> > state I would like to have the current-state-id,
> the
> > last-state-id, the last-transition-made.
> >
> > The purpose of this is not only logging that
> important
> > information for future DataMining/CRM but also
> because
> <snip/>
>
> Sold, don't worry about explaining ;-) Wire a
> SCXMLListener to the
> document root (SCXML object) and you will be
> notified on all state
> entries/exits and transitions. The SCXMLExecutor
> itself offers the
> getCurrentStatus() feedback as well. Together, these
> can get you the
> feedback information you need.
>
> -Rahul
>
>
> > I think in a web service infrastructure some
> clients
> > would love to have as response what I would call
> > "current-node" and "last-node" I evem would say
> that
> > besides storing in cvs the scxml file
> >
> > I would log also the possible transitions the
> current
> > state has because of course they can change in the
> > future and I would have then stored that valuable
> > information.
> > Thanks
> >
> <snap/>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> commons-user-help@jakarta.apache.org
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [SCXML] extracting info from FSM states
Posted by Rahul Akolkar <ra...@gmail.com>.
On 4/20/06, Nestor Urquiza <ne...@yahoo.com> wrote:
> Hello guys,
> Having an Executor and therefore having a current
> state I would like to have the current-state-id, the
> last-state-id, the last-transition-made.
>
> The purpose of this is not only logging that important
> information for future DataMining/CRM but also because
<snip/>
Sold, don't worry about explaining ;-) Wire a SCXMLListener to the
document root (SCXML object) and you will be notified on all state
entries/exits and transitions. The SCXMLExecutor itself offers the
getCurrentStatus() feedback as well. Together, these can get you the
feedback information you need.
-Rahul
> I think in a web service infrastructure some clients
> would love to have as response what I would call
> "current-node" and "last-node" I evem would say that
> besides storing in cvs the scxml file
>
> I would log also the possible transitions the current
> state has because of course they can change in the
> future and I would have then stored that valuable
> information.
> Thanks
>
<snap/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org