You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Milosz Tylenda (JIRA)" <ji...@apache.org> on 2010/06/25 21:02:59 UTC

[jira] Assigned: (OPENJPA-6) OpenJPA doesn't meaningfully implement JDBC3, JDBC4 methods in its delegates

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