[jboss-jira] [JBoss JIRA] Commented: (JGRP-619) Change getState semantics

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609406#comment-12609406 ] 

Bela Ban commented on JGRP-619:
-------------------------------

Replace uses of ChannelNotConnectedException and ChannelClosedException with their superclass ChannelException. This way, we don't have to add new exceptions to methods getState(), connect() (and send()) when we create subclasses of StateTransferException (for example), or add other subclasses of ChannelException

> Change getState semantics
> -------------------------
>
>                 Key: JGRP-619
>                 URL: https://issues.jboss.org/browse/JGRP-619
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.2.9, 2.3, 2.4, 2.5
>            Reporter: Vladimir Blagojevic
>            Assignee: Vladimir Blagojevic
>             Fix For: 3.0
>
>
> Currently Channel's getState method returns boolean indicating only whether state was successfully received by state receiver and not whether it was successfully processed at relevant channel listener. This anomaly lead to convoluted application code that had to do rather complicated lock synchronization and notification mechanism on the progress of entire state transfer.
> We have to simplify this process!  State receiver should simply call blocking getState and be notified in the form of Exception of anything that went wrong; be it that state could not be received at all or that it was received but could not be installed at channel listener. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira