View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000696310000-004: ServicesSpecpublic2021-05-26 15:272023-03-21 20:11
ReporterKevin Herron (Inductive Automation) Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Fixed in Version1.05.03 RC1 
Summary0006963: Correct usage of ServiceFault is under-documented
Description

Part 4 says:

The ServiceFault parameter is returned instead of the Service response message when a service level error occurs.

But does not go into any further detail. I have interpreted (and implemented) this as meaning any time a service level StatusCode is Bad quality a ServiceFault is returned instead.

It seems not all implementations take the same approach, in particular when dealing with PublishResponses containing "expected" service level errors such as Bad_NoSubscription or Bad_SessionClosed.

Should a PublishResponse containing Bad_NoSubscription be returned as a PublishResponse or a ServiceFault? The spec should be more clear about this.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2021-09-14 16:26

administrator   ~0014854

Clarify that "service level error" means StatusCode is "Bad".

Matthias Damm

2023-03-20 23:17

developer   ~0018919

5.3 Service results
7.35 ServiceFault

Both places talk about service level error and I clarified in both places

  • ServiceFault shall be returned instead of the Service response message
  • when serviceResult is a StatusCode with Severity Bad

Jim Luth

2023-03-21 20:11

administrator   ~0018947

Agreed to changes in Dallas meeting.

Issue History

Date Modified Username Field Change
2021-05-26 15:27 Kevin Herron (Inductive Automation) New Issue
2021-09-14 16:26 Jim Luth Note Added: 0014854
2021-09-14 16:26 Jim Luth Assigned To => Matthias Damm
2021-09-14 16:26 Jim Luth Status new => assigned
2023-03-20 23:17 Matthias Damm Status assigned => resolved
2023-03-20 23:17 Matthias Damm Resolution open => fixed
2023-03-20 23:17 Matthias Damm Note Added: 0018919
2023-03-21 20:11 Jim Luth Status resolved => closed
2023-03-21 20:11 Jim Luth Fixed in Version => 1.05.03 RC1
2023-03-21 20:11 Jim Luth Note Added: 0018947