Bug 193323 - Connection "Local" always created on startup even if another local connection exists
Summary: Connection "Local" always created on startup even if another local connection...
Status: CLOSED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P5 trivial (vote)
Target Milestone: 2.0.1   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on: 196838
Blocks:
  Show dependency tree
 
Reported: 2007-06-19 10:37 EDT by Kevin Doyle CLA
Modified: 2007-07-19 17:27 EDT (History)
2 users (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 Kevin Doyle CLA 2007-06-19 10:37:01 EDT 
If you rename your local connection and close and reopen the workbench, a new "Local" connection is created.  It appears as if a local connection named Local is always created.  When it should just be checking if a local connection exists, not for one specifically called "Local".

-----------Enter bugs above this line-----------
TM 2.0RC3 Testing
installation : eclipse-SDK-3.3RC4
RSE install  : RSE 2.0 RC3
java.runtime : Sun 1.5.0_11-b03
os.name:     : Windows XP, Service Pack 2
------------------------------------------------
Comment 1 Martin Oberhuber CLA 2007-06-28 09:13:16 EDT 
This should be simple to fix (I think there is SystemRegistry.getLocalConnection() or something like that which would need to be updated), but I'm not sure if we really want to fix it since it appears to be really low in priority.

I dont think that any extenders can expect the connection named "Local" to always be there, so either case I don't see this as a big issue.
Comment 2 Martin Oberhuber CLA 2007-07-19 12:55:31 EDT 
Fixed through the fix for bug #196838
Comment 3 Kevin Doyle CLA 2007-07-19 17:27:55 EDT 
Verified with driver I20070719-1300.