Re: java.sql.SQLRuntimeException: Cannot store DataSet instance to WeakHashMap

The following message is a courtesy copy of an article that has been posted to comp.lang.java.databases as well. I'm cc'ing this reply to derby-user@db.apache.org, since not many derby people follow this newsgroup. Harri Pesonen [EMAIL PROTECTED] writes: I get the following error (sometimes)

Re: java.sql.SQLRuntimeException: Cannot store DataSet instance to WeakHashMap

Hi all This is a JDK6 b98 problem, and not related to Derby. Bernt [EMAIL PROTECTED] wrote: The following message is a courtesy copy of an article that has been posted to comp.lang.java.databases as well. I'm cc'ing this reply to derby-user@db.apache.org, since not many derby people

10.2 licensing issue

I must report today that the restrictions imposed by the beta JDK license have not been lifted. As you know, the JDK 6 beta license requires a disclaimer that bars the use of the code for any productive use. This restriction is meant to forestall binary incompatibilities with the final, GA

Re: 10.2 licensing issue

Wow! Thanks for the update, Rick. I agree that option #1 (release 10.2 without JDBC 4) is best. -jean Rick Hillegas wrote: I must report today that the restrictions imposed by the beta JDK license have not been lifted. As you know, the JDK 6 beta license requires a disclaimer that bars the

Re: 10.2 licensing issue

On 9/11/06, Rick Hillegas [EMAIL PROTECTED] wrote: I can see two alternatives for us: 1. Ship 10.2 on the current schedule but do not include the JDBC4 drivers. When run on Java SE 6, Derby 10.2 would continue to expose our JDBC3 implementation. In addition, we would remove JDBC4-specific

Re: 10.2 licensing issue

Andrew McIntyre wrote: On 9/11/06, Rick Hillegas [EMAIL PROTECTED] wrote: I can see two alternatives for us: 1. Ship 10.2 on the current schedule but do not include the JDBC4 drivers. When run on Java SE 6, Derby 10.2 would continue to expose our JDBC3 implementation. In addition, we

Re: 10.2 licensing issue

Rick Hillegas wrote: I can see two alternatives for us: 1. Ship 10.2 on the current schedule but do not include the JDBC4 drivers. When run on Java SE 6, Derby 10.2 would continue to expose our JDBC3 implementation. In addition, we would remove JDBC4-specific documentation from our user

Have you tried 10.2 beta?

Have you tried 10.2 beta? What were your results? Positive or negative or why it is not worth your time I'd like to know. The reason is this: Open source software development is based (as I understand it) on iterative feedback and involvement from users especially beta. Any regression

Re: Have you tried 10.2 beta?

Stephen Caine wrote: I followed your link to send in beta reports (http://wiki.apache.org/ db-derby/TenTwoApplicationTesting), but I could not find how to submit a report. Can you be more specific? Thanks Steven! And I assume all went well. This is great news. Please just edit the wiki