You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/06/10 17:58:42 UTC

[jira] [Created] (SLING-2507) Thread local for resource resolver does not handle includes correctly

Carsten Ziegeler created SLING-2507:
---------------------------------------

             Summary: Thread local for resource resolver does not handle includes correctly
                 Key: SLING-2507
                 URL: https://issues.apache.org/jira/browse/SLING-2507
             Project: Sling
          Issue Type: Bug
          Components: Scripting
    Affects Versions: Scripting Core 2.0.22
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Scripting Core 2.0.24


The DefaultSlingScript sets a thread local variable to point to the resource resolver if a request object is
available. When it is finished it simply removes this.
If this is an included script, it removes the resource resolver for all scripts running after the included script

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

        

[jira] [Closed] (SLING-2507) Thread local for resource resolver does not handle includes correctly

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

Carsten Ziegeler closed SLING-2507.
-----------------------------------

    
> Thread local for resource resolver does not handle includes correctly
> ---------------------------------------------------------------------
>
>                 Key: SLING-2507
>                 URL: https://issues.apache.org/jira/browse/SLING-2507
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.22
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting Core 2.0.24
>
>
> The DefaultSlingScript sets a thread local variable to point to the resource resolver if a request object is
> available. When it is finished it simply removes this.
> If this is an included script, it removes the resource resolver for all scripts running after the included script

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

        

[jira] [Resolved] (SLING-2507) Thread local for resource resolver does not handle includes correctly

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

Carsten Ziegeler resolved SLING-2507.
-------------------------------------

    Resolution: Fixed
    
> Thread local for resource resolver does not handle includes correctly
> ---------------------------------------------------------------------
>
>                 Key: SLING-2507
>                 URL: https://issues.apache.org/jira/browse/SLING-2507
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.22
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting Core 2.0.24
>
>
> The DefaultSlingScript sets a thread local variable to point to the resource resolver if a request object is
> available. When it is finished it simply removes this.
> If this is an included script, it removes the resource resolver for all scripts running after the included script

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