View Issue Details

IDProjectCategoryView StatusLast Update
0009337Part 81: UAFX Connecting Devices and Information ModelSpecpublic2024-01-12 14:18
ReporterJan Murzyn Assigned ToGeorg Biehler  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.00.02 
Fixed in Version1.00.02 
Summary0009337: Clarify the expected content of the EstablishConnections outputs in case of aborting a multi-step process with roll-back.
Description

Example scenario:
EstablishConnections was called with CreateConnectionEndpoint and SetCommunicationConfiguration commands. The method got aborted due to failure of SetCommunicationConfiguration. Endpoint created earlier by CreateConnectionEndpoint got cleaned up (rolled back) as specified. What is the expected content of the ConnectionEndpointId field in ConnectionEndpointConfigurationResults?

Do we want to specify that it shall be set to a specific (“zero”) value after the endpoint got rolled back, or do we want to remain silent, which means the implementation can leave anything there?

Another place to where clarification would be needed is the content of PubSubCommunicationConfigurationResultDataType in case of rolled back communication configuration.

TagsNo tags attached.

Activities

Georg Biehler

2024-01-12 08:44

developer   ~0020615

Last edited: 2024-01-12 08:56

Since the NodeId is no longer valid (if the CEP got deleted (if not preconfigured)) I would expect that the NodeId is set to zero.
For PubSubCommunicationConfigurationResults, I would expect that all ChangesApplied is set to FALSE, and ConfigurationObjects set to null or empty

Do we need an addtional ErrorCode stating "Aborted"? An earlier command could have been good, but was aborted - how to indicate?

Georg Biehler

2024-01-12 08:58

developer   ~0020616

Fixed text

DISCUSS: Do we need an addtional ErrorCode stating "Aborted"? An earlier command could have been good, but was aborted - how to indicate?

Paul Hunkar

2024-01-12 14:18

manager   ~0020618

reviewed changes in call, agreed to changes and closed issue

Issue History

Date Modified Username Field Change
2024-01-05 22:27 Jan Murzyn New Issue
2024-01-12 08:44 Georg Biehler Assigned To => Georg Biehler
2024-01-12 08:44 Georg Biehler Status new => assigned
2024-01-12 08:44 Georg Biehler Note Added: 0020615
2024-01-12 08:51 Georg Biehler Note Edited: 0020615
2024-01-12 08:56 Georg Biehler Note Edited: 0020615
2024-01-12 08:58 Georg Biehler Status assigned => resolved
2024-01-12 08:58 Georg Biehler Resolution open => fixed
2024-01-12 08:58 Georg Biehler Fixed in Version => 1.00.03
2024-01-12 08:58 Georg Biehler Note Added: 0020616
2024-01-12 14:18 Paul Hunkar Status resolved => closed
2024-01-12 14:18 Paul Hunkar Fixed in Version 1.00.03 => 1.00.02
2024-01-12 14:18 Paul Hunkar Note Added: 0020618