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

ASF GitHub Bot commented on SLING-3695:
---------------------------------------

GitHub user tmaret opened a pull request:

    https://github.com/apache/sling/pull/21

    SLING-3695 - TenantProvider throws NPE when listing tenants root tenant ...

    ...resource does not exist
    
    * fix NPE
    * add unit test

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tmaret/sling SLING-3695a

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/21.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #21
    
----
commit 1c065647ccd0267a8f992ff450d60031520e4f3a
Author: tmaret <tma...@adobe.com>
Date:   2014-06-24T15:35:43Z

    SLING-3695 - TenantProvider throws NPE when listing tenants root tenant 
resource does not exist
    
    * fix NPE
    * add unit test

----


> TenantProvider throws NPE when listing tenants root tenant resource does not 
> exist
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-3695
>                 URL: https://issues.apache.org/jira/browse/SLING-3695
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Tenant 1.0.2
>            Reporter: Timothee Maret
>            Priority: Minor
>              Labels: tenant
>
> The method
> org.apache.sling.tenant.TenantProvider#getTenants
> throws an NPE when the tenant root resource does not exists.
> The tenant root resource is created if needed when creating a tenant (see 
> org.apache.sling.tenant.internal.TenantProviderImpl#createTenantResource)
> A workaround is to create a tenant and remove it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to