ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002565Part 06: TTCN-3 Control InterfaceNew Featurepublic05-12-2007 15:1112-12-2008 15:40
ReporterIna Schieferdecker 
Assigned ToIna Schieferdecker 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Versionv4.1.1 (published 2009-06)Fixed in Versionv4.1.1 (published 2009-06) 
Clause Reference(s)Part 1, Clause 24.1
Source (company - Author)     
Summary0002565: TTCN-3 Exceptions
DescriptionThe error handling in TTCN-3 is very weak - only an error verdict can be assigned. A more fine-grained solution as e.g. used in other technologies (for example CORBA system exceptions) could be used instead.

This CR proposes to have predefined TTCN-3 system exceptions which may be raised by the runtime system, logged in the verdict (for example as a parameter to the error verdict) and in the logging file.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0003843closed Thomas Deiß Part 01: TTCN-3 Core Language Support C++ like Exception Handling mechanism 
Attached Filesdoc CR_2565_resolution_01.doc (168,960) 13-10-2008 15:12
http://oldforge.etsi.org/mantis/file_download.php?file_id=1682&type=bug
Issue History
Date ModifiedUsernameFieldChange
05-12-2007 15:11Ina SchieferdeckerNew Issue
05-12-2007 15:11Ina SchieferdeckerStatusnew => assigned
05-12-2007 15:11Ina SchieferdeckerAssigned To => Thomas Deiß
05-12-2007 15:11Ina SchieferdeckerClause Reference(s) => Part 1, Clause 24.1
05-12-2007 15:11Ina SchieferdeckerSource (company - Author) =>
05-12-2007 15:12Ina SchieferdeckerTarget Version => Edition 4.1.1 (not yet published)
23-04-2008 18:13Thomas DeißNote Added: 0005536
11-08-2008 10:35Thomas DeißRelationship addedrelated to 0003843
13-10-2008 15:12Thomas DeißFile Added: CR_2565_resolution_01.doc
13-10-2008 15:17Thomas DeißNote Added: 0007044
13-10-2008 15:17Thomas DeißAssigned ToThomas Deiß => Ina Schieferdecker
14-10-2008 09:49Ina SchieferdeckerStatusassigned => resolved
14-10-2008 09:49Ina SchieferdeckerResolutionopen => fixed
14-10-2008 09:55Ina SchieferdeckerNote Added: 0007051
14-10-2008 09:56Ina SchieferdeckerNote Deleted: 0007051
14-10-2008 09:56Ina SchieferdeckerNote Added: 0007052
10-12-2008 08:59Ina SchieferdeckerProjectPart 01: TTCN-3 Core Language => Part 06: TTCN-3 Control Interface
12-12-2008 15:40Ina SchieferdeckerStatusresolved => closed
12-12-2008 15:40Ina SchieferdeckerFixed in Version => Edition 4.1.1 (not yet published)

Notes
(0005536)
Thomas Deiß   
23-04-2008 18:13   
1) The TCI-CH has to be extended by tciError and tciErrorReq such that errors can be propagated to the TM in a distributed test system.
2) tliSetverdict should be extended such that it can be called also when there is a dynamic error. tliInfo is not a suitable log event in this case.

3) Erroneous situations shall not be _handled_ within the test system, but a user should be informed in a consistent manner.
(0007044)
Thomas Deiß   
13-10-2008 15:17   
Resolution:
tliSetverdict may be called to report runtime error.

corrections in constraints of TCI-CH operations because the start test component operation may call a function with out and inout parameters. Allow to use PTC_ALIVE as type in create test component.

No change to parameter lists of operations, therefore no change to language mappings.
(0007052)
Ina Schieferdecker   
14-10-2008 09:56   
Had to correct also the tliSetVerdict operation in the C++ mapping:

from

"virtual void tliSetVerdict (const Tstring &am, const timeval ts, const Tstring &src, const Tinteger line, const TriComponentId *c, const VerdictValue *verdict)=0"

to

"virtual void tliSetVerdict (const Tstring &am, const timeval ts, const Tstring &src, const Tinteger line, const TriComponentId *c, const VerdictValue *verdict, const TString &reason)=0"

The reason parameter was missing.