commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fasih" <fasihullah.ask...@baypackets.com>
Subject Re: [SCXML]: BUG: Inner States with no InitialState
Date Sat, 08 Apr 2006 15:16:15 GMT
Sorry for the typo I did mean <initial>. Though many such errors can be 
caught with DTD, there will be many more that would not be.The most common 
would be typo in event names. I was thinking if we can compile the SCXML 
somehow.
For validation of events, maybe we could generate a class ConnectionEvent 
extends Event for "connection.xxxx" events
Restrict the creaion of TriggerEvent to the package, and have a method 
fire() on the generated class.

For model consistency, we can have a ModelValidationFramework, which would 
fire all events that a state can transition into + an error state to see the 
behaviour of the Model. I dont think that would be very difficult. I am 
actually planning to do that for my work coz in my case, my scxml will be 
written by end users. And I want to make sure that they dont make silly 
mistakes that are not caught easily.

Comments?

+Fasih
----- Original Message ----- 
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Sent: Saturday, April 08, 2006 12:50 AM
Subject: Re: [SCXML]: BUG: Inner States with no InitialState


On 4/7/06, Fasih <fasihullah.askiri@baypackets.com> wrote:
> Hi
> With reference to my last mail. I tried to add the rest of the states as 
> child state to the one which does the default error handling(I had missed 
> out the <initialstate>). I get a NullPointerException.
> The problem is with:
> http://jakarta.apache.org/commons/sandbox/scxml/xref/org/apache/commons/scxml/io/SCXMLDigester.html#955
> It checks for a null, and continues using the state. How do I file a BUG?
>
<snip/>

True, an interesting exercise would be to author many illegal SCXML
documents (with different anomalies) and ensure that the failures are
always in the best possible places and with decent error reporting
(rather than an NPE). In this case, its obvious that after logging the
error, we shouldn't continue. Probably makes sense to die with a
ModelException. Not having an <initial> defined (I assume
<initialstate> is just a typo, given the line number you point to) is
probably a common authoring faux pas, but thats not the only one.
Furthermore, many of these can't be caught with a DTD, or even a
schema.

Please follow the guidelines on the Commons SCXML issue tracking page
[1] to file a bug for this. If you also want to suggest a patch,
information about creating patches is here [2] (please attach patches
to the bugzilla ticket, rather than sending to the mailing lists --
need to change that text on the website). Thanks.

-Rahul

[1] http://jakarta.apache.org/commons/sandbox/scxml/issue-tracking.html
[2] http://jakarta.apache.org/commons/patches.html


> +Fasih
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Mime
View raw message