xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [POLL]: Dropping JDK 1.3 support for Xerces-J?
Date Sat, 10 Jul 2010 10:35:41 GMT
+1 for dropping support for 1.3

1.5 has a better memory model but as far as I know, this is part of
the JVM, rather than depending on the compiler, i.e. merely running
under 1.5 will help (please correct me if I'm wrong!). Switching to
1.5 involves a lot of work initially (generics, annotations) before
one can take full advantage of all its benefits.

So I would be inclined to do at least one release which requires 1.4,
and then look again at 1.5.

On 8 July 2010 19:27, Dave Brosius <dbrosius@baybroadband.net> wrote:
> the end of life on 1.4 was fall 2008!
>
> +1 in going to 1.5 directly
>
> Michael Glavassevich <mrglavas@ca.ibm.com> wrote:
>
>>
>>Hi Jake,
>>
>>"Jacob Kjome" <hoju@visi.com> wrote on 07/08/2010 12:58:49 PM:
>>
>>> I have a library I develop (XMLC [1]) that depends on JDK1.3 and also
>>depends
>>> on Xerces.  That said, part of the reason of depending on JDK1.3 is
>>> to stay in
>>> line with the Xerces dependency on JDK1.3.  The other reason is
>>thatJDK1.3 is
>>> free and clear of any built-in XML APIs, which allows me to include
>>exactly
>>> the JAXP library of my choice (xml-apis.jar) without worry of
>>compile-time
>>> binding to odd invalid APIs included in 1.4 (such as some stuff meant for
>>the
>>> HTML2 API that got placed in the HTML1 API DOM package namespace).  But
>>if
>>> Xerces decides to move to a later version of Java, then I will probably
>>move
>>> XMLC right along with it.
>>>
>>> That said, I would think that if Xerces were going to bother making a
>>move at
>>> all it would move to JDK1.5 rather than bother with 1.4.  Xerces 2.10 is
>>> always there for 1.3 and 1.4 codebases, which should all be well into
>>> maintenance mode meaning few, if any, library changes.
>>
>>It's often not a choice but a constraint of the environment the developer
>>is working in, having to write a new application on top of a product stack
>>which is stuck on one of these earlier JDK releases. JDK 1.4 isn't dead
>>yet; still in service for some vendors, including Oracle/Sun if you're a
>>business willing to pay for the support. Not aware of any vendors
>>supporting JDK 1.3 anymore though.
>>
>>> Moving to 1.5 would
>>> allow Xerces to take advantage of all the new language constructs added
>>in
>>> 1.5, as well as APIs added in 1.5 (e.g., StringBuilder -vs-
>>StringBuffer).
>>
>>Right. We all talked about the benefits of moving up even higher to Java 5
>>and 6 before, but have been quite conservative about upgrading because of
>>where we are in the food chain.
>>
>>> So, +1 for changing JDK dependency in general, but I would prefer a move
>>> straight to JDK1.5+ skipping JDK1.4 support.  This also seems to be
>>> what a lot
>>> of Apache commons libraries are doing, so it's certainly not
>>unprecedented.
>>>
>>> [1] http://forge.ow2.org/projects/xmlc/
>>>
>>>
>>> Jake
>>>
>>> On Thu, 8 Jul 2010 11:36:07 -0400
>>>   Michael Glavassevich <mrglavas@ca.ibm.com> wrote:
>>> >
>>> >
>>> > Hi all,
>>> >
>>> > (including general@xml.apache.org on the cc list to hopefully reach a
>>wider
>>> > audience)
>>> >
>>> > We're talking again on the Xerces j-dev mailing list about dropping
>>support
>>> > for JDK 1.3. The reason being that current builds of the XPath 2.0
>>> > processor (Eclipse PsychoPath) used by the XML Schema 1.1
>>implementation
>>> > require JDK 1.4. While we do have a one-off PsychoPath jar that was
>>built
>>> > with JDK 1.3 some time ago, in order to pick up recent bug fixes in
>>this
>>> > library we need to refresh it with the JDK 1.4 version. This would only
>>> > impact the XML Schema 1.1 enabled release for now but at some point in
>>the
>>> > future when XML Schema 1.1 becomes stable (both spec and impl) this
>>would
>>> > get merged into the main line.
>>> >
>>> > Given the age of JDK 1.3 and that it's generally out of service my
>>> > intuition is that this upgrade would probably be okay but wanted to
>>check
>>> > with users on their needs. Is there anyone out there still using
>>Xerces-J
>>> > with JDK 1.3? If you are, how long into the future will you continue to
>>do
>>> > so, and would you be willing to migrate to JDK 1.4 (or higher) to be
>>able
>>> > to use XML Schema 1.1?
>>> >
>>> > Thanks.
>>> >
>>> > Michael Glavassevich
>>> > XML Parser Development
>>> > IBM Toronto Lab
>>> > E-mail: mrglavas@ca.ibm.com
>>> > E-mail: mrglavas@apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>>Thanks.
>>
>>Michael Glavassevich
>>XML Parser Development
>>IBM Toronto Lab
>>E-mail: mrglavas@ca.ibm.com
>>E-mail: mrglavas@apache.org

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


Mime
View raw message