Issue 5688: Derived component supported interface restriction  (formal/2002-06-65) (components-ftf)
Source: Computational Physics, Inc. (Mr. J. Scott Evans, evans(at)cpi.com)
Nature: Uncategorized Issue
Severity: 
Summary: Both the CORBA spec (formal/02-06-01 page 3-61) and the CCM spec (formal/02-06-65 page 1-51) state that "A derived component type may not directly support an interface." Moreover the sentence you depicted is a contradiction with the formal/02-06-65 section 1.3.2.4 page 1-7.


Resolution:


In formal/02-06-65 page 1-51 and formal/02-06-01 page 3-61 replace the sentence


"A derived component type may not directly support an interface."


with


"If a derived component type directly supports one or more IDL interfaces, the component interface is derived from both  the interface of its base component type and the supported interfaces."
Resolution: 
Revised Text: 
Actions taken:
October 10, 2002: received issue
Discussion: 

End of Annotations:=====
X-Sender: evans@mail.cpi.com 
X-Mailer: QUALCOMM Windows Eudora Version 5.1 
Date: Thu, 10 Oct 2002 12:37:37 -0400 
To: issues@omg.org 
From: "J. Scott Evans" <evans@cpi.com> 
Subject: Derived component supported interface restriction 



Issue:


Both the CORBA spec (formal/02-06-01 page 3-61) and the CCM spec
(formal/02-06-65 page 1-51) state that "A derived component type may
not directly support an interface." Moreover the sentence you depicted
is a contradiction with the formal/02-06-65 section 1.3.2.4 page 1-7.


Resolution:


In formal/02-06-65 page 1-51 and formal/02-06-01 page 3-61 replace the
sentence


"A derived component type may not directly support an interface."


with


"If a derived component type directly supports one or more IDL
interfaces, the component interface is derived from both  the
interface of its base component type and the supported interfaces."





Date: Wed, 16 Oct 2002 11:57:03 -0400 
From: Jishnu Mukerji <jishnu@hp.com> 
Organization: Software Global Business Unit, Hewlett-Packard 
X-Mailer: Mozilla 4.79 [en] (Win98; U) 
X-Accept-Language: en 
To: Juergen Boldt <juergen@omg.org> 
Cc: issues@omg.org, components-rtf@omg.org, corba-rtf@omg.org 
Subject: Re: issue 5683 -- Components RTF issue 




Juergen Boldt wrote:
> 
> This is issue # 5683    "J. Scott Evans" <evans@cpi.com>
> 
> Derived component supported interface restriction
> 
> Both the CORBA spec (formal/02-06-01 page 3-61) and the CCM spec
> (formal/02-06-65 page 1-51) state that "A derived component type may
not
> directly support an interface." Moreover the sentence you depicted
is a
> contradiction with the formal/02-06-65 section 1.3.2.4 page 1-7.
> Resolution:
> 
> In formal/02-06-65 page 1-51 and formal/02-06-01 page 3-61 replace
the sentence
> 
> "A derived component type may not directly support an interface."
> 
> with
> 
> "If a derived component type directly supports one or more IDL
interfaces,
> the component interface is derived from both  the interface of its
base
> component type and the supported interfaces."
> 
> =================================



I'd actually recommend that the resolution for formal/02-06-01 be to
simply remove the inaccurate sentence from page 3-61.


It would be inappropriate to include material on how the derived IDL
looks in this particular case since in general that is not presented
in
Core Chapter 3. It would be appropriate to substitute the proposed
text
in formal/02-06-65 as suggested.


Juergen, just to make the logisitics of this easier...... could you
please split this issue into two:


1) Dealing with the problem in document formal/02-06-01, and assign it
to the Core RTF,


2) Dealing with the problem in document formal/02-06-65, and assign it
to the Components RTF, and close this combined issue.


Unbless we do this, we will eventually lose track of the issue in
either
the Core RTF or the Component RTF.


Thanks,


Jishnu