View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000272010000-004: ServicesSpecpublic2014-02-06 13:592014-11-18 18:55
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0002720: Relation between Call::Response::results - statusCode and inputArgumentResults
Description

I have the following issues with the description of Call::Response::results::statusCode:

a) Relation between statusCode and inputArgumentResults parameter

Case 1: One of the input arguments is wrong is clearly covered by the following description:
'This StatusCode is set to the Bad_InvalidArgument StatusCode if at least one input argument broke a constraint (e.g. wrong data type, value out of range).'

Case 2: All inputs are ok and statusCode is Good
I assume the inputArgumentResults has the same size like the inputArguments array and contains only Good results.

Case 3: The number or arguments is wrong.
Status Bad_ArgumentsMissing states: The client did not specify all of the input arguments for the method.
Does this also apply if too many arguments are passed in?
What happens with the inputArgumentResults in this case?

b) Bad_InvalidArgument is listed in the statusCode parameter description but not in the list of operation results

c) HRESULT should not be referred in the description 'e.g. based on an exception or an HRESULT'

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0002796 closedMatthias Damm NodeSets, XSDs and Generated Code Relation between Call::Response::results - statusCode and inputArgumentResults 

Activities

Jim Luth

2014-03-04 17:46

administrator   ~0005296

Add Bad_TooManyArguments as an overall status return and specify when it is used.

Clarify that only if Bad_InvalidArgument is returned the inputArgumentResults is populated.

Bad_InvalidArgument needs to be listed in the list of operation results

HRESULT should not be referred in the description 'e.g. based on an exception or an HRESULT'

THIS Requires and Errata.

These changes should go in the current IEC CDV.

Matthias Damm

2014-06-04 14:07

developer   ~0005346

Change applied in 65E-62541-4-Ed2-IS-CDV-FE-to-kog - Editor Updates.doc

Added the following sentence to Table 61:
This list is only filled with input argument specific status codes if the operation level result is Bad_InvalidArgument.

Added new status code to Table 63:
Bad_TooManyArguments - The client did specify more input arguments than defined for the method.
Added status code to Table 63:
Bad_InvalidArgument - See Table 165 for the description of this result code.
Used to indicate in the operation level results that one ore more of the input arguments are invalid. The inputArgumentResults contain more specific status codes in this case.

We need an errata for this fix.

Jim Luth

2014-06-10 16:52

administrator   ~0005356

Agreed to text changes. Needs errata and clone to fix stacks.

Jim Luth

2014-11-18 17:12

administrator   ~0005627

Agreed to the errata text.

Issue History

Date Modified Username Field Change
2014-02-06 13:59 Matthias Damm New Issue
2014-03-04 17:46 Jim Luth Note Added: 0005296
2014-03-04 17:46 Jim Luth Status new => assigned
2014-03-04 17:46 Jim Luth Assigned To => Matthias Damm
2014-06-04 14:07 Matthias Damm Status assigned => resolved
2014-06-04 14:07 Matthias Damm Resolution open => fixed
2014-06-04 14:07 Matthias Damm Note Added: 0005346
2014-06-10 16:52 Jim Luth Note Added: 0005356
2014-06-10 16:54 Jim Luth Issue cloned: 0002796
2014-06-10 16:54 Jim Luth Relationship added related to 0002796
2014-11-18 17:10 Jim Luth Category (No Category) => Spec
2014-11-18 17:12 Jim Luth Note Added: 0005627
2014-11-18 17:12 Jim Luth Status resolved => closed
2014-11-18 17:12 Jim Luth Fixed in Version => 1.03
2014-11-18 18:55 Jim Luth Target Version => 1.03