[
https://issues.apache.org/jira/browse/SCXML-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar resolved SCXML-64.
--------------------------------
Resolution: Invalid
Thanks for the tests. I've added the tests you suggest in r608646 and added you
as a contributor:
http://svn.apache.org/viewvc?view=rev&revision=608646
The behavior of the tests is as expected. I am not sure why you say the same
rules are added for <state> and <transition> (that isn't true). The <datamodel>
in fails.xml is simply ignored.
As a broader statement, the SCXMLParser needs to be supplied a well-formed and
correct SCXML document. If that assumption doesn't hold, the results are
generally not defined. Moreover, the act of creating valid SCXML documents is
beyond the scope of the runtime engine (though it should try its best to
complain correctly).
Resolving again as Invalid.
> datamodel should not be allowed in transition.
> ----------------------------------------------
>
> Key: SCXML-64
> URL: https://issues.apache.org/jira/browse/SCXML-64
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.6
> Environment: win xp, java 1.5
> Reporter: Ross Yakulis
> Priority: Minor
> Attachments: fails.xml, TransitionBugTest.java,
> TransitionBugTestSuite.java, works.xml
>
>
> <transition event="my.event" target="somewhere">
> <datamodel>
> <data name="dummy" expr="somedata"/>
> </datamodel>
> <log expr="dummy" />
> <log expr="'*****' + dummy" />
> /transition>
> Given the above transition, the first log logs null, send log causes a
> nullpointerexception. Acording to the SCXML spec datamodel is not allowed in
> a transition only globally and at the state level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
