Link Search Menu Expand Document

MessageEventChecker

The MessageEventChecker processes BPMN models and checks whether a MessageEvent refers to a concrete message and names it accordingly. It validates that there exists a message and a message name for StartEvents, EndEvents, IntermediateThrowEvents, BoundaryEvents and additionally of ReceiveTasks. All message names can be plain strings or consist of expressions, except for StartEvents with one further exception: StartEvents of a subprocess may use expressions.

Assumptions

  • The BPMN-models have to be in the classpath at build time

Configuration

The rule should be configured as follows:

<rule>
  <name>MessageEventChecker</name>
  <state>true</state>
</rule>

Error messages

No message has been specified for %MessageEvent%

This message indicates that no message or message name was specified for a given MessageEvent.

Examples

Correct usage
Correct usage of message event
No Message Name
No message name specified
No Message
No message at all specified