Re: [certi-dev] RequestClassAttributeValueUpdate service
From:
Michael Raab
Subject:
Re: [certi-dev] RequestClassAttributeValueUpdate service
Date:
Thu, 30 Sep 2010 16:39:58 +0200
Thanks for the fast reply.
How much work do you expect on this
issue? What exactly is missing? Sorry but I'm missing the whole picture
as I'm not familiar with CERTI source code
Thanks,
Michael
Dipl.-Inf. Michael Raab
Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden http://www.iff.fraunhofer.de
oder http://www.vdtc.de
Von:
Eric Noulard <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
09/30/2010 04:34 PM
Betreff:
Re: [certi-dev]
RequestClassAttributeValueUpdate service
Gesendet von:
address@hidden
2010/9/30 Michael Raab <address@hidden>:
> Hi all,
>
> I got a runtime warning that the service RequestClassAttributeValueUpdate
is
> not implemented yet. Looking into the code it seems that the appropriate
> method is written but not called. Instead a warning is generated.
> Is it simple mistake or is there a reason for not calling?
The code is called in libRTI (RTIambassador.cc)
then a message is sent to RTIA process
where the method is not implemented (RTIA_federate.cc)
thus the warning.
CERTI has a multi-process implementation for which many (but not all)
RTI services have to be handle at different places:
libRTI --> the HLA API
RTIA --> Local RTI component
RTIG --> Central RTI component