Bug 202621 - Cannot open workspace with connections of unknown systemType
Summary: Cannot open workspace with connections of unknown systemType
Status: RESOLVED DUPLICATE of bug 202416
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P2 major (vote)
Target Milestone: 2.0.1   Edit
Assignee: David Dykstal CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on: 202416
Blocks:
  Show dependency tree
 
Reported: 2007-09-07 08:59 EDT by Martin Oberhuber CLA
Modified: 2007-09-10 22:00 EDT (History)
1 user (show)

See Also:

Attachments
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 Martin Oberhuber CLA 2007-09-07 08:59:33 EDT 
When a single workspace is used by multiple Eclipse installations, the following problem can occur:

* Installation A has all connection types installed. User creates a connection
  of type dstore.

* Installation B does not have dstore installed. When user tries to open the
  workspace created by A, an NPE happens in RSEDOMImporter, and the systemView
  does not work at all.

This issue is critical, because RSE is not usable at all.
Expected behavior: missing systemType should be logged when loading the
workspace, connections of unknown systemType should not be shown, but 
apart from that RSE should work as normal.

When adding a new connection in installation B, (so the RSE DOM is saved), original connections of unknown type should not be deleted.

-----------Enter bugs above this line-----------
TM 2.0 I20070816-0800
installation : eclipse-SDK-3.3 (I20070625-1500), cdt-4.0.0, emf-2.3.0
RSE install  : I20070816-0800
java.runtime : Sun 1.5.0_11
os.name:     : Windows XP 5.1, Service Pack 2
------------------------------------------------
systemtype   : Windows-local
------------------------------------------------
Comment 1 Martin Oberhuber CLA 2007-09-07 09:01:25 EDT 
The exception when loading should be fixed by the patch for bug 202416, but I'm not sure what happens when saving the DOM (I think that unknown connections would be deleted).
Comment 2 Martin Oberhuber CLA 2007-09-10 08:48:09 EDT 
Dave I'd think it's safe to close this when you review the patch for bug 202416 and apply it.
Comment 3 David Dykstal CLA 2007-09-10 22:00:09 EDT 
Reviewed the patch for 202416 which contained the fix for this bug. I'm marking this as a duplicate since the fixed was contained there. I'm not sure if that is appropriate.

*** This bug has been marked as a duplicate of bug 202416 ***