On 11/16/06, THOMAS, JAYANT (SBCSI) <[EMAIL PROTECTED]> wrote:
Thanks, Iam using the dialog2 implementation inside shale, can I do the same.
<snip/>
Yup, should do, dialog2 was the sandbox moniker, its now the shale-dialog module (and the two impls - shale-dialog-basic and shale-dialog-scxml), part of the shale-framework-* builds [1]. IIRC, the "white box" nature referred to below was clarified post v0.5, so dangling target references might need the Commons SCXML nightlies [2] (trunk has test cases that verify the particular behavior under discussion here). If you have further questions, please ping the user list (Shale or Commons, as you find appropriate). Thanks. -Rahul [1] http://people.apache.org/builds/shale/nightly/ [2] http://people.apache.org/builds/jakarta-commons/nightly/commons-scxml/
Thanks Jayant -----Original Message----- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 7:36 PM To: dev@shale.apache.org Subject: Re: Navigating from One SCXML dialog to another SCXML dialog in shale On 11/15/06, THOMAS, JAYANT (SBCSI) <[EMAIL PROTECTED]> wrote: > Thanks, That is what I want , say for example I might have a bunch of > higher level states from where at certain point I can navigate to child > states defined in another xml like popup.xml, it will be nice If I can > navigate from Wizard to popup by saying something like #popup/statename > in the state transition logic of wizard itself. > I hope this is possible !! <snip/> If using the Commons SCXML dialogs impl, this is possible. In fact, you don't even need to use '#popup' (at the cost of implying unique IDs for <state>s when subdialog state machines are pulled in via 'src' attribute -- see subdialogs bit here [1]). This has to do with the semantics of SCXML itself, which treats included state machines as white boxes (this differs from the basic impl) and thus, you can have dangling transition targets (as long as they're available in the included state machine -- or vice versa) as you mention above. Note that you don't even need to declare the included state machine as a <dialog> in the dialog-config.xml unless you plan on using it as a standalone dialog (at which point, the dangling unresolved transition target references will cause a parse time failure, if you choose to have them). -Rahul [1] http://shale.apache.org/shale-dialog-scxml/
<snap/>
