You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/01/13 00:37:59 UTC

[jira] Moved: (JCRRMI-3) Session.isLive() and logout() throw exceptions

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

Jukka Zitting moved JCR-1933 to JCRRMI-3:
-----------------------------------------

          Component/s:     (was: jackrabbit-jcr-rmi)
    Affects Version/s:     (was: 1.5.0)
             Workflow: no-reopen-closed, patch-avail  (was: jira)
                  Key: JCRRMI-3  (was: JCR-1933)
              Project: Jackrabbit JCR-RMI  (was: Jackrabbit)

> Session.isLive() and logout() throw exceptions
> ----------------------------------------------
>
>                 Key: JCRRMI-3
>                 URL: https://issues.apache.org/jira/browse/JCRRMI-3
>             Project: Jackrabbit JCR-RMI
>          Issue Type: Bug
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> The two methods will throw an exception in case the remote session is not available anymore. For most other methods an exception is OK in that case, but I think for the methods isLive() and logout() (both do not declare any exception) a client expects a different behavior. I propose we change it as follows:
> - Session.isLive(): return false if remote session is not available anymore
> - Session.logout(): write a log message, but do not throw a runtime exception.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.