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 (Reopened) (JIRA)" <ji...@apache.org> on 2012/02/02 12:15:53 UTC
[jira] [Reopened] (SLING-2389) Separate request/access logging from
the Sling Engine
[ https://issues.apache.org/jira/browse/SLING-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reopened SLING-2389:
--------------------------------------
Oops, log files may not be created inside of ${sling.home} if the path is provided as a relative path
> Separate request/access logging from the Sling Engine
> -----------------------------------------------------
>
> Key: SLING-2389
> URL: https://issues.apache.org/jira/browse/SLING-2389
> Project: Sling
> Issue Type: Improvement
> Components: Commons, Engine
> Affects Versions: Engine 2.2.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Engine 2.2.6
>
>
> Currently the request and access log entries are generated in the Sling Engine bundle. The consequence of this is, that only requests going through the Sling Main Servlet are actually logged.
> The fix is to hook the request and access logging infrastructure into the serlvet container as a Servlet API Filter such as to run it as early and late as possible and more importantly on a global level to catch all requests.
> In addition, since this filter has nothing to do with the Sling Engine, it would make sense to create a bundle in the commons area along with the commons/log and commons/logservice bundles.
--
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