[
https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795960#action_12795960
]
Felix Meschberger commented on FELIX-1962:
------------------------------------------
The drawback of adding support for other listeners (ServletContext and
HttpSession*) is that this requires more involvement.
For the ServletContextListener we would have to add lifecycle support to our
ServletContextImpl (not that hard, maybe possible with reference counting for
registered servlets and resources).
For the HttpSession* listeners we might have to hook into the environment:
* The embedded Jetty container is not hard (had an early prototype with this)
* The proxy/bridge case is harder since it requires the embedding to register
HttpSession*Listener which may be proxied
(had an early prototype, too) The problem is that like for servlets a
special setup and proxy is required in the "outer web app"
> Add support for (select) Servlet API listeners
> ----------------------------------------------
>
> Key: FELIX-1962
> URL: https://issues.apache.org/jira/browse/FELIX-1962
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
> Affects Versions: http-2.0.4
> Reporter: Felix Meschberger
> Fix For: http-2.0.6
>
> Attachments: FELIX-1962.patch
>
>
> The new Http Service implementation currently does not support any Servlet
> API listeners at all. Support for some listeners can easily be implemented in
> a transparent way: ServletContextAttributeListener, ServletRequestListener,
> ServletRequestAttributeListener.
> The HttpSession listeners can probably not easily be implemented in such a
> transparent way.
> The ServletContextListener is probably not worth it supporting. Most (if not
> all) use cases for ServletContextListeners in traditional web applications
> can be solved in better ways in an OSGi framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
