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:46:19 UTC
[jira] Created: (OPENJPA-1492) Change access on
ReverseMappingTool#getAnnotationsForMeta(Object) from protected to public
Change access on ReverseMappingTool#getAnnotationsForMeta(Object) from protected to public
------------------------------------------------------------------------------------------
Key: OPENJPA-1492
URL: https://issues.apache.org/jira/browse/OPENJPA-1492
Project: OpenJPA
Issue Type: Improvement
Components: tooling
Affects Versions: 2.0.0-beta, 2.0.0-M3, 2.0.0-M2, 2.0.0-M1, 1.2.2, 1.2.1, 1.2.0, 1.1.0, 1.0.3, 1.0.2, 1.0.1, 1.0.0
Reporter: Laird Nelson
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1492) Change access on
ReverseMappingTool#getAnnotationsForMeta(Object) from private to public
Posted by "Laird Nelson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (OPENJPA-1492) Change access on
ReverseMappingTool#getAnnotationsForMeta(Object) from private to public
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1492:
----------------------------------
Fix Version/s: (was: 2.0.0)
2.0.0-beta3
> 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
> Fix For: 1.3.0, 2.0.0-beta3
>
>
> 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.
[jira] Assigned: (OPENJPA-1492) Change access on
ReverseMappingTool#getAnnotationsForMeta(Object) from private to public
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (OPENJPA-1492) Change access on
ReverseMappingTool#getAnnotationsForMeta(Object) from private to public
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1492.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.3.0
trunk - r920404
13x - r920405
> 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
> Fix For: 1.3.0, 2.0.0
>
>
> 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.