Ticket #477 (closed Enhancement: fixed)
Additional Core Event: PRE_SEND_RESPONSE
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.2 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.1 |
| Keywords: | Cc: | dgf, Malte | |
| Complexity: | 3 | Area: | Application Framework / API |
| Module: | deepamehta-core |
Description
To be fired before the response is send to the client. That is exactly once per request.
This is needed as a means to let plugins set certain response headers like Last-Modified.
Note: the existing PRE_SEND_XXX events are fired multiple times if the response contains a collection (like a set of topics or a set of directives).
Change History
comment:2 Changed 11 years ago by jri
New Core Event PRE_SEND_RESPONSE (#477, #386).
Fired before the response is send to the client. That is exactly once per request.
This allows plugins to set certain response headers like Last-Modified.
New listener interface:
de.deepamehta.core.service.event.PreSendResponseListener?
Listener method:
void preSendResponse(ContainerResponse? response)
Note: ContainerResponse? is a Jersey-specific class (com.sun.jersey.spi.container.ContainerResponse?).
We should remove the Jersey dependency and move to JAX-RS 2.0 instead.
See ticket 477.
See ticket 386.
Changeset: 1676101075ebb2789642fe7770d0595cb0d1a97e
