jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCRRMI-3) Session.isLive() and logout() throw exceptions
Date Tue, 24 Feb 2009 10:54:01 GMT

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

Jukka Zitting resolved JCRRMI-3.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
         Assignee: Jukka Zitting

Fixed in revision 747337.

> 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
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.0
>
>
> 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.


Mime
View raw message