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

Posted to dev@sling.apache.org by "Dan Klco (JIRA)" <ji...@apache.org> on 2012/12/06 16:45:09 UTC

[jira] [Created] (SLING-2695) SlingServletResolver Logging

Dan Klco created SLING-2695:
-------------------------------

             Summary: SlingServletResolver Logging
                 Key: SLING-2695
                 URL: https://issues.apache.org/jira/browse/SLING-2695
             Project: Sling
          Issue Type: Improvement
          Components: Servlets
    Affects Versions: Servlets Resolver 2.2.0
            Reporter: Dan Klco
            Priority: Minor


There are two odd things (to me at least) about the Sling Servlet Resolver.  First, the logger for this class is public static final, which means it is effectively a global variable.  It is actually referenced outside the class in the AbstractResourceCollector.  

Second, when the Sling Servlet Resolver is going to resolve a request and if finds that the request path is not in the servletresolver.paths set of allowed paths, it sends a log message to the getRequestProgressTracker, but I would think it should log at least an info message to the logs, letting the developer know that the script is not going to be executed.

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