E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (8)
View Page History
...
h4. Interceptor Using interceptor is very sensitive and must be manipulate only by power users. An non properly coded interceptor engaged in a component can lead to uncontrolled behaviors, out of the standard process.
Example of an interceptor configuration:
...{center}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;"}
|| Parameter || Description || Default || Required ||
| interceptor - class | Name of the interceptor class to implement. This class must extend the abstract class _org.ow2.petals.component.common.interceptor.Interceptor_. This class must be loadable from the component classloader, or in a dependent Shared Library classloader. | {center}\-{center} \- | {center}Yes{center} Yes |
| interceptor - name | Logical name of the interceptor instance. It can be referenced to add extended parameters by a SU Interceptor configuration. \\ | {center}\-{center} \- | {center}Yes{center} Yes |
| interceptor - active | If _true_, the Interceptor instance is activated for every SU deployed on the component. \\
If _false_, the Interceptor can be activated: \\
\-by the InterceptorManager Mbean at runtime, to activate the interceptor for every deployed SU. \\
If _false_, the Interceptor can be activated: \\
\-by the InterceptorManager Mbean at runtime, to activate the interceptor for every deployed SU. \\
\-by a SU configuration | {center}\-{center} \- | {center}Yes{center} Yes |
| param\[\] - name \\ | The name of the parameter to use for the interceptor \\ | {center}\-{center} \- | {center}No{center} No |
| param\[\] \\ | The value of the parameter to use for the interceptor | {center}\-{center} \- | {center}No{center} No |
{table-plus}