Issue 3254: Invalid IDL                                                                                                                                                                                             (rad-ftf)
Source: 2AB (Mr. Bob Burt, bburt@2ab.com)
Nature: Uncategorized Issue
Severity: 
Summary: In multiple places in the IDL (struct AccessDefinition,
AccessDecision::access_allowed) the following is used:
	
	Operation operation;

This is invalid IDL despite the fact that many IDL compilers accept this
today.

Resolution: resolved
Revised Text: In the DfResourceAccessDecision.idl file:
1) Remove the following line in the IDL: typedef string Operation;
2) Replace all instances of "Operation" with "string" in the IDL and
supporting text that references this IDL type. Note that case matters in this
replacement.
Actions taken:
January 26, 2000: received issue
January 9, 2001: closed issue
Discussion: 

End of Annotations:=====
X-Sender: bburt@mindspring.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 26 Jan 2000 14:30:50 -0600
To: <rad-ftf@omg.org>
From: Bob Burt <bburt@2ab.com>
Subject: RAD FTF comments
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-UIDL: N3f!!Q/;e9i6V!!BQ@e9

A couple of minor issues for the RAD FTF:

Issue 2:

In multiple places in the IDL (struct AccessDefinition,
AccessDecision::access_allowed) the following is used:
	
	Operation operation;

This is invalid IDL despite the fact that many IDL compilers accept
this
today.

X-Sender: carolbrt@mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Aug 2000 17:09:54 -0500
To: rad-ftf@omg.org
From: Carol Burt <cburt@2ab.com>
Subject: [RAD-FTF Issue 3254] Proposed resolution
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-UIDL: ;^3e93ZYd9l3!e9;K"!!

Issue 3254 notes illegal IDL as a result of several places where
Operation operation is used.

Proposed Resolution (what I think most implementors have already done)
:


In the DfResourceAccessDecision.idl file:


1) Remove the following line in the IDL:

typedef string Operation;

2) replaced all instances of "Operation" with "string".  Note that
   case matters in this replacement.

_________________________________________________________
Carol Burt                                             2AB, Inc.
cburt@2ab.com                                     www.2ab.com
205-621-7455 ext 103
Member, OMG Architecture Board          OMG Domain Member
_________________________________________________________
             "Solutions for Distributed Business (SM)"


X-Sender: carolbrt@mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Aug 2000 21:45:51 -0500
To: rad-ftf@omg.org
From: Carol Burt <cburt@2ab.com>
Subject: Fwd: RE: [RAD-FTF Issue 3254] Proposed resolution
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-UIDL: 4nKe9jO`d9^?"!!HcGe9


X-MindSpring-Loop: cburt@2ab.com
From: "Chris White" <cwhite@ic.net>
To: "Carol Burt" <cburt@2ab.com>
Subject: RE: [RAD-FTF Issue 3254] Proposed resolution
Date: Wed, 9 Aug 2000 21:11:07 -0400
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal

Sounds good to me!

-----Original Message-----
From: Carol Burt [mailto:cburt@2ab.com]
Sent: Wednesday, August 09, 2000 6:10 PM
To: rad-ftf@omg.org
Subject: [RAD-FTF Issue 3254] Proposed resolution


Issue 3254 notes illegal IDL as a result of several places where
Operation
operation is used.

Proposed Resolution (what I think most implementors have already done)
:


In the DfResourceAccessDecision.idl file:


1) Remove the following line in the IDL:

typedef string Operation;

2) replaced all instances of "Operation" with "string".  Note that
   case
matters in this replacement.

_________________________________________________________
Carol Burt                                             2AB, Inc.
cburt@2ab.com                                     www.2ab.com
205-621-7455 ext 103
Member, OMG Architecture Board          OMG Domain Member
_________________________________________________________
              "Solutions for Distributed Business (SM)"

_________________________________________________________
Carol Burt                                             2AB, Inc.
cburt@2ab.com                                     www.2ab.com
205-621-7455 ext 103
Member, OMG Architecture Board          OMG Domain Member
_________________________________________________________
             "Solutions for Distributed Business (SM)"


X-Sender: u076663@cic-mail.lanl.gov
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 09 Aug 2000 22:38:32 -0600
To: Carol Burt <cburt@2ab.com>, rad-ftf@omg.org
From: David Forslund <dwf@lanl.gov>
Subject: Re: [RAD-FTF Issue 3254] Proposed resolution
In-Reply-To: <4.3.2.7.2.20000809170552.03941008@mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-UIDL: #R-!!^<md9pG^d9856!!

I think this approach is fine.  However, if you wanted to preserve the
use of the term Operation, you could
qualify it everywhere by replacing the occurrences of Operation with
DfResourceAccessDecision::Operation
after the definition of Operation as string.   This solution works for
many of the earlier IDL specifications that
incorrectly depended on case.   The above approach has been tested and
verified to work correctly.

Dave


At 05:09 PM 8/9/00 -0500, Carol Burt wrote:

Issue 3254 notes illegal IDL as a result of several places where
Operation operation is used.

Proposed Resolution (what I think most implementors have already done)
:


In the DfResourceAccessDecision.idl file:


1) Remove the following line in the IDL:

typedef string Operation;

2) replaced all instances of "Operation" with "string".  Note that
   case matters in this replacement.

_________________________________________________________
Carol Burt                                             2AB, Inc.
cburt@2ab.com                                     www.2ab.com
205-621-7455 ext 103
Member, OMG Architecture Board          OMG Domain Member
_________________________________________________________
             "Solutions for Distributed Business (SM)"


X-Sender: u076663@cic-mail.lanl.gov
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 09 Aug 2000 22:38:32 -0600
To: Carol Burt <cburt@2ab.com>, rad-ftf@omg.org
From: David Forslund <dwf@lanl.gov>
Subject: Re: [RAD-FTF Issue 3254] Proposed resolution
In-Reply-To: <4.3.2.7.2.20000809170552.03941008@mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-UIDL: #R-!!^<md9pG^d9856!!

I think this approach is fine.  However, if you wanted to preserve the
use of the term Operation, you could
qualify it everywhere by replacing the occurrences of Operation with
DfResourceAccessDecision::Operation
after the definition of Operation as string.   This solution works for
many of the earlier IDL specifications that
incorrectly depended on case.   The above approach has been tested and
verified to work correctly.

Dave


At 05:09 PM 8/9/00 -0500, Carol Burt wrote:

Issue 3254 notes illegal IDL as a result of several places where
Operation operation is used.

Proposed Resolution (what I think most implementors have already done)
:


In the DfResourceAccessDecision.idl file:


1) Remove the following line in the IDL:

typedef string Operation;

2) replaced all instances of "Operation" with "string".  Note that
   case matters in this replacement.

_________________________________________________________
Carol Burt                                             2AB, Inc.
cburt@2ab.com                                     www.2ab.com
205-621-7455 ext 103
Member, OMG Architecture Board          OMG Domain Member
_________________________________________________________
             "Solutions for Distributed Business (SM)"