On 18/11/11 5:58 PM, Mariano Martinez Peck wrote:
I've just noticed that even with the PUSecurity object being striped before serialization, I'm still seeing that the files are big and the same size. It seems that my mapping strategy was leaving off a lot more than just the PUSecurity object.
You debug you can do is to put a halt in FLSerialization>>run just after #analysisStep is done. Once there you can inspect the instVar 'clusters' and see how many clusters you have and how many objects each cluster has.
Thanks for the hint. I've not had to dive into Fuel's internals, so far. Anyhow, I've finally got the problems cleaned up. Mainly, I had to make sure that all references to the original root of the subtree, are replaced by a reference to a copy of the root. It needs to be a copy, because its parent must be set to nil, but that cannot be done to the original object. Other problems flowed from having to make a copy of the root. If you miss one reference, then that one reference will pull the entire kernel into the serialization. With the new code, I should be able to create new PRStructure or PRComponent, without having to add any custom visitor code (which I had to do with my old mapping strategy).