sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (SLING-2389) Separate request/access logging from the Sling Engine
Date Thu, 02 Feb 2012 10:55:53 GMT


Felix Meschberger resolved SLING-2389.

    Resolution: Fixed
      Assignee: Felix Meschberger

Assuming this fixed. For now I leave it in the Engine bundle. We can factor it out later
> Separate request/access logging from the Sling Engine
> -----------------------------------------------------
>                 Key: SLING-2389
>                 URL:
>             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
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message