cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby" <ru...@us.ibm.com>
Subject Re: JDK 1.3 vs JDK 1.4 issue
Date Thu, 18 Apr 2002 12:03:01 GMT
"Stefano Mazzocchi" <stefano@apache.org> wrote:

> We could also have our representatives for Java 1.5 ask the reasons why
> the JDBC were modified in a back incompatible way and what is the
> solution they thought (if any) about allowing WORA between java versions
> (if they thought about it at all for JDBC).

http://java.sun.com/j2se/1.4/index.html

   In addition to new features, version 1.4 addresses key customer issues
   and is fully compatible with previous J2SE software releases.

I asked this very same question I started testing with JDK 1.4 with Gump.
The response was that it only affected database vendors.  I provided
numerous counter examples, asked for support from jcp@apache and exchanged
e-mail with the spec lead for JDBC.

I was not successful.  Below is one of the e-mails from the period:

- Sam Ruby

I'm looking for suggestions on how to provide constructive feedback on the
JDK 1.4 beta.  Note: the JDK is just a beta, so problems are not
unexpected.  The question is how to best work together to make sure that
when it goes production that users wishing to use Apache projects on this
new platform will have the minimum of problems.

Background: I've gotten JDK 1.4 beta for Linux, and have let lose Gump on
it.  None of the failures in today's run
(http://jakarta.apache.org/builds/gump/2001-06-01/) are present when using
JDK 1.3.

Question: Is there value in a consolidated Apache feedback, or should I
encourage projects to pursue the issues separately?  Here's a quick
summary:

   Biggest issue is JDBC 3.0 changes.  Affects struts, xalan2,
   commons-dbcp, avalon, and castor.

   Changes is compiler rules (variable scoping, inner classes) affects
   batik.

   Changes in reflection affects Scarab at runtime.

   Bug in Crimson affects Gump itself (the bug was fixed in the Apache tree
   over two months ago).

   Overall performance of compiler seems noticably worse.  Complete build
   of most projects used to take 80-90 minutes.  This partial build (some
   failures, many projects skipped) took 122 minutes.

- Sam Ruby


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message