[OPENJPA-1360] ReverseMappingTool omits nullable, length, etc. when ClassMapping.setEmbedded(true) is called

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2
• Fix Version/s: 1.3.0, 2.0.0-beta3
• Component/s: tooling
• Assignee: Donald Woods
• Reporter: Laird Nelson
• Created: 23/Oct/09 15:53
• Updated: 29/Mar/10 23:17
• Resolved: 08/Mar/10 21:48

Description

In my ReverseCustomizer, I call classMapping.setEmbedded(true). This is because for a variety of reasons I need the code that is generated by the ReverseMappingTool to be @MappedSuperclasses, not @Entities.

Indeed when I do this, the resulting class is a @MappedSuperclass (great!) BUT all of the length and nullable and other @Column attributes are missing. In other words, all simple fields receive only a @Basic annotation, with no attributes, and nothing else. In addition, the class declaration receives a @Table annotation with no attributes. (I'm using the command line flag that instructs the ReverseMappingTool to generate annotations.)

Ideally I'd like the generated source code to look identical to the source code that would be generated for a ClassMapping where setEmbedded(true) was never called, except of course that I want the @Entity annotation to be replaced with @MappedSuperclass.

Obviously if there is a better way from within a ReverseCustomizer for me to accomplish my (very odd) goals (mandated by a strange development process and a 30-year-old database), I am all ears.

Issue Links

• relates to: OPENJPA-1492 Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from private to public