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

Jens Lauterbach updated SLING-7744:
-----------------------------------
    Description: 
The {{org.apache.sling.servlethelpers.MockRequestPathInfo}} allows consumers to 
set almost every field except the {{suffixResource}}. Currently, the 
{{getSuffixResource()}} just throws a {{UnsupportedOperationException}}.

*I propose implementing a {{setSuffixResource}} method equivalent to all the 
other setters in this mock.*

As far as I can tell this can be easily implemented (see attached patch) and 
would improve usability of this mock a little bit.

  was:
The `org.apache.sling.servlethelpers.MockRequestPathInfo` allows consumers to 
set almost every field except the 'suffixResource`. Currently, the 
`getSuffixResource()` just throws a `UnsupportedOperationException`.

*I propose implementing a `setSuffixResource` method equivalent to all the 
other setters in this mock.*

As far as I can tell this can be easily implemented (see attached patch) and 
would improve usability of this mock a little bit.


> MockRequestPathInfo: Add Setter for SuffixResource
> --------------------------------------------------
>
>                 Key: SLING-7744
>                 URL: https://issues.apache.org/jira/browse/SLING-7744
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets, Testing
>            Reporter: Jens Lauterbach
>            Priority: Minor
>         Attachments: SLING-7744.patch
>
>
> The {{org.apache.sling.servlethelpers.MockRequestPathInfo}} allows consumers 
> to set almost every field except the {{suffixResource}}. Currently, the 
> {{getSuffixResource()}} just throws a {{UnsupportedOperationException}}.
> *I propose implementing a {{setSuffixResource}} method equivalent to all the 
> other setters in this mock.*
> As far as I can tell this can be easily implemented (see attached patch) and 
> would improve usability of this mock a little bit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to