You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/05/22 09:29:17 UTC

[jira] [Updated] (SLING-4738) MockValueMap should also throw UOE for modification operations

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

Konrad Windszus updated SLING-4738:
-----------------------------------
    Summary: MockValueMap should also throw UOE for modification operations  (was: MockValueMap should also throw UOE for remove(), put())

> MockValueMap should also throw UOE for modification operations
> --------------------------------------------------------------
>
>                 Key: SLING-4738
>                 URL: https://issues.apache.org/jira/browse/SLING-4738
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Testing ResourceResolver Mock 1.1.0
>            Reporter: Konrad Windszus
>              Labels: mocks
>
> To be closer to the original {{org.apache.sling.jcr.resource.JcrPropertyMap}} the {{org.apache.sling.testing.resourceresolver.MockValueMap}} should not be modifiable. All modification methods like put, putAll, clear and remove should throw {{UnsupportedOperationException}}s.



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