Source: Diebold Nixdorf Global Solutions B.V. ( Denis Kuniss)
In general, this seems to be a design issue as readData() method was design to be synchronous only, but additionally it causes input data and input error events what definitely is intended only for devices which follow the asynchronous data input model. Because readData() is a synchronous method only, it normally cannot cover asynchronous input!
As we cannot change the UPOS method syntax anymore (for removing the output parameters and moving them to properties as it would be required by the asynchronous input model) and also not the synchronous flavor, it is recommended to just correct the status diagram by removing the edges "DataEvent()" and "ErrorEvent()" and maybe add a note to readData() how this could be implemented.
Initially reported by https://github.com/mjpcger.
BTW, the UML diagrams are very hard to read due to a very poor density/quality!
Reported: UPOS 1.15 — Mon, 25 Apr 2022 13:41 GMT
Updated: Mon, 25 Apr 2022 14:16 GMT
- UPOS 1.15 SmartCardRW issue readData.jpg 118 kB (image/jpeg)
UPOS1151 — SmartCardRW: UML status diagram causes confusion for readData()
- Key: UPOS1151-11
- OMG Task Force: UnifiedPOS 1.15.1 RTF