Details
-
Enhancement
-
Resolution: Obsolete
-
Major
-
None
-
7.8.0.GA
-
False
-
False
-
Undefined
-
---
-
---
Description
In process designer, all of the nodes below have similar warning Error messages in Alerts panel: "unable to parse xml : Exception class java.lang.IllegalArgumentException with specific messages:
- Two start nodes on canvas:
- "A RuleFlowProcess cannot have more than one start node!"
- Error, Escalation and Compensation intermediate catching events without incoming sequence flows:
- "Event node 'null' [1] has no incoming connection".
- Furthermore, Error event cannot even cannot have incoming connection, so the message shouldn't be there at all.
- All Message events:
- "No messages found"
- Both intermediate catching and throwing Link events:
- "These nodes do not have a name"
- Intermediate throwing Escalation event:
- "General escalation is not yet supported"
- End Escalation event:
- "End events throwing an escalation must throw specific escalations (and not general ones)"
- Service task:
- "Interface name is required attribute"
- Parallel, Exclusive and Inclusive gateways:
- "Unknown gateway direction: Unspecified"
The messages mentioned above should be changed to a different format since the process can be parsed.
[Draft] Acceptance criteria
The messages mentioned above are changed to messages with format similar to:
- "Process 'PROCESS_NAME' [POJECT_NAME.PROCESS_NAME]: Node 'NODE_NAME' [NODE_NUMBER] Has no connection to the start node." or
"[NODE] NODE_NAME has no outgoing connection.", etc..
"unable to parse xml" messages are shown only in case the process cannot be parsed.
Attachments
Issue Links
- clones
-
JBPM-9408 Stunner - Change "Unable to parse xml" validation messages in Alerts panel
- Pull Request Sent