Project: mulestudio
Issue STUDIO-2885: Incorrect XML is generated when changing the transaction demarcation of nested transactions
XML is incorrectly generated when a flow contains nested transactions Say you have two transaction scopes, the second being inside the first. The XML would look as follows: {code:xml} ... {code} When changing the demarcation of the first transaction, such as Multi-Transactional, the generated XML would be incorrectly generated as follows: {code:xml} ... {code} Steps to reproduce: 1) Create two transaction scopes, where one is nested inside the other. 2) Place a widget inside the inner-most transaction scope 3) Attempt to change the demarcation of the outer transaction scope. This bug causes the Message Flow canvas and the generated XML to go out of sync. Attempting to delete every transaction scope from the Message Flow canvas after reproducing this bug does not remove the XML.
Story points: 8