Use of HttpContext to determine filter invocation makes filters unusable with
OSGi service spec example section 102.3
----------------------------------------------------------------------------------------------------------------------
Key: PAXWEB-97
URL: http://issues.ops4j.org/jira/browse/PAXWEB-97
Project: Pax Web
Issue Type: Improvement
Components: WebContainer
Affects Versions: 0.4.1
Environment: Equinox / Jetty, Windows XP, etc. Problem is with
contract, not environment
Reporter: Ed Grossenbacher
Assignee: Alin Dreghiciu
WebContainer .registerFilter appears to only invoke the Filter for incoming
requests that have the same HttpContext.
Per the OSGi r4 service compendium, section 102.3 "Registering Resources",
there is an example where they call HttpService.registerResource with a custom
HttpContext object that knows how to do resource lookup (via getResource) for
particular bundles. This means that if I have a number of bundles that want to
register resources, I end up with a number of HttpContext objects, one per
Bundle.
The problem is, if I register a filter on a url, like /* for example, I would
*expect* it to apply to all URLs. But it doesn't, because the HttpContext
objects used to registerResource(...) are obviously not the same as the
HttpContext object used to registerFilter(...).
This behavior seems surprising - I would expect registerFilter(...) to work at
the URL level. How can I accomplish what I'm trying to do here?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
