You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/07/23 21:43:31 UTC

[jira] Created: (SLING-580) Improve SlingServletResolver logging to show how scripts and servlets are selected

Improve SlingServletResolver logging to show how scripts and servlets are selected
----------------------------------------------------------------------------------

                 Key: SLING-580
                 URL: https://issues.apache.org/jira/browse/SLING-580
             Project: Sling
          Issue Type: Improvement
    Affects Versions: Servlets Resolver 2.0.4
            Reporter: Bertrand Delacretaz
            Priority: Minor


The SlingServletResolver log does not currently give much detail about how scripts and servlets are selected, this can be improved.

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


[jira] Closed: (SLING-580) Improve SlingServletResolver logging to show how scripts and servlets are selected

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz closed SLING-580.
-------------------------------------

    Resolution: Fixed

Implemented in revision 679169, the SlingServletResolver debug log now indicates which scripts and servlets are candidates for selection.

Example with an nt:unstructured resource where one script is available:

SlingServletResolver resolveServlet called for Resource JcrNodeResource, type=nt:unstructured, path=/xxyz
SlingServletResolver Ordered list of Servlet candidates follows
SlingServletResolver Servlet candidate: /apps/nt/unstructured/html.esp
SlingServletResolver Servlet candidate: /apps/sling/servlet/default/GET.servlet
SlingServletResolver Servlet candidate: /apps/sling/servlet/default.servlet
SlingServletResolver Checking if candidate Resource /apps/nt/unstructured/html.esp adapts to Servlet and accepts request
SlingServletResolver getServlet returns Servlet /apps/nt/unstructured/html.esp
SlingServletResolver Servlet /apps/nt/unstructured/html.esp found for Resource=JcrNodeResource, type=nt:unstructured, path=/xxyz

Example with an resource of type foo where many scripts are available, this shows for example that the esp script has precedence over the jsp one (but does that depend on bundle loading order? didn't check):

SlingServletResolver resolveServlet called for Resource JcrNodeResource, type=foo, path=/xx
SlingServletResolver Ordered list of Servlet candidates follows
SlingServletResolver Servlet candidate: /apps/foo/html.esp
SlingServletResolver Servlet candidate: /apps/foo/html.jsp
SlingServletResolver Servlet candidate: /apps/foo/foo.esp
SlingServletResolver Servlet candidate: /apps/foo/GET.esp
SlingServletResolver Servlet candidate: /apps/sling/servlet/default/GET.servlet
SlingServletResolver Servlet candidate: /apps/sling/servlet/default.servlet
SlingServletResolver Checking if candidate Resource /apps/foo/html.esp adapts to Servlet and accepts request
SlingServletResolver getServlet returns Servlet /apps/foo/html.esp
SlingServletResolver Servlet /apps/foo/html.esp found for Resource=JcrNodeResource, type=foo, path=/xx

> Improve SlingServletResolver logging to show how scripts and servlets are selected
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-580
>                 URL: https://issues.apache.org/jira/browse/SLING-580
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Servlets Resolver 2.0.4
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> The SlingServletResolver log does not currently give much detail about how scripts and servlets are selected, this can be improved.

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


[jira] Updated: (SLING-580) Improve SlingServletResolver logging to show how scripts and servlets are selected

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated SLING-580:
------------------------------------

    Fix Version/s:  Servlets Resolver 2.0.6
         Assignee: Bertrand Delacretaz

> Improve SlingServletResolver logging to show how scripts and servlets are selected
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-580
>                 URL: https://issues.apache.org/jira/browse/SLING-580
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Servlets Resolver 2.0.4
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For:  Servlets Resolver 2.0.6
>
>
> The SlingServletResolver log does not currently give much detail about how scripts and servlets are selected, this can be improved.

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