[jira] [Resolved] (SLING-6935) Context-Aware web console default experience difficult

["Stefan Seifert (JIRA)" <ji...@apache.org>]

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

Stefan Seifert resolved SLING-6935.
-----------------------------------
    Resolution: Fixed

Completed: At revision: 1808876  

changes
- fix NPE when no config name is given
- default content path to /content
- fallback to web console resource resolver if no valid system user mapping is configured

producing any useful result if no config name is given is more difficult - and should be handled in a separate ticket. given "." as config name does work.

> Context-Aware web console default experience difficult
> ------------------------------------------------------
>
>                 Key: SLING-6935
>                 URL: https://issues.apache.org/jira/browse/SLING-6935
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Context-Aware Configuration Impl 1.4.2
>            Reporter: Alexander Klimetschek
>            Assignee: Stefan Seifert
>             Fix For: Context-Aware Configuration Impl 1.4.4
>
>
> A resolve with the default values doesn't give anything. Default values should be:
> * Content Path "/content"
> * other config name "."
> Which should on a typical system give you something, such as "/conf/global/settings" for example. This makes exploring the UI much simpler.
> If no config name is set, one gets a 500 error "Invalid configuration name: null".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)