Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364532 - [DB] Fetching non-existent CDOID from DBStore throws wrong exception
Summary: [DB] Fetching non-existent CDOID from DBStore throws wrong exception
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.db (show other bugs)
Version: 4.13   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 22:40 EST by Caspar D. CLA
Modified: 2020-12-11 10:47 EST (History)
2 users (show)

See Also:

Attachments
Stacktrace (2.62 KB, text/plain)
2011-11-22 22:40 EST, Caspar D. CLA 		no flags Details
Testcase (as patch) (2.23 KB, patch)
2011-11-23 03:33 EST, Caspar D. CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Caspar D. CLA 2011-11-22 22:40:56 EST 
Created attachment 207397 [details]
Stacktrace

Fetching a non-existent CDOID from MEMStore gives ObjectNotFoundException,
which makes sense.

Doing the same on a DBStore gives a RemoteException wrapping an ISE.
Comment 1 Caspar D. CLA 2011-11-22 22:45:36 EST 
Note also (see stacktrace) that the exception thrown suggests that the
specific problem is the absence of type information for that ID. In fact,
there is simply no object by that ID at all. Perhaps the DBStore should 
catch and "translate" the exception. In any case, for a given scenario, 
the client should be presented with the same exception from all stores.
Comment 2 Eike Stepper CLA 2011-11-22 23:47:01 EST 
(In reply to comment #1)
> [...] In any case, for a given scenario, 
> the client should be presented with the same exception from all stores.

+1

That reminds me to bug 336318...
Comment 3 Caspar D. CLA 2011-11-23 03:32:17 EST 
Not reproducible in 4.1.
Comment 4 Caspar D. CLA 2011-11-23 03:33:08 EST 
Created attachment 207402 [details]
Testcase (as patch)
Comment 5 Eike Stepper CLA 2012-06-05 07:28:34 EDT 
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems.

Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Comment 6 Eike Stepper CLA 2012-08-14 22:50:31 EDT 
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 7 Eike Stepper CLA 2013-06-29 12:16:10 EDT 
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 8 Eike Stepper CLA 2015-07-14 02:07:42 EDT 
Moving all open bugzillas to 4.5.
Comment 9 Eike Stepper CLA 2016-07-31 00:50:32 EDT 
Moving all unaddressed bugzillas to 4.6.
Comment 10 Eike Stepper CLA 2017-12-28 01:13:40 EST 
Moving all open bugs to 4.7
Comment 11 Eike Stepper CLA 2019-11-08 02:09:25 EST 
Moving all unresolved issues to version 4.8-
Comment 12 Eike Stepper CLA 2019-12-13 12:49:25 EST 
Moving all unresolved issues to version 4.9
Comment 13 Eike Stepper CLA 2020-12-11 10:47:17 EST 
Moving to 4.13.