[
https://issues.apache.org/jira/browse/SLING-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652785#action_12652785
]
Felix Meschberger commented on SLING-752:
-----------------------------------------
As pointed out by Carsten in the thread at [1], it is more important to be
backwards compatible in this case.
So I will modify the JavaDoc as follows:
* resolve(HttpServletRequest) never returns null (has always been like that)
* resolve(HttpServletRequest, String) never returns null (is a new method
anyway)
* resolve(String) will return null if no resource can be resolved
[1] http://markmail.org/message/ulqwzjilp6prq75m
> JcrResourceResolver2 resolve(String) method not API conform
> -----------------------------------------------------------
>
> Key: SLING-752
> URL: https://issues.apache.org/jira/browse/SLING-752
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.4
> Reporter: christian
> Priority: Minor
> Attachments: SLING-752.patch
>
>
> Affected is the JcrResourceResolver2#resolve(abspath) method.
> If abspath argument doesn't point to an Item, the resolver returns a
> Resource of type non-existing.
> The API according its JAVA-Doc requires to return <null> in this case
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
