Portico is an open source, cross-platform, fully supported HLA RTI implementation. Designed with modularity and flexibility in mind, Portico is a production-grade RTI for the Simulation and Training Community, so come say hi!
The implementation of the joinFederationExecution( String federateName, String federateType, String federationName, URL[] fomModules ) method in Rti1516eAmbassador ignores the federateType parameter.
When creating the JoinFederation request instance, it only uses the federateName, federationName and fomModules parameters. It's worth noting that the JoinFederation class currently has no ability to store the federateType parameter in any case.
A practical side effect of this is that when one subscribes to the HLAobjectRoot.HLAmanager.HLAfederate attribute reflection to discover federates joining the federation, the value for the HLAfederateType attribute is always the same as the HLAfederateName attribute, no matter what parameter was used for federateType during the joinFederationExecution(...) call.
This means that one cannot detect the types of a federate joining the federation based on the value of the HLAfederateType in the attribute reflections.
A temporary workaround would be to name federates in such a way as to encapsulate the federate type information (e.g., fedtypeA-fedname1, fedtypeA-fedname2, fedtypeB-fedname1, fedtypeB-fedname2, etc...), but support of the federateType parameter is preferred to this.
The implementation of the
joinFederationExecution( String federateName, String federateType, String federationName, URL[] fomModules )
method inRti1516eAmbassador
ignores thefederateType
parameter.When creating the
JoinFederation
request instance, it only uses thefederateName
,federationName
andfomModules
parameters. It's worth noting that theJoinFederation
class currently has no ability to store thefederateType
parameter in any case.A practical side effect of this is that when one subscribes to the
HLAobjectRoot.HLAmanager.HLAfederate
attribute reflection to discover federates joining the federation, the value for theHLAfederateType
attribute is always the same as theHLAfederateName
attribute, no matter what parameter was used forfederateType
during thejoinFederationExecution(...)
call.This means that one cannot detect the types of a federate joining the federation based on the value of the
HLAfederateType
in the attribute reflections.A temporary workaround would be to name federates in such a way as to encapsulate the federate type information (e.g.,
fedtypeA-fedname1
,fedtypeA-fedname2
,fedtypeB-fedname1
,fedtypeB-fedname2
, etc...), but support of thefederateType
parameter is preferred to this.