[
https://issues.apache.org/jira/browse/OPENJPA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515020
]
Patrick Linskey commented on OPENJPA-266:
-----------------------------------------
Agreed. Additionally, it is already trivial for vendors to repackage OpenJPA
with different dbdictionaries. All you need to do is create a ProductDerivation
that changes the aliases listed in the JDBCConfigurationImpl.dbdictionaryPlugin.
See JDBCPersistenceProductDerivation for an example of a product derivation
that changes alias settings.
> 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-266.patch, OPENJPA-266.patch.txt
>
>
> 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.
