There are no default processors. If no processor is specified, no processor is run on context initialization or destruction. This allows configuring a listener with only an initialization pipeline, only a destruction pipeline, both, or none.
|
|
OPS User Guide
|
Listeners1. Servlet Context ListenerThe OPS Servlet Context Listener allows configuring one processor to be called when the Servlet context is initialized, and one to be called when the Servlet context is destroyed. These processors are looked up in the following locations, in this order:
Not every processor can be run from those pipelines, because the execution context is limited. In particular, you can't call processors like the Request generator, or any HTTP serializers. You have access to the Application context.
For the OPS Servlet Context Listener to be called, you need to
configure the following listener in your
<listener> <listener-class>org.orbeon.oxf.webapp.OXFServletContextListener</listener-class> </listener>
Note
There are no default processors. If no processor is specified, no processor is run on context initialization or destruction. This allows configuring a listener with only an initialization pipeline, only a destruction pipeline, both, or none. 2. Session ListenerThe OPS Session Listener allows configuring one processor to be called when the Session is created, and one to be called when the Session is destroyed. These processors are looked up in the following locations, in this order:
Not every processor can be run from those pipelines, because the execution context is limited. In particular, you can't call processors like the Request generator, or any HTTP serializers. You have access to the Application and Session contexts.
For the OPS Session Listener to be called, you need to configure the
following listener in your
<listener> <listener-class>org.orbeon.oxf.webapp.OXFSessionListener</listener-class> </listener>
Note
There are no default processors. If no processor is specified, no processor is run on session creation or destruction. This allows configuring a listener with only a creation pipeline, only a destruction pipeline, both, or none. |