Issue 5335: OMG Document formal/98-10-35 (CosRelationships::RelationshipFactory::create (relationship-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: The declaration of CosRelationships::RelationshipFactory::create does not mention the DuplicateRoleName exception in its raises clause. The specification (formal/00-06-24) states that Role names must be unique within each relationship type. Is this an error in the IDL? Resolution: Revised Text: Actions taken: June 6, 2002: received issue Discussion: End of Annotations:===== Date: Fri, 29 Oct 1999 04:09:39 -0400 (EDT) Message-Id: <199910290809.EAA11376@emerald.omg.org> From: x_ramak@ugsolutions.com To: juergen@omg.org, web-incoming@omg.org Subject: Issue Report Content-Type: text X-UIDL: /YY!!Z-_!!T7C!!5Pjd9 Name: Ramakrishna. K Company: Tata Consultancy Services mailFrom: x_ramak@ugsolutions.com Notification: Yes Specification: CORBA Services/ CosRelationships Section: 9/Relationship Service specification Formal #: 97-12-16.pdf Version: v 1.0 Revision_Date: 12/16/97 Page: 9-41 Nature: Clarification Severity: Significant full_desc: CosGraphs::Node interface provides a function add_role() which helps in adding a new role to the related object the Node is representing. The specifications suggests to raise an exception DuplicateRoleType if the new role is same, subtype, supertype of one of the role of the Node object. What if the user of function calls add_role() with a role for an object which is not represented by this node. Definitely we cannot add the new role to the Node. Only thing we can do here is return out of function. But user will not be aware that the function has failed, since the return type is void. suggestion: The functionality can be improved by making the return type of add_role() as boolean. But again user will not be able to find the reason for failure. This condition can be better handled by raising an exception. submit: Submit Issue Report Date: Wed, 21 Mar 2001 10:57:02 +1000 (EST) From: Michi Henning To: Juergen Boldt cc: issues@emerald.omg.org Subject: Re: Lost issues In-Reply-To: <4.2.0.58.20010320104951.00a86ca0@emerald.omg.org> Message-ID: Organization: Object Oriented Concepts - An IONA Company MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: :BJe9a1K!!,[8e9=SL!! On Tue, 20 Mar 2001, Juergen Boldt wrote: > Hello all, > > URL http://cgi.omg.org/issues/issues.html > contains links to issues which have not been assigned to R/FTFs > because of > a couple of reasons: > ..to name a few... > a) The RTF/FTF has expired and should be re-chartered > b) The RTF/FTF has expired and will never be re-chartered again > (several > reasons why are possible) > c) I just didn't know what RTF/FTF would be responsible for an issue > submitted.. > d) There appear to be no RTFs for most of the CORBAservices > e) Nobody knew about this issues archive > > With your help some of those issues could be resolved (by assigning > some of > those issues to active RTFs/FTFs or by rechartering some of the > expired > RTFs...) Here are some proposals: Issue 184: Close no change. I don't understand the question Issue 468: Close. The issue is empty. Issue 493: Close no change. It doesn't because the submitters decided that it wouldn't. Issue 498: From what I can recall, this refers to name equivalence in the Naming Service. INS has cleaned this, so close it. Issue 961: Move to http://cgi.omg.org/issues/event-rtf.html Issue 2347: Close. This was fixed by INS. Issue 2972: Move to http::/cgi.omg.org/issues/relationship-rtf.html Issue 3003: Close. Issue 3271: Close no change. Historically, iterators in the various specs are a total mess, and all of them, without exception, get it wrong :-( I'm afraid we have to live with the resulting inconsistencies. Issue 4216: Should probably be reassigned to Core RTF? Issues 284, 546, 547, 548, 549, 550, 558, 559, 560, 561, 562, 4225: We need a trader RTF for those. The remaining open issues also will require formation of RTFs. Cheers, Michi. -- Michi Henning +61 7 3324 9633 Object Oriented Concepts - An IONA Company +61 4 1118 2700 (mobile) Suite 4, 8 Martha St +61 7 3324 9799 (fax) Camp Hill 4152 michi.henning@iona.com Brisbane, AUSTRALIA http://www.ooc.com.au/staff/michi