[ 
https://issues.apache.org/jira/browse/SLING-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033615#comment-18033615
 ] 

Konrad Windszus edited comment on SLING-12978 at 11/30/25 6:56 PM:
-------------------------------------------------------------------

Fixed in 
https://github.com/apache/sling-org-apache-sling-api/commit/0f3a152fe9999fd276910c10d6a5ac39acf1f405
 and 
https://github.com/apache/sling-org-apache-sling-api/commit/61ef2599dd0a023956ae7bb1e459b3fdadf360ad.

Adjusted the site in 
https://github.com/apache/sling-site/commit/a068e949b70f4b7f30b8c1faaabcbff4962f0a63.


was (Author: kwin):
Fixed in 
https://github.com/apache/sling-org-apache-sling-api/commit/0f3a152fe9999fd276910c10d6a5ac39acf1f405.

> 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)

Reply via email to