Patrick now has god-like powers to edit JIRA issues. Use them wisely. ;-)

Specifically, Patrick will now find more left jira navbar options from which to choose how to spend his time.


On Jul 31, 2006, at 10:29 PM, Patrick Linskey (JIRA) wrote:

[ page=comments#action_12424742 ]

Patrick Linskey commented on OPENJPA-6:

Patrick also thought that 'Clone' would provide an opportunity to mutate the description.

See the last paragraph of the description for the interesting bits.

OpenJPA doesn't meaningfully implement JDBC3, JDBC4 methods in its delegates --------------------------------------------------------------------- -------

                Key: OPENJPA-6
            Project: OpenJPA
         Issue Type: Improvement
           Reporter: Patrick Linskey

Patrick opines:
OpenJPA implements Statement, ResultSet, Connection, and maybe a
couple other JDBC interfaces. See
org.apache.openjpa.lib.jdbc.Delegating*. We do this for a number of
reasons: to resolve database-specific bugs in a transparent fashion, to
provide logging, to handle reference counting, etc.
The pressing issue is that we must provide implementations of all of the
methods in the various java.sql interfaces. The fact that we do not
implement the new JDBC4 methods is why OpenJPA won't currently compile
against JDK6. This is pretty easy to fix; take a look at
org.apache.openjpa.lib.jdbc.DelegatingStatement to see how we handled
this for JDBC3. Since we know that we never invoke the new methods, we can happily throw unsupported operation exceptions for the new methods.
However, these unsupported methods do provide a challenge. While Kodo
doesn't use any of these methods, our mechanism for implementing them is
limiting, in that users who obtain Connections from Kodo 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.
If you think it was sent incorrectly contact one of the administrators: Administrators.jspa
For more information on JIRA, see: software/jira

Craig Russell
Architect, Sun Java Enterprise System
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to