You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Catalina Wei (JIRA)" <ji...@apache.org> on 2007/06/26 22:18:26 UTC
[jira] Commented: (OPENJPA-266) Add Extensibility: Change "private"
field/method to "protected" or "public" in OpenJPA classes to be
extendable
[ https://issues.apache.org/jira/browse/OPENJPA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508314 ]
Catalina Wei commented on OPENJPA-266:
--------------------------------------
This patch has passed TCK with Derby
Catalina
> Add Extensibility: Change "private" field/method to "protected" or "public" in OpenJPA classes to be extendable
> ----------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-266
> URL: https://issues.apache.org/jira/browse/OPENJPA-266
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 1.0.0
> Reporter: Catalina Wei
> Priority: Trivial
> Fix For: 1.0.0
>
> Attachments: openjpa-jdbc.patch
>
>
> In order to extend existing OpenJPA classes, for example OperationOrderUpdateManager, private field or method needed to change to protected or public.
> This kind of modification is not adding any functionality but making OpenJPA classes subclassable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.