Use allocateNextId when building new NextObjective

In order to avoid nextId collisions, all users of the flow objective
service should use the provided allocateNextId() method when
constructing new NextObjectives. I found one instance where this was not
the case: CordMcast.

Solution: removed private id generator from CordMacst and replaced it
with allocateNextId.

Change-Id: I134931b58c524291ae937dd6f0051ee549236734
1 file changed
tree: 66c22b374e9d61d36fe44cdb8ec23a16ce050bdc
  1. features.xml
  2. pom.xml
  3. src/