taskCERTI - Tasks: task #9306, Change Order Type


You are not allowed to post comments on this tracker with your current authentication level.

task #9306: Change Order Type

Submitter:  Pierre Siron <siron>
Submitted:  Tue 07 Apr 2009 11:29:19 AM UTC
Should Start On:  Tue 07 Apr 2009 12:00:00 AM UTC Should be Finished on:  Sun 07 Jun 2009 12:00:00 AM UTC
Category:  None Priority:  3 - Low
Status:  None Privacy:  Public
Assigned to:  siron Percent Complete:  0%
Open/Closed:  Open Planned Release:  None
RTI Service Groups:  None

Wed 08 Apr 2009 11:07:43 AM UTC, comment #1: 

The definition of the RECEIVE and TIMESTAMP
symbolic value in certi.hh is not so strange
it is used in several places in the code:


and in the parser/lexer for Fed File.

However the USER should NEVER use those definition
(in fact the symbolic definition should be made private
 to libCERTI I think).

The user should use the RTIambassador API

OrderingHandle getOrderingHandle(const char *)

in order to retrieve a proper value for

This value may then be used in

The definition of order type name is located in

this is currently a "static" list
const ObjectManagement::OrderTypeList
ObjectManagement::orderTypeList[] = {
    { "Receive", RECEIVE },
    { "Timestamp", TIMESTAMP },
    { NULL }

but we may change this if needed.

Eric NOULARD <erk>
Group administrator
Tue 07 Apr 2009 11:29:19 AM UTC, original submission:  

Implementation of 2 services (time management) :

The value can be RECEIVE (1) or TIMESTAMP (2).
These constants are defined in certi.hh.
This is strange because the user has to put a value
for the service call.

These services could be useful to do automated tests.
Otherwise the default value is in the fed file.

Pierre Siron <siron>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by erk (Posted a comment)
  • -email is unavailable- added by siron (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.12.
    Corresponding source code