Right, IBM has an alternate interface (other than JDBC) to access DB2. In order to use OpenJPA thru that interface in a project, we need to sub-class JDBC StoreManager. More detail information can be provided once it becomes available. Thanks.
On 1/8/08, Pinaki Poddar (JIRA) <[EMAIL PROTECTED]> wrote: > > > [ > https://issues.apache.org/jira/browse/OPENJPA-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556965#action_12556965] > > Pinaki Poddar commented on OPENJPA-477: > --------------------------------------- > > "a recent practice for providing a proprietary extension to use an > interface other than JDBC" - elaboration on this extension will help > everyone to appreciate the reasons for this patch better -- especially when > the changes required by this extension is not only confined at StoreManager > but permeates to almost every tier of OpenJPA (StateManager, Broker, > Configuration...). > > > > > making StoreManager more flexible and extensible. > > ------------------------------------------------- > > > > Key: OPENJPA-477 > > URL: https://issues.apache.org/jira/browse/OPENJPA-477 > > Project: OpenJPA > > Issue Type: Improvement > > Components: kernel > > Affects Versions: 1.0.2 > > Reporter: Daniel Lee > > Fix For: 1.0.2, 1.1.0 > > > > Attachments: OPENJPA-477.patch > > > > > > The OpenJPA StoreManager needs some modifications to make it more > flexible and extensible. For example, some private methods and attributes > need to made either public or protected. The attached patch identifies the > areas that have been identified thus far. Please let me know if there are > any concerns. Many thanks in advance. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
