[
https://issues.apache.org/jira/browse/SCXML-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550644
]
Rahul Akolkar commented on SCXML-62:
------------------------------------
Ah, I see the #, whats happening here is a combination of:
* Commons SCXML does not yet support the fragment URL notation for refering to
individual states
* Using a fragment URL as-is still returns the entire document (and causes the
entire state machine to be included twice, with identical state IDs et al)
I would recommend editing this issue to change this to an enhancement request
for supporting fragment URLs in <state>'s src attribute.
> Error on sourcing in content of states multiple times
> -----------------------------------------------------
>
> Key: SCXML-62
> URL: https://issues.apache.org/jira/browse/SCXML-62
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Ingmar Kliche
>
> It is not possible to source in the content of a state (from an external
> document) multiple times into a scxml state machine (even though there are
> only transitions in the sourced state, i.e. there are no conflicts on state
> id's).
> external-02-base.xml:
> ---------------------------------
> <scxml version="1.0"
> xmlns="http://www.w3.org/2005/07/scxml";
> id="base"
> initialstate="s1">
>
> <state id="s1">
> <initial>
> <transition target="s1.s11" />
> </initial>
> <state id="s1.s11" src="external-02-src.xml#sext" />
> <state id="s1.s12" src="external-02-src.xml#sext" />
> </state>
>
> </scxml>
> external-02-src.xml:
> ----------------------------
> <scxml version="1.0"
> xmlns="http://www.w3.org/2005/07/scxml";
> id="statesrc_ext"
> initialstate="sext">
>
> <state id="sext">
> <transition event="foo" />
> </state>
>
> </scxml>
> Testcase:
> ------------------
> public void testExternal02() {
> // (1) Get a SCXMLExecutor
> exec = SCXMLTestHelper.getExecutor(external02);
> }
> Error: Initial state null or not a descendant of state with ID "s1.s11"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
