Re: [SCXML] Next states

2016-05-06 Thread Woonsan Ko
On Fri, May 6, 2016 at 2:56 AM, Mansour Al Akeel wrote: > Thank you Woonsan, > The use case is to report transition failure or invalid path. > Using the listener is good, but it wont be triggered unless the > transition happens. > For example this was written to test

Re: [SCXML] Next states

2016-05-06 Thread Mansour Al Akeel
Thank you Woonsan, The use case is to report transition failure or invalid path. Using the listener is good, but it wont be triggered unless the transition happens. For example this was written to test commons SCXML 1: @Override public boolean fireEvent(String event) { List lst =

Re: [SCXML] Next states

2016-05-04 Thread Woonsan Ko
Not sure about the use case, but maybe you can add a listener (AbstractStateMachine#getEngine()#addListener(stateMachine, new MyListener())). If you get a TransitionalState in your listener, you may possibly get all the available Transitions and TransitionTargets. Regards, Woonsan On Sun, May

Re: [SCXML] Next states

2016-05-02 Thread Mansour Al Akeel
Thank you Benedikt. On Mon, May 2, 2016 at 6:47 AM, Benedikt Ritter wrote: > Hello Mansour, > > Mansour Al Akeel schrieb am Mo., 2. Mai 2016 um > 02:19 Uhr: > >> Is there a way to get the next valid states or transitions ? >> I am working with

Re: [SCXML] Next states

2016-05-02 Thread Benedikt Ritter
Hello Mansour, Mansour Al Akeel schrieb am Mo., 2. Mai 2016 um 02:19 Uhr: > Is there a way to get the next valid states or transitions ? > I am working with AbstractStateMachine > I think Woosan and Ate are the ones who have worked mostly on SCXML. Maybe they can

[SCXML] Next states

2016-05-01 Thread Mansour Al Akeel
Is there a way to get the next valid states or transitions ? I am working with AbstractStateMachine Thank you - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: