We are using the java assembler to fill collections. Sometimes an add comes in as a CollectionEvent.ADD with items[0] being the fully populated new item. This is good. Then some other times, the item comes in as a sequence of ADD, UPDATE, and REPLACE events. The ADD is basically a null object, the UPDATE sets the uid, then the REPLACE replaces with the fully populated object.
I think this is related to having the item pending at the point of addition but am not sure why or if this is something that can be avoided. Anyone see this behavior before?
