openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (OPENJPA-1492) Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from private to public
Date Mon, 08 Mar 2010 15:28:27 GMT

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

Donald Woods reassigned OPENJPA-1492:
-------------------------------------

    Assignee: Donald Woods

> 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
>            Assignee: Donald Woods
>
> 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.


Mime
View raw message