[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ]
Kristian Waagan updated DERBY-1146:
---
Attachment: derby-1146-v2-enable.diff
'derby-1146-v2-enable.diff' enables the VerifySignatures patch, as it no longer
fails. In addition, it sorts the
[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ]
Kristian Waagan updated DERBY-1146:
---
Derby Info: [Patch Available]
Verify that JDBC4 signatures satisfied
--
Key: DERBY-1146
URL:
[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ]
Knut Anders Hatlen updated DERBY-1146:
--
Attachment: client.txt
embedded.txt
The test is not ready to be uploaded yet, but I thought I'd share the
results I have found so
This is very interesting.
However, isn't it the job of the compiler to figure out that the
signatures of an interface has been implemented ?
I did the following change to EmbedResultSet40:
I added implements java.sql.ResultSet in the class definition. The
compilation then failed with:
Andreas Korneliussen [EMAIL PROTECTED] writes:
This is very interesting.
However, isn't it the job of the compiler to figure out that the
signatures of an interface has been implemented ?
It should be :)
I think it would be good for all EmbedXXX40 to declare which interface
they are
Also, I think this also indicates that we should consider using
delegation instead of inheritance for code reuse.
Andreas
I didn't get it, how does it indicates that ?
anurag
Anurag Shekhar wrote:
Also, I think this also indicates that we should consider using
delegation instead of inheritance for code reuse.
Andreas
I didn't get it, how does it indicates that ?
anurag
Because now we are fooling the compiler to think that EmbedXXX40 classes
implement
Andreas Korneliussen [EMAIL PROTECTED] writes:
This is very interesting.
However, isn't it the job of the compiler to figure out that the
signatures of an interface has been implemented ?
I did the following change to EmbedResultSet40:
I added implements java.sql.ResultSet in the class
Adding the implements java.sql.XXX should take care of detecting missing
methods in 4.0 classes. Delegating calls may be a safer way doing
things but it has practical problem take the case of EmbedConnection.
This class is being used in 102 different places in engine code.
I haven't seen all
I think that this test is the gold-standard. It supplies a missing
sanity check which won't be available until we have a TCK for JDBC4.
Thanks for writing this test, Knut Anders.
Regards,
-Rick
Knut Anders Hatlen wrote:
Andreas Korneliussen [EMAIL PROTECTED] writes:
This is very
[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ]
Knut Anders Hatlen updated DERBY-1146:
--
Component: Test
Verify that JDBC4 signatures satisfied
--
Key: DERBY-1146
URL:
[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ]
Rick Hillegas updated DERBY-1146:
-
Component: JDBC
Verify that JDBC4 signatures satisfied
--
Key: DERBY-1146
URL:
12 matches
Mail list logo