openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milosz Tylenda (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (OPENJPA-6) OpenJPA doesn't meaningfully implement JDBC3, JDBC4 methods in its delegates
Date Fri, 25 Jun 2010 19:02:59 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Milosz Tylenda reassigned OPENJPA-6:
------------------------------------

    Assignee: Milosz Tylenda

> OpenJPA doesn't meaningfully implement JDBC3, JDBC4 methods in its delegates
> ----------------------------------------------------------------------------
>
>                 Key: OPENJPA-6
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-6
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Patrick Linskey
>            Assignee: Milosz Tylenda
>            Priority: Minor
>
> OpenJPA's JDBC wrappers throw UnsupportedOperationException for all the JDBC3 and JDBC4
methods. While OpenJPA doesn't use any of these methods, our mechanism for implementing them
is limiting, in that users who obtain Connections from OpenJPA will not be able to use the
new JDBC3/JDBC4 methods in their own code. Ideally, we should provide some means for people
to designate to OpenJPA that it should use a dynamic proxy to implement the unimplemented
methods. This shouldn't be the default behavior, as the dynamic proxy will add overhead, but
certainly could be desirable for some. I'll file an issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message