You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/01/19 18:49:39 UTC

[jira] [Resolved] (SLING-5437) The NoSQL providers should throw LoginException if the connection to the NoSQL database can't be established

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

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

Completed: At revision: 1725576  

added check for couchbase as well and some more refactoring about automatic index creation to ensure it takes only place after successful connection check.

> The NoSQL providers should throw LoginException if the connection to the NoSQL database can't be established
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-5437
>                 URL: https://issues.apache.org/jira/browse/SLING-5437
>             Project: Sling
>          Issue Type: New Feature
>          Components: NoSQL
>    Affects Versions: NoSQL Generic Resource Provider 1.0.0, NoSQL Couchbase Resource Provider 1.0.0, NoSQL MongoDB Resource Provider 1.0.0
>            Reporter: Robert Munteanu
>            Assignee: Stefan Seifert
>             Fix For: NoSQL Generic Resource Provider 1.1.0, NoSQL Couchbase Resource Provider 1.1.0, NoSQL MongoDB Resource Provider 1.1.0
>
>         Attachments: 0001-SLING-5437-The-NoSQL-providers-should-throw-LoginExc.patch
>
>
> While trying to find a proper test for SLING-5217, I noticed that the NoSQL providers don't check the connection when the ResourceProvider is instantiated. Therefore the ResourceProvider is always considered valid and when access is attempted exceptions are thrown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)