Hi Ben, Could you create a new SCXML instance for each module? So, rather than having one global SCXML for the entire application, you have a number of small SCXML components, which you would instantiate when your module is loaded?
Jake On Oct 25, 2014, at 3:22 AM, Benoît Thiébault <thieba...@artenum.com> wrote: > Hi everyone, > > I am very pleased to learn that SCXML is back online and that new evolutions > are coming with version 2.0. Congrats and good luck to the development team! > > I already use SCXML 0.9 in one of my applications and one feature I was > missing was a more dynamic state engine. My application is OSGi-based and > thus very dynamic: modules come and go at runtime. What I wanted to do was to > be able to modify the state diagram at runtime: when a new bundle is loaded, > it injects its own state chart as a sub-set of the existing state chart. If I > understood SCXML correctly, this was not really possible with 0.9. Is it > planned for future versions? > > Kind regards, > > Ben > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
