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 2007/12/20 12:30:43 UTC

[jira] Updated: (SLING-3) Use RequestProgressTracker to log request processing steps

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

Felix Meschberger updated SLING-3:
----------------------------------

      Component/s: ServletResolver
                   Scripting
                   Resource
                   JSP
    Fix Version/s: 2.0.0
      Description: The RequestProgressTacker interface defines an API which may be used to track the process of request processing. Parties taking part in request processing, most notably resource resolution, script and servlet resolution and also request filters should track their progress in the tracker.  (was: It would be nice to be able to use Sling logging in developer training, to see how Content and Component selection works, in real time.

Work on the log messages of the main classes involved in this (URLMapperFilter, ComponentResolverFilter, Mapping, etc) so that the DEBUG log helps in understanding how things work.)
          Summary: Use RequestProgressTracker to log request processing steps  (was: Improve logging in URLMapperFilter and ComponentResolverFilter)

Retarget the issue to the new Sling API and module structure

> Use RequestProgressTracker to log request processing steps
> ----------------------------------------------------------
>
>                 Key: SLING-3
>                 URL: https://issues.apache.org/jira/browse/SLING-3
>             Project: Sling
>          Issue Type: Improvement
>          Components: Core, JSP, Resource, Scripting, ServletResolver
>            Reporter: Felix Meschberger
>             Fix For: 2.0.0
>
>
> The RequestProgressTacker interface defines an API which may be used to track the process of request processing. Parties taking part in request processing, most notably resource resolution, script and servlet resolution and also request filters should track their progress in the tracker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.