[
https://issues.apache.org/jira/browse/SLING-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597390#action_12597390
]
Felix Meschberger commented on SLING-457:
-----------------------------------------
By running the testcases committed in Rev. 656974, I was able to reproduce this
issue.
The problem was, that the SlingRequestDispatcher uses its own ResourceWrapper
implementation overwriting the getResourceType() method. But the
getResourceSupertType() was not overwritten, which caused the respective method
of wrapped resource to be called. That method, though, relies on the original
resource type and thus may result in the wrong resource super type returned.
In Rev. 656972 the resource wrapper implements the getResourceSuperType()
method employing the same semantics as used by the JcrItemResource
implementation.
Currently, code is still copied. Will implement a better solution preventing
code copying.
Implemented the fix in Rev. 656972 and committed the test cases in Rev. 656974.
> script include problem with selectors
> -------------------------------------
>
> Key: SLING-457
> URL: https://issues.apache.org/jira/browse/SLING-457
> Project: Sling
> Issue Type: Bug
> Components: Servlets Resolver
> Affects Versions: 2.0.0
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
>
> i have a base resource type /a with a script /a/foo.html.jsp
> then i have a extended resource type /b
> when i have content "/xyz" with resourcetype /b, and a request to
> "/xyz.foo.html" then it works.
> but when i have an include <sling:include path="./image.foo.html"
> resourceType="b"/> it does not. when i specify the base resource type, it
> works.
> it seams like the include resolution does not respect the selectors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
