Return-Path: Delivered-To: apmail-xml-general-archive@www.apache.org Received: (qmail 492 invoked from network); 11 Nov 2008 20:02:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Nov 2008 20:02:06 -0000 Received: (qmail 80423 invoked by uid 500); 11 Nov 2008 20:02:13 -0000 Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 80389 invoked by uid 500); 11 Nov 2008 20:02:13 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: general@xml.apache.org List-Id: Delivered-To: mailing list general@xml.apache.org Delivered-To: moderator for general@xml.apache.org Received: (qmail 28340 invoked by uid 99); 11 Nov 2008 14:34:52 -0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9440A.90F0EAF4" Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future) X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 11 Nov 2008 15:34:08 +0100 Message-ID: <96458C389BF1724995FFD7FAD88926371141C9@ex.nc-sb.de> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future) Thread-Index: AclC6J15d71uzNS/SAC26U7a4ymNCQA98nzg References: From: "Ludger Buenger" To: , Cc: X-OriginalArrivalTime: 11 Nov 2008 14:34:13.0305 (UTC) FILETIME=[91312A90:01C9440A] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C9440A.90F0EAF4 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Before Advancing beyond 1.3 I'd suggest to maybe initiate a usage poll analogous to http://wiki.apache.org/xmlgraphics/UserPollOct2007 to get an overview which JDK version is still in use and required by Xerces-J users. =20 That would give the community a foundation to base a good decision upon. =20 =20 From: Michael Glavassevich [mailto:mrglavas@ca.ibm.com]=20 Sent: Monday, November 10, 2008 4:52 AM To: j-dev@xerces.apache.org; j-users@xerces.apache.org Cc: general@xml.apache.org Subject: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future) =20 Hi all, (including general@xml.apache.org on the cc list to hopefully reach a wider audience) I would like to propose that we officially drop support for JDK 1.2 in the next release of Xerces-J. Though the documentation [1] states that Xerces supports JDK 1.2 it has been years since we have built or tested binaries with this level. All of the recent releases were built and tested with JDK 1.3. It was brought to my attention that the code [2] since at least 2006 has had a dependency on APIs introduced in JDK 1.3. So we inadvertently moved on awhile ago. It seems this has not been a practical issue for most users since we've received no posts on these lists about it and received no other bug reports. It's not clear that there would be much benefit in restoring JDK 1.2 compatibility at this point. It's been out of service for years and looking around Apache it seems most projects run on JDK 1.4 or higher with some of the stragglers [3][4] below that moving up soon. If you have serious concerns regarding Xerces abandoning JDK 1.2 support please send an email to the j-dev@xerces.apache.org mailing list, specifying why you can't use a higher level of JDK and what parser features you are using. While on the subject I wonder what the community would think of us eventually dropping support for JDK 1.3 and possibly 1.4. There were features introduced in JDK 1.4 and 5 which Xerces could benefit from (e.g. NIO, java.lang.CharSequence, exception chaining, java.lang.StringBuilder, java.util.concurrent.*, etc...). That's not something I'm proposing today (or thinking of proposing for awhile) but would like to hear feedback from users (please send to j-dev@xerces.apache.org) who may still need new versions of Xerces which run on JDK 1.3 and 1.4. It would also be nice hear from folks who've long since moved on to Java 5 and beyond and would like to see Xerces take advantage of JDK 1.4 and 5 features. Thanks. [1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11 =20 [2] http://issues.apache.org/jira/browse/XERCESJ-1297 =20 [3] http://marc.info/?l=3Dant-dev&m=3D122596549809889&w=3D2 =20 [4] http://marc.info/?l=3Dfop-user&m=3D119244442600564&w=3D2 =20 Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrglavas@ca.ibm.com E-mail: mrglavas@apache.org --=20 This message was scanned by ESVA and is believed to be clean.=20 Click here to report this message as spam. = =20 ------_=_NextPart_001_01C9440A.90F0EAF4 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Before Advancing beyond 1.3 I’d suggest to maybe = initiate a usage poll analogous to http://wiki.a= pache.org/xmlgraphics/UserPollOct2007 to get an overview which JDK version is still in use and required by = Xerces-J users.

 

That would give the community a foundation to base a good = decision upon.

 

 

From: Michael Glavassevich [mailto:mrglavas@ca.ibm.com]
Sent: Monday, November 10, 2008 4:52 AM
To: j-dev@xerces.apache.org; j-users@xerces.apache.org
Cc: general@xml.apache.org
Subject: Dropping JDK 1.2 support for Xerces-J (and possibly JDK = 1.3? 1.4? in the future)

 

Hi all,

(including general@xml.apache.org on the cc list to hopefully reach a = wider audience)

I would like to propose that we officially drop support for JDK 1.2 in = the next release of Xerces-J. Though the documentation [1] states that Xerces = supports JDK 1.2 it has been years since we have built or tested binaries with = this level. All of the recent releases were built and tested with JDK 1.3. It = was brought to my attention that the code [2] since at least 2006 has had a dependency on APIs introduced in JDK 1.3. So we inadvertently moved on = awhile ago. It seems this has not been a practical issue for most users since = we've received no posts on these lists about it and received no other bug = reports. It's not clear that there would be much benefit in restoring JDK 1.2 compatibility at this point. It's been out of service for years and = looking around Apache it seems most projects run on JDK 1.4 or higher with some of the stragglers [3][4] below that moving up soon.

If you have serious concerns regarding Xerces abandoning JDK 1.2 support = please send an email to the j-dev@xerces.apache.org mailing list, specifying = why you can't use a higher level of JDK and what parser features you are = using.

While on the subject I wonder what the community would think of us = eventually dropping support for JDK 1.3 and possibly 1.4. There were features = introduced in JDK 1.4 and 5 which Xerces could benefit from (e.g. NIO, java.lang.CharSequence, exception chaining, java.lang.StringBuilder, java.util.concurrent.*, etc...). That's not something I'm proposing = today (or thinking of proposing for awhile) but would like to hear feedback from = users (please send to j-dev@xerces.apache.org) who may still need new versions = of Xerces which run on JDK 1.3 and 1.4. It would also be nice hear from = folks who've long since moved on to Java 5 and beyond and would like to see = Xerces take advantage of JDK 1.4 and 5 features.

Thanks.

[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
[2] http://issues.apache.org/jira/browse/XERCESJ-1297=
[3] = http://marc.info/?l=3Dant-dev&m=3D122596549809889&w=3D= 2
[4] http://marc.info/?l=3Dfop-user&m=3D119244442600564&w= =3D2

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org


--
This message was scanned by ESVA and is believed to be clean.
Click here to report this message as spam.

------_=_NextPart_001_01C9440A.90F0EAF4--