This issue is still current and the above test case failed when tested with version 4.3.5 (just changed the pom). As test case suggests the issue can be easily avoided by renaming ids without @id annotations to other until this is fixed.

Thanks