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 2009/06/26 16:05:07 UTC
[jira] Created: (SLING-1024) Correct resource super type handling
Correct resource super type handling
------------------------------------
Key: SLING-1024
URL: https://issues.apache.org/jira/browse/SLING-1024
Project: Sling
Issue Type: Improvement
Components: API, JCR Resource
Affects Versions: API 2.0.4, JCR Resource 2.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: API 2.0.6, JCR Resource 2.0.6
A resource should only return a super resource type if it has configured one.
Currenty the jcr resource node implementation does a lookup of the resource representing its resource type to get the resource super type from there if it doesn't have a super type set.
This logic should solely be called from the script resolver (and not be tied to a resource implementation).
In this respect, the bundle resource should return "sling/bundle/resource" as it's super type and not null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1024) Correct resource super type handling
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1024:
------------------------------------
Component/s: Engine
Affects Version/s: Engine 2.0.4
Fix Version/s: Engine 2.0.6
> Correct resource super type handling
> ------------------------------------
>
> Key: SLING-1024
> URL: https://issues.apache.org/jira/browse/SLING-1024
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine, JCR Resource
> Affects Versions: JCR Resource 2.0.4, Engine 2.0.4, API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Engine 2.0.6, API 2.0.6, JCR Resource 2.0.6
>
>
> A resource should only return a super resource type if it has configured one.
> Currenty the jcr resource node implementation does a lookup of the resource representing its resource type to get the resource super type from there if it doesn't have a super type set.
> This logic should solely be called from the script resolver (and not be tied to a resource implementation).
> In this respect, the bundle resource should return "sling/bundle/resource" as it's super type and not null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1024) Correct resource super type handling
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1024.
-----------------------------------
Resolution: Fixed
> Correct resource super type handling
> ------------------------------------
>
> Key: SLING-1024
> URL: https://issues.apache.org/jira/browse/SLING-1024
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine, JCR Resource, Servlets Resolver
> Affects Versions: Servlets Resolver 2.0.6, JCR Resource 2.0.4, Engine 2.0.4, API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Servlets Resolver 2.0.8, Engine 2.0.6, API 2.0.6, JCR Resource 2.0.6
>
>
> A resource should only return a super resource type if it has configured one.
> Currenty the jcr resource node implementation does a lookup of the resource representing its resource type to get the resource super type from there if it doesn't have a super type set.
> This logic should solely be called from the script resolver (and not be tied to a resource implementation).
> In this respect, the bundle resource should return "sling/bundle/resource" as it's super type and not null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1024) Correct resource super type handling
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1024:
------------------------------------
Component/s: Servlets Resolver
Affects Version/s: Servlets Resolver 2.0.6
Fix Version/s: Servlets Resolver 2.0.8
Fixed as described above in Revision: 788719.
> Correct resource super type handling
> ------------------------------------
>
> Key: SLING-1024
> URL: https://issues.apache.org/jira/browse/SLING-1024
> Project: Sling
> Issue Type: Improvement
> Components: API, Engine, JCR Resource, Servlets Resolver
> Affects Versions: Servlets Resolver 2.0.6, JCR Resource 2.0.4, Engine 2.0.4, API 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Servlets Resolver 2.0.8, Engine 2.0.6, API 2.0.6, JCR Resource 2.0.6
>
>
> A resource should only return a super resource type if it has configured one.
> Currenty the jcr resource node implementation does a lookup of the resource representing its resource type to get the resource super type from there if it doesn't have a super type set.
> This logic should solely be called from the script resolver (and not be tied to a resource implementation).
> In this respect, the bundle resource should return "sling/bundle/resource" as it's super type and not null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.