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

["Robert Munteanu (JIRA)" <ji...@apache.org>]

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

Robert Munteanu updated SLING-5437:
-----------------------------------
    Attachment: 0001-SLING-5437-The-NoSQL-providers-should-throw-LoginExc.patch

Added a rough patch which works for MongoDB ( couchbase is a no-op since I did not have the time to test it ).

I'm not very eager to commit it without review since it bumps the API of `org.apache.sling.nosql.generic.adapter` to 2.0.0 .

[~sseifert@pro-vision.de] - thoughts?

> 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: Robert Munteanu
>             Fix For: NoSQL Generic Resource Provider 1.0.2, NoSQL Couchbase Client 1.0.2, NoSQL MongoDB Resource Provider 1.0.2
>
>         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)