In most cases, for efficiency, it is expected that Agents would actually manage objects that are subclasses of QmfAgentData and maintain subclass specific properties as primitives, only actually explicitly setting the underlying Map properties via setValue() etc. when the object needs to be "serialised". This would most obviously be done by extending the mapEncode() method (noting that it's important to call QmfAgentData's mapEncode() first via super.mapEncode(); as this will set the state of the underlying QmfData). @return the underlying map.
When we do a synchronous createSubscription the Subscription itself holds the info needed to populate the SubscriptionParams result. We encode the info in a Map to pass to the SubscribeParams Constructor
|
|