Issue 6328: The specification does not specify how a configuration can be modified (sdo-pim-psm-ftf) Source: (, ) Nature: Enhancement Severity: Significant Summary: The specification does not specify how a configuration can be modified. No operation to modify existing configuration sets is defined in the configuration interface. A method should be introduced for this purpose or how it can be done should be clearly defined (eg. Existing set is modified if the configuration is stored in the same name.). Possible options: - Add operation to modify stored configurations - Explain that to modify, the configuration set must first be removed and again be stored with the same name but with new values. - Explain that if confirationset is stored with the name that already exists then that configurationSet is modified. This method has disadvantage since same id can be given without knowledge that it already exists. For this, before storing the configurationSet it may need to check if the given id does not exist, which may be operation overhead. Resolution: Revised Text: Actions taken: October 15, 2003: received issue Discussion: End of Annotations:===== From: webmaster@omg.org Date: 15 Oct 2003 12:34:43 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Raju N. Vaidya Company: Fraunhofer FOKUS mailFrom: vaidya@hotmail.com Notification: Yes Specification: Platform Independent Model (PIM) and Platform Specific Model (PSM) for Super Distributed Objects (SDO) Specification Section: Configuration Interface FormalNumber: dtc/03-09-01 Version: 03-09-01 RevisionDate: 03-09-03 Page: Configuration Interface Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Description The specification does not specify how a configuration can be modified. No operation to modify existing configuration sets is defined in the configuration interface. A method should be introduced for this purpose or how it can be done should be clearly defined (eg. Existing set is modified if the configuration is stored in the same name.). Possible options: - Add operation to modify stored configurations - Explain that to modify, the configuration set must first be removed and again be stored with the same name but with new values. - Explain that if confirationset is stored with the name that already exists then that configurationSet is modified. This method has disadvantage since same id can be given without knowledge that it already exists. For this, before storing the configurationSet it may need to check if the given id does not exist, which may be operation overhead.