Bug 185752 - [api]RSE DOM and Persistence should use systemType ID instead of Name
Summary: [api]RSE DOM and Persistence should use systemType ID instead of Name
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P2 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: David Dykstal CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 184095
  Show dependency tree
 
Reported: 2007-05-07 09:20 EDT by Martin Oberhuber CLA
Modified: 2008-08-13 13:18 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-05-07 09:20:56 EDT
As per bug 184095, the systemType name should be replaced by a systemType ID or label everywhere in order to
 - allow multiple extenders register system types without namespace clash by
   using reverse dns notation, like com.foobar.systemtype.linux
 - allow translating system type names into foreign languages

The RSE DOM and Persistence framework currently still uses the systemType name. This should be changed to using the systemType ID instead:
 * DOM usage can be found by searching for usage of IRSESystemType.getName(),
   or by searching for usage of IRSEDOMConstants.ATTRIBUTE_TYPE
 * The persistence DOM Writer should write out both the system type name AND the
   id in order to be backward compatible
 * The persistence DOM Reader should try reading the system type ID and use it
   if available; or fall back to the system type name only if it is not
   available.
Comment 1 David Dykstal CLA 2007-05-07 09:46:42 EDT
I agree. I should be able to map from the old system name to the new one so that older profiles can still be used, but all ones that are written should use the ID.

I will get to this today.
Comment 2 David Dykstal CLA 2007-05-07 13:05:16 EDT
Fixed as specified in the description.
Comment 3 Martin Oberhuber CLA 2008-08-13 13:18:27 EDT
[target cleanup] 2.0 M7 was the original target milestone for this bug