[SCXML-264] Support <invoke> with inline (<content> body) SCXML statemachine definition

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 10/Dec/17 15:23
• Updated: 10/Dec/17 22:04
• Resolved: 10/Dec/17 15:25

Description

The SCXML Invoke allows specifying the target process (another SCXML statemachine) to be defined 'inline' through a child <content> element.
The <content> element itself can either use a src expression (to load the SCXML from data) or inline body.
To support this feature the Invoker, which currently only loads another SCXML statemachine from an external resource (remote url or file path) also need to be able to parse a statemachine definition directly inline.
Because the SCXMLReader currently cannot parse XML directly, the embedded statemachine definition (XML fragment) first will be transformed back into a string, so the Invoker can use the SCXMLReader to parse a new SCXML instance.

Embedded SCXML with the <invoke> is a common and most convenient usage, and implementing this feature will fix 24 more SCXML IRP tests!

Issue Links

• incorporates: SCXML-238 idlocation not read for invoke element
• supercedes: SCXML-232 Invoke element with content as a xml node