Re: [certi-dev] Calling UpdateAttributeValues with NULL

[Michael Raab]

Hi Eric,

this one seems to be a good approach,
to be safe an the one side but also compatible with DMSO on the other.

if ( theTag != NULL) {
        req.setTag(theTag);      
          
}

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:      
 11/10/2010 09:33 AM
Betreff:    
   Re: [certi-dev]
Calling UpdateAttributeValues with NULL
Gesendet von:    
   address@hidden

---

2010/11/10 Michael Raab <address@hidden>:
> Hi Eric,
>
> there's a RTIIInternal exception thrown with message "Calling
> UpdateAttributeValues with NULL".
>
> Why is that needed? Couldn't you just pass an empty string if the
user
> decides to pass NULL?

Because the user may erroneously believing he was passing a real tag?

I think it was already discussed, and it was considered a bug on federate
side.
However I understand that it would be a nice "legacy" feature
I'll check and come back to you.

> In dmso it was possible you pass NULL as TAG.

May be we can just not put a tag in the internal message and
not throw the exception.

Like:
if ( theTag != NULL) {
                
  req.setTag(theTag);            
    
}

Would you try this, does it work for you?        
        
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org

-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel