You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Laird Nelson (JIRA)" <ji...@apache.org> on 2010/02/01 19:48:20 UTC

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

     [ https://issues.apache.org/jira/browse/OPENJPA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Laird Nelson updated OPENJPA-1492:
----------------------------------

    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.
        Summary: Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from private to public  (was: Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from protected to public)

> Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from private to public
> ----------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1492
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1492
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: tooling
>    Affects Versions: 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
>            Reporter: Laird Nelson
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.