You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/10/16 12:23:03 UTC

[jira] [Resolved] (SLING-2397) Logging Panel not always provided

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

Felix Meschberger resolved SLING-2397.
--------------------------------------

    Resolution: Fixed

Fixed in Rev. 1398715 and 1398716 by dynamically importing the Servlet API and registering the panel as a ServiceFactory. This way the actual class is only created when actually used  and this only happens if the Servlet API is available.
                
> Logging Panel not always provided
> ---------------------------------
>
>                 Key: SLING-2397
>                 URL: https://issues.apache.org/jira/browse/SLING-2397
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Log 2.1.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Commons Log 3.0.2
>
>
> The "Sling Log Support" Web Console page has a problem when the log bundle is started without Servlet API wiring. In this case the panel is not available and can only be made available upon rewiring the log bundle.
> Fix:
>  - Register plugin as a ServiceFactory to lazily instantiate the class when required/used
>  - dynamically import the servlet API to lazily wire when required

--
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