[
https://issues.apache.org/jira/browse/FELIX-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-3225.
------------------------------------
Resolution: Invalid
This always has been implemented except for the delayed registration, which I
will report a different issue for.
> Support flexible use of HttpContext implementations for Servlet whiteboard
> pattern
> ----------------------------------------------------------------------------------
>
> Key: FELIX-3225
> URL: https://issues.apache.org/jira/browse/FELIX-3225
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
> Affects Versions: http-2.2.0
> Reporter: Felix Meschberger
>
> The servlet registration whiteboard pattern is great. But it lacks
> functionality to use a custom HttpContext implementation. This is
> particularly annoying in situations where a custom implementation is required
> e.g. for authentication purposes.
> The idea is:
> * HttpContext services are registered with an identification property, e.g.
> felix.context.id
> * Servlet services are registered with the same identification property,
> where the whiteboard support will merge the two
> * If a Servlet service is registered for which not HttpContext is
> available, the servlet is not registered with the HttpService (yet).
> * When an HttpContext is registered any registered servlet services are
> checked for whether they refer to the newly registered HttpContext
> * Likewise on HttpContext unregistration, related services must be
> unregistered from the HttpContext again
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
