Actions generally act as templates, requiring external configuration in order to perform their tasks. For example, a
PrintMessage action might use a property named message to indicate what to print and another property called repeatCount to indicate the number of times to print it. If so, the action configuration in the
jboss-esb.xml file should look like this:
<action name="PrintAMessage" class="test.PrintMessage">
<property name="information" value="Hello World!" />
<property name="repeatCount" value="5" />
How this configuration is then mapped on to the action instance will depend on the type of action.