Bug 449079 - Have ProtocolVersionException dispatched to client
Summary: Have ProtocolVersionException dispatched to client
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-28 12:08 EDT by Esteban DUGUEPEROUX CLA
Modified: 2020-12-11 10:46 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esteban DUGUEPEROUX CLA 2014-10-28 12:08:25 EDT
Currently when we use a cdo client with a protocol version, as defined by CDOProtocolConstants.PROTOCOL_VERSION, different of the one of server, the server throw a ProtocolVersionException which is catched by the net4j channel layer which dispatch a ChannelException to the client.
The client can receive a ChannelException for different reasons, but to distinguish protocol version mismatch reason of other ones, he must parse the exception message.
It would be more convenient to have ProtocolVersionException type accessible to client, for example by putting it in cdo.common or net4j.util plugin, and having this exception thrown to the client.
Comment 1 Esteban DUGUEPEROUX CLA 2014-10-28 12:14:02 EDT
A first draft : https://git.eclipse.org/r/#/c/35598/
ChannelException should give more information about issue, in this case we need type of issue, protocol version mismatch, and the client and server protocol version to give feedback to end-user that it use an older or newer CDO client.
Comment 2 Eike Stepper CLA 2015-07-14 02:20:15 EDT
Moving all open bugzillas to 4.5.
Comment 3 Eike Stepper CLA 2016-07-31 01:03:01 EDT
Moving all unaddressed bugzillas to 4.6.
Comment 4 Eike Stepper CLA 2017-12-28 01:19:19 EST
Moving all open bugs to 4.7
Comment 5 Eike Stepper CLA 2019-11-08 02:17:47 EST
Moving all unresolved issues to version 4.8-
Comment 6 Eike Stepper CLA 2019-12-13 12:48:04 EST
Moving all unresolved issues to version 4.9
Comment 7 Eike Stepper CLA 2020-12-11 10:46:46 EST
Moving to 4.13.