[
https://issues.apache.org/jira/browse/SLING-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041292#comment-18041292
]
Konrad Windszus commented on SLING-12978:
-----------------------------------------
FTR: The implementation is at
https://github.com/apache/sling-org-apache-sling-engine/blob/229091497ffcfcb43ebcce659f0cc36b007ad5a6/src/main/java/org/apache/sling/engine/impl/request/SlingRequestPathInfo.java#L57-L102.
There was also some discussion on the mailing list at
https://lists.apache.org/thread/0xlyqxcr6d4q9cc1ylpn3tofconcklx0.
> Clarify RequestPathInfo for requests not matching a resource
> ------------------------------------------------------------
>
> Key: SLING-12978
> URL: https://issues.apache.org/jira/browse/SLING-12978
> Project: Sling
> Issue Type: Improvement
> Components: API
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: API 3.0.4
>
>
> Currently
> https://github.com/apache/sling-org-apache-sling-api/blob/master/src/main/java/org/apache/sling/api/request/RequestPathInfo.java
> has some incorrect documentation for the edge case when the request cannot
> be resolved to a Sling resource. In such a case {{getResourcePath()}} rather
> returns the full request path (including selectors/extensions and suffixes).
> Also there is some inconsistency in the javadoc regarding resource
> path/content path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
