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 2018/08/19 20:56:00 UTC
[jira] [Updated] (SLING-7831) support injecting custom/alternate
PostResponse implementations for the servlets in the usermanager and
accessmanager bundles
[ https://issues.apache.org/jira/browse/SLING-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman updated SLING-7831:
-------------------------------
Affects Version/s: Launchpad Integration Tests 1.0.6
> support injecting custom/alternate PostResponse implementations for the servlets in the usermanager and accessmanager bundles
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-7831
> URL: https://issues.apache.org/jira/browse/SLING-7831
> Project: Sling
> Issue Type: Bug
> Affects Versions: JCR Jackrabbit User Manager 2.2.6, JCR Jackrabbit Access Manager 3.0.0, Launchpad Integration Tests 1.0.6
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
>
> The changes from SLING-2223 added support for custom PostResponse implementations in the main sling post servlet, but the same changes were not done for the similar implementations from these other locations:
> 1. AbstractPostServlet#createHtmlResponse in the org.apache.sling.jcr.jackrabbit.usermanager bundle
> 2. AbstractAccessPostServlet#createHtmlResponse in the org.apache.sling.jcr.jackrabbit.accessmanager bundle.
>
>
> Adding the same support in those additional locations should make it possible for the developer to provide more user friendly UI when something goes wrong in usermanager or accessmanager POST calls.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)