Issue 3256: The exception InputFormatError is only raises by one operation                                                                                                                                          (rad-ftf)
Source: 2AB (Mr. Bob Burt, bburt@2ab.com)
Nature: Uncategorized Issue
Severity: 
Summary: The exception InputFormatError is only raises by one operation,
set_evaluators_by_pattern.  I don't understand why this would not raise the
same exceptions as add_evaluators_by_pattern or
delete_evaluators_by_pattern.  They all have the same input parameters.

Resolution: resolved
Revised Text: Remove the InputFormatError exception from the IDL and all explanatory
text.
Change the signature of the set_eveluators_by_pattern to throw the same
exceptions as add_evaluators_by_pattern and
delete_evaluators_by_pattern. See below:
Change idl and associated descriptions to:
void set_evaluators_by_pattern(
in PolicyEvalutatorList policy_evaluator_list,
in ResourceNamePattern pattern
)
raises (InvalidResourceNamePattern,
PatternNotRegistered,
InvalidPolicyEvaluatorList,
DuplicateEvaluatorName);
Actions taken:
January 26, 2000: receive dissue
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 4:

The exception InputFormatError is only raises by one operation,
set_evaluators_by_pattern.  I don't understand why this would not
raise the
same exceptions as add_evaluators_by_pattern or
delete_evaluators_by_pattern.  They all have the same input
parameters.

X-Sender: carolbrt@mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 10 Aug 2000 20:46:54 -0500
To: rad-ftf@omg.org
From: Carol Burt <cburt@2ab.com>
Subject: [RAD-FTF Issue 3256] Proposed solution
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-UIDL: pF?!!@']!!-;c!!2\Me9

Issue 3256 states: The exception InputFormatError is only raised by
one operation, set_evaluators_by_pattern. I don't understand why this
would not raise the same exceptions as add_evaluators_by_pattern or
delete_evaluators_by_pattern. They all have the same input parameters.

Proposed resolution:

Remove the InputFormatError exception from the IDL and all
explainatory text.
Change the signature of the set_eveluators_by_pattern to throw the
same exceptions as add_evaluators_by_pattern and
delete_evaluators_by_pattern which would be:
Change idl and associated descriptions to:

void set_evaluators_by_pattern(
     in PolicyEvalutatorList policy_evaluator_list,
     in ResourceNamePattern pattern
)
raises (InvalidResourceNamePattern,
       PatternNotRegistered,
       InvalidPolicyEvaluatorList,
       DuplicateEvaluatorName);
_________________________________________________________
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)"


From: "Chris White" <cwhite@ic.net>
To: "Carol Burt" <cburt@2ab.com>, <rad-ftf@omg.org>
Subject: RE: [RAD-FTF Issue 3256] Proposed solution
Date: Fri, 11 Aug 2000 12:40:27 -0400
Message-ID: <NCBBKDBPMKKGILBIHIBOOEHICOAA.cwhite@ic.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <4.3.2.7.2.20000810203830.00b3d450@mindspring.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: Z4H!!6pD!!(Z-e91A,e9

OK

-----Original Message-----
From: Carol Burt [mailto:cburt@2ab.com]
Sent: Thursday, August 10, 2000 9:47 PM
To: rad-ftf@omg.org
Subject: [RAD-FTF Issue 3256] Proposed solution


Issue 3256 states: The exception InputFormatError is only raised by
one
operation, set_evaluators_by_pattern. I don't understand why this
would not
raise the same exceptions as add_evaluators_by_pattern or
delete_evaluators_by_pattern. They all have the same input parameters.

Proposed resolution:

Remove the InputFormatError exception from the IDL and all
explainatory
text.
Change the signature of the set_eveluators_by_pattern to throw the
same
exceptions as add_evaluators_by_pattern and
delete_evaluators_by_pattern
which would be:
Change idl and associated descriptions to:

void set_evaluators_by_pattern(
     in PolicyEvalutatorList policy_evaluator_list,
     in ResourceNamePattern pattern
)
raises (InvalidResourceNamePattern,
       PatternNotRegistered,
       InvalidPolicyEvaluatorList,
       DuplicateEvaluatorName);
_________________________________________________________
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)"