You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (JIRA)" <ji...@apache.org> on 2012/11/04 02:41:11 UTC

[jira] [Commented] (SLING-2644) Make the jackrabbit/accessmanager and jackrabbit/usermanager to work with newer servlets/post bundle

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

Eric Norman commented on SLING-2644:
------------------------------------

Looks ok to me.  Just make sure to change the version number on the exported packages since the signature of some methods has changed.
                
> Make the jackrabbit/accessmanager and jackrabbit/usermanager to work with newer servlets/post bundle
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-2644
>                 URL: https://issues.apache.org/jira/browse/SLING-2644
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Mike Müller
>            Assignee: Mike Müller
>            Priority: Minor
>             Fix For: JCR Jackrabbit Access Manager 2.1.2
>
>         Attachments: patch.txt, patch.txt
>
>
> With SLING-1725 the package of JSONResponse was changed from 
> org.apache.sling.servlets.post.impl.helper
> to
> org.apache.sling.servlets.post
> This change was ignored in the jackrabbit/accessmanager and jackrabbit/usermanager, which imports org.apache.sling.servlets.post.impl.helper.JSONResponse till now and uses the org.apache.sling.servlets.post version 2.1.0. To use the newer version 2.1.2 some changes have to be done
> The "old" JSONResponse extended HtmlResponse, which is deprecated by now.
> To use the "new" JSONResponse which does not extend HtmlResponse anymore different classes in the accessmanager and usermanager packages have to be changed (protected method signatures).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira