I don’t see any obvious configuration problem here. And I don’t think that it has something to do with the annotation-based configuration. But you could try (just for a test) to do the same configuration via the XML configuration file. But I really don’t think that this will make a difference.
It seems like there is some other thing wrong here. You could try to debug the application and set a breakpoint at ParentingPostProcessor.createAncestry().
This method performs the parenting postprocessing and is really straightforward. The interesting question is if this method gets executed correctly and what it does with your mappings.
If you don’t want to spend much time on debugging you could create a ticket and attach a small sample application so I can start the debugging.