ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007611 | Part 01: TTCN-3 Core Language | Clarification | public | 13-02-2017 11:27 | 23-08-2019 09:39

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.9.1 (published 2017-05) |
Target Version | v4.10.1 (published 2018-05) | Fixed in Version | v4.10.1 (published 2018-05) |
Clause Reference(s) | 6.2.9, 22.3
Source (company - Author) | STF 521

Summary | 0007611: Valid port lists for the procedure operations

Description

The clause 6.2.9 and related sections of 22.3 don't provide sufficient rules on how signatures listed in the in-list and out-list of port definitions restrict which signatures can be used in procedure-based communication. The used logic is not straightforward, as the in/out directions are assessed from the caller's point of view. Let's demonstrate it on an example with the following definitions:
type signature S() exception (charstring);
port PClient procedure { out S; }
port PServer procedure { in S; }
With these definitions, the following operations using the signature S shall be possible for a port of the PClient type:
- call
- getreply
- catch
And the following operations using the signature S shall be possible for a port of the PServer type:
- getcall
- reply
- raise
There are some hints on how this should work in the core language specification, especially in the way how system adapter works (in 6.2.9, but getcall, reply, raise are not explicitly mentioned) and in the description of the call (22.3.1 restriction a), getcall (22.3.2 restriction b) and raise (22.3.5 restriction b). However, the reply, getreply and catch operations do not contain any relevant restriction and there's no general explanation of the whole logic in 6.2.9.
Proposal:
1. In 6.2.9, explicitly list procedure-based communication operations associated with the in-list and out-list.
2. Extend the list of in and out directions of the system adapter by adding the missing operations.
3. Add the missing restrictions to the reply, getreply and catch operation clauses

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

related to | 0007860 | closed | Gyorgy Rethy | CR 7611 wasn't properly added to the specification

Attached Files

7611.doc (171,008) 09-06-2017 08:34
http://oldforge.etsi.org/mantis/file_download.php?file_id=3623&type=bug
7611-v2.doc (159,232) 09-06-2017 09:23
http://oldforge.etsi.org/mantis/file_download.php?file_id=3625&type=bug
7611-v3.doc (175,616) 09-06-2017 09:49
http://oldforge.etsi.org/mantis/file_download.php?file_id=3630&type=bug
7611-v4.doc (146,944) 09-06-2017 10:17
http://oldforge.etsi.org/mantis/file_download.php?file_id=3632&type=bug

Issue History
Date Modified | Username | Field | Change
13-02-2017 11:27 | Tomas Urban | New Issue |
15-02-2017 11:33 | Jacob Wieland - Spirent | Note Added: 0014528 |
15-02-2017 12:15 | Tomas Urban | Note Added: 0014529 |
06-06-2017 14:56 | Jens Grabowski | Assigned To | => Julien Deltour
06-06-2017 14:56 | Jens Grabowski | Status | new => assigned
09-06-2017 08:34 | Julien Deltour | File Added: 7611.doc |
09-06-2017 08:35 | Julien Deltour | Note Added: 0014676 |
09-06-2017 08:36 | Julien Deltour | Status | assigned => confirmed
09-06-2017 08:36 | Julien Deltour | Assigned To | Julien Deltour => Tomas Urban
09-06-2017 08:36 | Julien Deltour | Status | confirmed => assigned
09-06-2017 09:23 | Tomas Urban | File Added: 7611-v2.doc |
09-06-2017 09:24 | Tomas Urban | Note Added: 0014685 |
09-06-2017 09:24 | Tomas Urban | Assigned To | Tomas Urban => Julien Deltour
09-06-2017 09:24 | Tomas Urban | Status | assigned => confirmed
09-06-2017 09:48 | Julien Deltour | File Added: 7611-v3.doc |
09-06-2017 09:48 | Julien Deltour | File Deleted: 7611-v3.doc |
09-06-2017 09:49 | Julien Deltour | File Added: 7611-v3.doc |
09-06-2017 09:50 | Julien Deltour | Note Added: 0014690 |
09-06-2017 09:53 | Julien Deltour | Assigned To | Julien Deltour => Tomas Urban
09-06-2017 10:17 | Tomas Urban | File Added: 7611-v4.doc |
09-06-2017 10:18 | Tomas Urban | Note Added: 0014693 |
09-06-2017 10:18 | Tomas Urban | Status | confirmed => resolved
09-06-2017 10:18 | Tomas Urban | Resolution | open => fixed
09-06-2017 10:18 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
30-12-2017 20:15 | Gyorgy Rethy | Note Added: 0014971 |
30-12-2017 20:15 | Gyorgy Rethy | Status | resolved => closed
30-12-2017 20:15 | Gyorgy Rethy | Product Version | => v4.9.1 (published 2017-05)
30-12-2017 20:15 | Gyorgy Rethy | Fixed in Version | => v4.10.1 (published 2018-05)
30-12-2017 20:15 | Gyorgy Rethy | Target Version | => v4.10.1 (published 2018-05)
23-08-2019 09:39 | Tomas Urban | Relationship added | related to 0007860

Notes

(0014528)
Jacob Wieland - Spirent
15-02-2017 11:33

I am confused by this part of the proposal: " Extend the list of in and out directions of the system adapter by adding the missing operations." I have no idea what you mean specifically by that statement.

(0014529)
Tomas Urban
15-02-2017 12:15

Detailed explanation:
The original sentence "...with the exception of the test system interface, where in identifies the direction of message sending or procedure call and out identifies the direction of message receive, get reply or catch exception from the point of view of the test component connected to the test system interface port."
The proposed sentence: "...with the exception of the test system interface, where the communication operations are seen from the point of view of the test component port mapped to the test system interface port. The in-list of the test system interface port contains messages or signatures for which the mapped component port allows the following operations: receive, trigger, getcall, reply or raise. The out-list of the test system interface port contains messages or signatures for which the mapped component port allows the following operations: send, call, getreply or catch."

(0014676)
Julien Deltour
09-06-2017 08:35

Please review the proposal

(0014685)
Tomas Urban
09-06-2017 09:24

I made several minor changes in the document. Please review and if you are fine with the resolution, you can mark the CR as resolved and assign it to Gyorgy for implementation.

(0014690)
Julien Deltour
09-06-2017 09:50

for consistency in restrictions rules, I have made two more changes. Please review

(0014693)
Tomas Urban
09-06-2017 10:18

The last revision contains only cosmetic changes and the resolution is ready to be added to the next version of the core language specification.

(0014971)
Gyorgy Rethy
30-12-2017 20:15

Implemented in draft V4.9.2