You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/09/27 21:37:07 UTC

[jira] [Resolved] (FELIX-3684) Expose the servlet registration information in HandlerRegistry through WebConsole

     [ https://issues.apache.org/jira/browse/FELIX-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved FELIX-3684.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: http-2.2.2

Thank your very much for your patch.

Applied the with some minore changes patch on http.base in Rev. 1391181:
- depend on OSGi Core 4.2 and thus prevent the reflection trick
- Omit the pattern field for filters since the Pattern class also holds this reference and returns it in the toString() method.

And applied the other part of the patch to the http.jetty module in Rev. 1391184.
                
> Expose the servlet registration information in HandlerRegistry through WebConsole
> ---------------------------------------------------------------------------------
>
>                 Key: FELIX-3684
>                 URL: https://issues.apache.org/jira/browse/FELIX-3684
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>    Affects Versions: http-2.2.0
>            Reporter: Chetan Mehrotra
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: http-2.2.2
>
>         Attachments: FELIX-3684.patch, http-service-plugin.png
>
>
> If a bundle programatically registers a servlet with the HTTP Service its not possible to determine which servlet is handling which request. This information is present in the org.apache.felix.http.base.internal.handler.HandlerRegistry. We just need to expose it through some WebConsole plugin or ConfigurationPrinter
> For more details refer to http://markmail.org/thread/oua65hrxmu45xkmq

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira