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/07/24 00:01:31 UTC

[jira] Updated: (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:all-tabpanel ]

Catalina Wei updated OPENJPA-266:
---------------------------------

    Attachment: OpenJPA-266.patch

Allow vendor  "extended" DB Dictionaray plugins.
For example, 
public Class MyDB2Dictionary 
    extends org.apache.openjpa.jdbc.sql.DB2Dictionary { ...}

By changing default plugin values by :
JDBCConfigurationImpl.dbdictionaryPlugin.setAlias("db2", "test.MyDB2Dictionary")

will instantiate  test.MyDB2Dictionary

> 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.