bugCERTI - Bugs: bug #21610, Timestamp should be allowed as...

 
 

bug #21610: Timestamp should be allowed as attribute/parameter name

Submitter:  Chris Rule <crule>
Submitted:  Mon 19 Nov 2007 03:33:08 PM UTC
   
 
Category:  CERTI Severity:  * 4 - Important
Item Group:  HLA compliance error Status:  Ready For Test
Privacy:  Public Assigned to:  erk
Open/Closed:  Closed Release:  * CVS
Reproducibility:  Every Time Fixed Release:  * 3.3.2
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 21 Oct 2008 10:56:19 AM UTC, comment #5: 

The trouble reported by Michael should be fixed in the
current CVS version.

Eric NOULARD <erk>
Group administrator
Tue 06 May 2008 08:17:59 AM UTC, comment #4: 

Michael reported a problem
with attribute named timestamp
see:
http://lists.nongnu.org/archive/html/certi-devel/2008-04/msg00023.html

and attached FED file

(file #15614)

Eric NOULARD <erk>
Group administrator
Wed 23 Apr 2008 02:50:22 PM UTC, comment #3: 

Needs more testing

Eric NOULARD <erk>
Group administrator
Fri 25 Jan 2008 03:01:59 PM UTC, comment #2: 

Hi Chris,

I am back working on CERTI in order to make it more HLA compliant.
I'm not able to reproduce your bug?
May be some other fix we did fix this one two?
Could try the current CVS code in order to tell me
if the bug is still there?

If it is may be you can tell me a little more about your test?

How many federate?
What is the exact sequence of the RTI request
I did in a first federate:

createFederationExecution
joinFederationExecution
getObjectClassHandle
getAttributeHandle
publishObjectClass
registerObjectInstance
updateAttributeValues
resignFederationExecution
destroyFederationExecution

then in another one:
createFederationExecution
joinFederationExecution
getObjectClassHandle
getAttributeHandle
subscribeObjectClassAttributes
tick tick tick (in order to get reflectAttributeValues called)
resignFederationExecution
destroyFederationExecution


Eric NOULARD <erk>
Group administrator
Sun 09 Dec 2007 05:04:10 PM UTC, comment #1: 

You are right I did not find any restriction
on attribute or parameter name.
I've just applied your patch to the CVS tree.
Thanks.

Eric NOULARD <erk>
Group administrator
Mon 19 Nov 2007 03:33:08 PM UTC, original submission:  

There is nothing in the HLA specification that disallows "timestamp" as an attribute or parameter name. However, CERTI currently does not work if there is an attribute or parameter name "Timestamp". This should be corrected.

Enclosed is a patch that corrects this problem.

Chris Rule <crule>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #15614:  TestFed.fed added by erk (1KiB - application/octet-stream - Buggy when read)
file #14432:  timestamp.patch added by crule (3KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by erk (Notified a problem with "timestamp" on ML)
  • -email is unavailable- added by erk (Posted a comment)
  • -email is unavailable- added by crule (Submitted the item)
  •  

    Follow 15 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-04-29 erk Open/ClosedOpen Closed
        Fixed ReleaseCVS 3.3.2
    2008-10-21 erk StatusIn Progress Ready For Test
        Fixed ReleaseUnknown CVS
    2008-05-06 erk Attached File- Added TestFed.fed, #15614
        StatusReady For Test In Progress
        Carbon-Copy- Added michaelraab
    2008-04-23 erk Open/ClosedClosed Open
        Fixed Release3.2.6 Unknown
    2008-03-22 erk Open/ClosedOpen Closed
        Fixed ReleaseCVS 3.2.6
    2007-12-09 erk StatusNone Ready For Test
        Assigned toNone erk
        Fixed ReleaseNextRelease CVS
    2007-11-19 crule Attached File- Added timestamp.patch, #14432

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code