...
You can alternatively select a pre-defined sequence from the registry as the in/out/fault sequence for a proxy service or a REST service without adding any mediator configurations inline. The difference between these two options are described in the table below.
| Attribute | Picking a pre-defined sequence as in/out/fault sequence | Referring to a pre-defined sequence via the Sequence mediator |
|---|---|---|
| Adding other mediators | Other mediator configurations that are not already included in the pre-defined sequence cannot be added to the in/out/fault sequence. | Other mediator configurations that are not already included in the pre-defined sequence can be added to the in/out/fault sequence |
| Applying changes done to the pre-defined sequence | Any changes done to the sequence saved in the registry after it was selected as the in/out/fault sequence will not be considered when carrying out mediation. | Any changes done to the sequence saved in the registry after it was selected as the in/out/fault sequence will be considered when carrying out mediation. |
...
| Info |
|---|
The Sequence mediator is a content-unaware mediator. |
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Parameter Name | Description | |||||
|---|---|---|---|---|---|---|
| Key Type | This parameter defines whether the key to access the required sequence is a static key or a dynamic key. Possible values are as follows.
| |||||
| Referring sequence | The key to access the sequence saved in the registry. You can enter a static value selected from the resource tree, or an XPath expression based on the option you selected for the Key Type parameter.
|
Example
In this example, the following sequence named StoreSend is saved in the Configuration registry. It includes a Store Mediator to store the request in a message store named JMSMS and a Send Mediator to send it to an endpoint afterwards.
...