bugCERTI - Bugs: bug #26696, User Supplied Tags cannot be NULL

 
 

bug #26696: User Supplied Tags cannot be NULL

Submitted by:  Steffen Strassburger <strassbu>
Submitted on:  Wed 27 May 2009 12:17:25 PM UTC  
 
Category: CERTISeverity: 2 - Minor
Item Group: HLA compliance errorStatus: Confirmed
Privacy: PublicAssigned to: None
Open/Closed: ClosedRelease: 3.3.2
Reproducibility: Every TimeFixed Release: 3.4.0

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 11 Nov 2010 12:12:48 PM UTC, comment #4:

With support the RTI-NG legacy "NULL" tag
for UAV/RAV SI/RI in the 1.3 API.

The solution is not to transmit the NULL tag at all.

1516 still throw exceptions.

Eric NOULARD <erk>
Project Administrator
Thu 28 May 2009 08:33:57 PM UTC, comment #3:

Ok fine I understand,
and you are right about reporting even if you cannot
fix we will track the issue down when the time comes.

However if ever you get a chance/time
to dive into CERTI, dot not be afraid
we usually provided the rubber ring
for newcomers :-)

Eric NOULARD <erk>
Project Administrator
Thu 28 May 2009 02:18:19 PM UTC, comment #2:

I'd like 2) better, too, but I don't feel confident about providing a patch myself (plus I simply don't have the time to dive into the CERTI code).

As this is a minor issue (and I already implemented a simple workaround in my code) I would "abstain" in this case.

Just wanted to let you know that this issue existed in the first place.

Steffen Strassburger <strassbu>
Wed 27 May 2009 04:53:20 PM UTC, comment #1:

You are right this is not really an error
but it would be a good thing to help with
RTI-NG transition.

Regarding the HLA 1.3 document the one I have
does not state that char* theTag is optional
thus we decided it should be given and not NULL.
Just a possible interpretation though.

The only trouble with accepting
NULL as a string is the way you'll have to handle it
because NULL should be transmitted through the network.

1) The easy way:

We automagically replace NULL with 0-length string=""
in either sendInteraction or UAV (inside libRTI).
Thus we may transmit 0-length string through the network.
Then in ReflectAttributeValue we will have to translate
"" back to NULL.

In this user may not distinguish UAV(....,"") from
UAV(....,NULL)

2) The not so difficult way.

Handle the NULL case properly and add a boolean or
something to UAV/RAV/Interaction message in order
tell whether if there was [non NULL] tag provided.

I'd like the 2) better but 1) is definitely acceptable
Would you like to try to provide a patch for 1) or 2)?

Eric NOULARD <erk>
Project Administrator
Wed 27 May 2009 12:17:25 PM UTC, original submission:

Gentlemen,

not sure if you will accept this as a HLA compliancy error, however, it is at least a compatibility issue when switching from DMSO RTI 1.3NG to CERTI.

Here is what this is about:

In several RTI ambassador calls you can pass a UserSuppliedTag to the call (i.e. sendInteraction, updateAttributeValues, ...). As this is hardly used, it was possible in the DMSO RTI to simply pass a NULL pointer when you did not want to use this parameter. If you do that with CERTI, it throws an exception complaining "Calling sendInteraction with Tag NULL", in case of an rtiSendInteraction call.

Would you be able and willing to fix this issue? It would probably help a lot of people to switch from DMSO RTI to CERTI.

The HLA 1.3 Spec is somewhat ambiguous in this regard, it simply mandates a "const char* theTag" but does not explicitly prohibit it from being NULL.

Best regards,
Steffen

Steffen Strassburger <strassbu>

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by breholee
  • -unavailable- added by erk (Posted a comment)
  • -unavailable- added by strassbu (Submitted the item)
  •  

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 11 Nov 2010 12:12:48 PM UTCerkOpen/ClosedOpen=>Closed
      Fixed ReleaseUnknown=>3.4.0
    Fri 04 Sep 2009 11:04:16 AM UTCbreholeeCarbon-Copy-=>Added breholee
    Thu 28 May 2009 08:33:57 PM UTCerkStatusNone=>Confirmed

    Back to the top


    Powered by Savane 3.1-cleanup1