You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/02/03 10:46:34 UTC

[jira] [Updated] (SLING-4384) MockResourceResolver: Methods that are not implemented should throw UnsupportedOperationException

     [ https://issues.apache.org/jira/browse/SLING-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert updated SLING-4384:
----------------------------------
    Summary: MockResourceResolver: Methods that are not implemented should throw UnsupportedOperationException   (was: MockResourceResolver.findResources and queryResources should throw UnsupportedOperationException instead of returning an empty list)

this applies to the following ResourceResolver API methods:
* findResources(String, String)
* queryResources(String, String)
* resolve(HttpServletRequest)
* getParentResourceType(Resource)
* getParentResourceType(String)
* clone(Map)

> MockResourceResolver: Methods that are not implemented should throw UnsupportedOperationException 
> --------------------------------------------------------------------------------------------------
>
>                 Key: SLING-4384
>                 URL: https://issues.apache.org/jira/browse/SLING-4384
>             Project: Sling
>          Issue Type: Bug
>    Affects Versions: Testing ResourceResolver Mock 1.1.2
>            Reporter: Konrad Windszus
>            Assignee: Stefan Seifert
>
> I would prefer if all non-supported operations would rather throw an {{UnsupportedOperationException}} instead of just returning an empty list. That way the missing features become more obvious and every test which is using the non-implemented features will automatically fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)