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 2010/04/08 10:21:38 UTC

[jira] Created: (SLING-1479) Add JSP Tag for new script resolution

Add JSP Tag for new script resolution
-------------------------------------

                 Key: SLING-1479
                 URL: https://issues.apache.org/jira/browse/SLING-1479
             Project: Sling
          Issue Type: New Feature
          Components: Scripting
    Affects Versions: Scripting JSP-Taglib 2.0.6
            Reporter: Felix Meschberger
             Fix For: Scripting JSP-Taglib 2.0.8


SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.

This functionality should be reflected in a new JSP tag, e.g. along the lines:

    <sling:call script=... resource=... resourceType=... noResourceType=.... />

where:

    script is a path to a script
    resource is a resource whose resource type hierarchy is used to resolve the script
    resourceType is a resource type hierarchy to resolve the script
    noResourceType prevents using resource type hiearchy if set to true (default: false)

If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

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


[jira] Assigned: (SLING-1479) Add JSP Tag for new script resolution

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

Carsten Ziegeler reassigned SLING-1479:
---------------------------------------

    Assignee: Carsten Ziegeler

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.0.8
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

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


[jira] Resolved: (SLING-1479) Add JSP Tag for new script resolution

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

Carsten Ziegeler resolved SLING-1479.
-------------------------------------

    Resolution: Fixed

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.1.0
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (SLING-1479) Add JSP Tag for new script resolution

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857002#action_12857002 ] 

Carsten Ziegeler commented on SLING-1479:
-----------------------------------------

I've created a new version (1.1) for the new tag, so if you want to use it you have to reference the new taglib, the old taglib (1.0) is still available for compatiblity.
Changed in revision: 934075

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.1.0
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (SLING-1479) Add JSP Tag for new script resolution

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857741#action_12857741 ] 

Carsten Ziegeler commented on SLING-1479:
-----------------------------------------

Agreed, renamed in revision 934704

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.1.0
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (SLING-1479) Add JSP Tag for new script resolution

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857195#action_12857195 ] 

Felix Meschberger commented on SLING-1479:
------------------------------------------

How about renaming the old taglib.tld to taglib10.tld to consistently include the version number in the file name ? Since this is an internal name only, this should not have any impact on users, right ?

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.1.0
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (SLING-1479) Add JSP Tag for new script resolution

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855962#action_12855962 ] 

Carsten Ziegeler commented on SLING-1479:
-----------------------------------------

Added a first implementation in revision 933231

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.1.0
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [jira] Commented: (SLING-1479) Add JSP Tag for new script resolution

Posted by Felix Meschberger <fm...@gmail.com>.
Hi,

On 08.04.2010 10:25, Carsten Ziegeler (JIRA) wrote:
> I think a slightly better name for the tag would be <sling:eval>

Sounds good.

Regards
Felix

[jira] Commented: (SLING-1479) Add JSP Tag for new script resolution

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854864#action_12854864 ] 

Carsten Ziegeler commented on SLING-1479:
-----------------------------------------

I think a slightly better name for the tag would be <sling:eval>

> Add JSP Tag for new script resolution
> -------------------------------------
>
>                 Key: SLING-1479
>                 URL: https://issues.apache.org/jira/browse/SLING-1479
>             Project: Sling
>          Issue Type: New Feature
>          Components: Scripting
>    Affects Versions: Scripting JSP-Taglib 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Scripting JSP-Taglib 2.0.8
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
>     <sling:call script=... resource=... resourceType=... noResourceType=.... />
> where:
>     script is a path to a script
>     resource is a resource whose resource type hierarchy is used to resolve the script
>     resourceType is a resource type hierarchy to resolve the script
>     noResourceType prevents using resource type hiearchy if set to true (default: false)
> If neither resource nor resource type are declared, the script is resolved according to the type hierarchy of the request's resource.

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