Hi Rahul,
maybe adapting http://commons.apache.org/scxml/guide/datamodel.html
related to your answer will help other users (like me also ;-) to hit
not this pitfall.
Regards
Danny
SCXML documents are namespace aware. data elements are recommended
to have a root such as:
data name=foo
I agree. I'm just following the given examples on the scxml website. I
would appreciate if these can be updated to reflect the actual working.
I have the impression a lot of starters fall in the same pitfalls as I
did.
Thanks for the help so far. I got most of my basis stuff to work now.
Few
I would like to reuse a statediagram in an overall state diagram. The
src attribute in the state tag seems to suggest this is possible.
For example the main state.xml file would contain:
state id=Composite1 src=include.xml
state id=finalState
transition target=Composite2/
/state
On Mon, Jul 21, 2008 at 4:39 AM, Berg, T.W. (Tom) van den
[EMAIL PROTECTED] wrote:
I agree. I'm just following the given examples on the scxml website. I
would appreciate if these can be updated to reflect the actual working.
I have the impression a lot of starters fall in the same pitfalls as
On Mon, Jul 21, 2008 at 9:59 AM, Berg, T.W. (Tom) van den
[EMAIL PROTECTED] wrote:
I would like to reuse a statediagram in an overall state diagram. The
src attribute in the state tag seems to suggest this is possible.
For example the main state.xml file would contain:
state
Also, when using the src attribute, here is a general pattern that
supports good encapsulation practices:
state id=foo src=foo.xml
transition event=foo.done target=bar/
/state
state id=bar
...
/state
On Mon, Jul 21, 2008 at 11:28 AM, Rahul Akolkar [EMAIL PROTECTED] wrote:
On Mon, Jul 21,
Hi!
1. Do you have any mechanism in mind to give feedback on the result of the
operation?
Not yet, this is all work in progress. But probably changing the
FileOperation interface to
ProcessReturn process()
and add a new ProcessReturn interface with.
boolean isCorrect();
int
