[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566489#action_12566489 ]
Tobias Bocanegra commented on SLING-227: ---------------------------------------- > This might also be caused by the situation, that the > ResourceResolver.resolve(String) method is implemented as ... that's what i meant :-) maybe we should split those methods: ResourceResolver.resolve(String) ResourceResolver.resolveFromURL(String) and remove any path scanning logic from the first one. so you always know what you get. > sling:include tag: use ResourceResolver.resolve(String) method to get the > resource > ---------------------------------------------------------------------------------- > > Key: SLING-227 > URL: https://issues.apache.org/jira/browse/SLING-227 > Project: Sling > Issue Type: Bug > Components: JSP > Reporter: Felix Meschberger > Assignee: Felix Meschberger > Fix For: 2.0.0 > > > In case of using the path attribute of the sling:include tag, the resource is > resolved from that path using the ResourceResolver.getResource() method. If > the path contains any selectors and/or extension, the getResource() method > fails. > The sling:include tag should be fixed to request a RequestDispatcher based on > the path if the path attribute is given instead of resolving the resource > itself, because this duplicates code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.