Rebuild the full mapping from persistence-jpa-1.5.1 to reproduce the bug