E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (7)
View Page Historyh4. Interceptor
{anchor:cdk-su-interceptor-cfg}
Interceptors can be defined to inject some post or pre-processing in the service processing.
Interceptors can be defined to inject some post or pre-processing in the service processing.
Using interceptor is very sensitive and must be manipulated only by power users. A non properly coded interceptor engaged in a component can lead to uncontrolled behaviors, out of the standard process.
Example of an interceptor configuration:
...
{code:lang=xml} <?xml version="1.0" encoding="UTF-8"?>
<!--...-->
<!--...-->
<jbi:provides>
<!--...-->
<!--...-->
<petalsCDK:su-interceptors>
<petalsCDK:send>
<petalsCDK:send>
... </petalsCDK:accept-response>
</petalsCDK:su-interceptors>
</petalsCDK:su-interceptors>
<!--...-->
</jbi:provides>
</jbi:provides>
<!--...-->{code}
...| send-response | Interceptor dedicated to send phase, for an exchange (a response) received by a consumer | \- | No |
| accept-response | Interceptor dedicated to receive phase, for an exchange sent (a response) by a provider | \- | No |
| accept-response | Interceptor dedicated to receive phase, for an exchange sent (a response) by a provider | \- | No |
| interceptor - name | Logical name of the interceptor instance. It can be referenced to add extended parameters by a SU Interceptor configuration. | \- | Yes |
| interceptor - name | Logical name of the interceptor instance defined at component level, see [CDK Interceptor configuration|#cdk-component-interceptor-cfg]. | \- | Yes |
| param\[\] - name | The name of the parameter to use for the interceptor for this SU | \- | No |
| param\[\] | The value of the parameter to use for the interceptor for this SU | \- | No |
| param\[\] | The value of the parameter to use for the interceptor for this SU | \- | No |
...