[OPENJPA-1492] Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from private to public

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.2.0, 1.2.1, 1.2.2, 2.0.0-M1, 2.0.0-M2, 2.0.0-M3, 2.0.0-beta
• Fix Version/s: 1.3.0, 2.0.0-beta3
• Component/s: tooling
• Assignee: Donald Woods
• Reporter: Laird Nelson
• Created: 01/Feb/10 18:45
• Updated: 29/Mar/10 23:17
• Resolved: 08/Mar/10 17:08

Description

Because of two other related bugs, it is impossible to have the ReverseMappingTool output Java code that is annotated properly.

The easiest way to work around the two related bugs would be for the ReverseCustomizer supplier to return code from its methods like getClassCode(). But if you do this, you need the ability to have OpenJPA hand you the annotations it has determined are necessary. Those annotations are currently present in the ReverseMappingTool#_annos field, which is accessed by the currently private getAnnotationsForMeta(Object) method.

Moving the access level of this method to public would allow a great deal of flexibility in ReverseCustomizer implementations.

Issue Links

• is related to: OPENJPA-1417 Supplying CodeFormat to ReverseCustomizer prevents usage of annotations
• is related to: OPENJPA-1423 @ManyToOne is never output with referencedColumnName attribute, even when called for
• is related to: OPENJPA-1360 ReverseMappingTool omits nullable, length, etc. when ClassMapping.setEmbedded(true) is called