You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Michael Glavassevich <mr...@ca.ibm.com> on 2008/11/10 04:51:51 UTC
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=ant-dev&m=122596549809889&w=2
[4] http://marc.info/?l=fop-user&m=119244442600564&w=2
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Thanks Nathan. It works fine for me too.
I decided to change build.xml [1] so that source/target always matches the
version of Java used for invoking Ant. So 1.3 on 1.3, 1.4 on 1.4, etc...
[1] http://svn.apache.org/viewvc?view=rev&revision=719475
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
nbeyer@gmail.com wrote on 11/14/2008 11:24:32 PM:
> Here's a diff of the 'build.xml' to set these values. The build works
fine.
>
> Index: build.xml
> ===================================================================
> --- build.xml (revision 714215)
> +++ build.xml (working copy)
> @@ -255,7 +255,10 @@
> </fileset>
> </copy>
>
> - <xjavac srcdir="${build.src}"
> + <xjavac
> + source="1.3"
> + target="1.3"
> + srcdir="${build.src}"
> destdir="${build.dest}"
> classpath="${build.dir}/classes:${tools.dir}/${jar.
> apis}:${tools.dir}/${jar.resolver}:${tools.dir}/${jar.serializer}"
> debug="${debug}"
>
>
> On Fri, Nov 14, 2008 at 10:21 PM, Nathan Beyer <nd...@apache.org>
wrote:
> > Another optimization between 1.1 and 1.3 seems to be the copying of
> > method information from interfaces to classes. For example, take
> > ValidationHandler, an abstract class, which implements ContentHandler,
> > but only some of the methods. In the 1.1 version of the class file,
> > every method from the interface is represented in the bytecode. In the
> > 1.3 version of the class file, only the overridden methods are
> > represented in the bytecode.
> >
> > -Nathan
> >
> > On Fri, Nov 14, 2008 at 10:13 PM, Nathan Beyer <nd...@apache.org>
wrote:
> >> For the most part, the difference is usually only in the class file
> >> version. 1.1 has a version of 45.3, 1.2 has a version of 46.0 and 1.3
> >> has a version of 47.0. If the target is set to 1.3, then if the class
> >> files are loaded by a JRE < 1.3, they'll get a class loading error.
> >>
> >> From the detailed comparisons I've done on a few examples, the class
> >> file differences between a 1.1 target and a 1.3 target are in the
> >> constant pool. The constant pool of 1.3 class files is generally
> >> slightly smaller.
> >>
> >> -Nathan
> >>
> >> On Thu, Nov 13, 2008 at 9:43 PM, Michael Glavassevich
> >> <mr...@ca.ibm.com> wrote:
> >>> Hi Nathan,
> >>>
> >>> nbeyer@gmail.com wrote on 11/13/2008 09:54:57 AM:
> >>>
> >>> <snip/>
> >>>
> >>>> Personally, I like to set the source and targets, as the defaults
> >>>> prior to Java 5 were surprising, at least to me. If you don't set
> >>>> target=1.3 and use the J2SE 1.3 javac [1], the default bytecode
target
> >>>> is 1.1. If you use a J2SE 1.4 javac [2], the default bytecode target
> >>>> is 1.2. Since we're discussing dropping JDK 1.2 support, it just
> >>>> seemed natural to set the bytecode target appropriately.
> >>>
> >>> I've never read about the difference between bytecode targeted
> for 1.1, 1.2
> >>> and 1.3. Are there specific benefits to setting the target to 1.3?
> >>>
> >>>> Note - with Java 5 and Java 6, the javac defaults are now the same
> >>>> level as the JDK version and the ECJ follows these same defaults
> >>>>
> >>>> -Nathan
> >>>> [1] http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javac.html
> >>>> [2] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html
> >>>>
> >>>> >
> >>>> >> Anything else?
> >>>> >
> >>>> > That's about it.
> >>>> >
> >>>> >> +1 (non-binding) for that
> >>>> >>
> >>>> >> -Nathan
> >>>> >
> >>>> > 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-dev-unsubscribe@xerces.apache.org
> >>>> For additional commands, e-mail: j-dev-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: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
Here's a diff of the 'build.xml' to set these values. The build works fine.
Index: build.xml
===================================================================
--- build.xml (revision 714215)
+++ build.xml (working copy)
@@ -255,7 +255,10 @@
</fileset>
</copy>
- <xjavac srcdir="${build.src}"
+ <xjavac
+ source="1.3"
+ target="1.3"
+ srcdir="${build.src}"
destdir="${build.dest}"
classpath="${build.dir}/classes:${tools.dir}/${jar.apis}:${tools.dir}/${jar.resolver}:${tools.dir}/${jar.serializer}"
debug="${debug}"
On Fri, Nov 14, 2008 at 10:21 PM, Nathan Beyer <nd...@apache.org> wrote:
> Another optimization between 1.1 and 1.3 seems to be the copying of
> method information from interfaces to classes. For example, take
> ValidationHandler, an abstract class, which implements ContentHandler,
> but only some of the methods. In the 1.1 version of the class file,
> every method from the interface is represented in the bytecode. In the
> 1.3 version of the class file, only the overridden methods are
> represented in the bytecode.
>
> -Nathan
>
> On Fri, Nov 14, 2008 at 10:13 PM, Nathan Beyer <nd...@apache.org> wrote:
>> For the most part, the difference is usually only in the class file
>> version. 1.1 has a version of 45.3, 1.2 has a version of 46.0 and 1.3
>> has a version of 47.0. If the target is set to 1.3, then if the class
>> files are loaded by a JRE < 1.3, they'll get a class loading error.
>>
>> From the detailed comparisons I've done on a few examples, the class
>> file differences between a 1.1 target and a 1.3 target are in the
>> constant pool. The constant pool of 1.3 class files is generally
>> slightly smaller.
>>
>> -Nathan
>>
>> On Thu, Nov 13, 2008 at 9:43 PM, Michael Glavassevich
>> <mr...@ca.ibm.com> wrote:
>>> Hi Nathan,
>>>
>>> nbeyer@gmail.com wrote on 11/13/2008 09:54:57 AM:
>>>
>>> <snip/>
>>>
>>>> Personally, I like to set the source and targets, as the defaults
>>>> prior to Java 5 were surprising, at least to me. If you don't set
>>>> target=1.3 and use the J2SE 1.3 javac [1], the default bytecode target
>>>> is 1.1. If you use a J2SE 1.4 javac [2], the default bytecode target
>>>> is 1.2. Since we're discussing dropping JDK 1.2 support, it just
>>>> seemed natural to set the bytecode target appropriately.
>>>
>>> I've never read about the difference between bytecode targeted for 1.1, 1.2
>>> and 1.3. Are there specific benefits to setting the target to 1.3?
>>>
>>>> Note - with Java 5 and Java 6, the javac defaults are now the same
>>>> level as the JDK version and the ECJ follows these same defaults
>>>>
>>>> -Nathan
>>>> [1] http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javac.html
>>>> [2] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html
>>>>
>>>> >
>>>> >> Anything else?
>>>> >
>>>> > That's about it.
>>>> >
>>>> >> +1 (non-binding) for that
>>>> >>
>>>> >> -Nathan
>>>> >
>>>> > 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-dev-unsubscribe@xerces.apache.org
>>>> For additional commands, e-mail: j-dev-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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
Another optimization between 1.1 and 1.3 seems to be the copying of
method information from interfaces to classes. For example, take
ValidationHandler, an abstract class, which implements ContentHandler,
but only some of the methods. In the 1.1 version of the class file,
every method from the interface is represented in the bytecode. In the
1.3 version of the class file, only the overridden methods are
represented in the bytecode.
-Nathan
On Fri, Nov 14, 2008 at 10:13 PM, Nathan Beyer <nd...@apache.org> wrote:
> For the most part, the difference is usually only in the class file
> version. 1.1 has a version of 45.3, 1.2 has a version of 46.0 and 1.3
> has a version of 47.0. If the target is set to 1.3, then if the class
> files are loaded by a JRE < 1.3, they'll get a class loading error.
>
> From the detailed comparisons I've done on a few examples, the class
> file differences between a 1.1 target and a 1.3 target are in the
> constant pool. The constant pool of 1.3 class files is generally
> slightly smaller.
>
> -Nathan
>
> On Thu, Nov 13, 2008 at 9:43 PM, Michael Glavassevich
> <mr...@ca.ibm.com> wrote:
>> Hi Nathan,
>>
>> nbeyer@gmail.com wrote on 11/13/2008 09:54:57 AM:
>>
>> <snip/>
>>
>>> Personally, I like to set the source and targets, as the defaults
>>> prior to Java 5 were surprising, at least to me. If you don't set
>>> target=1.3 and use the J2SE 1.3 javac [1], the default bytecode target
>>> is 1.1. If you use a J2SE 1.4 javac [2], the default bytecode target
>>> is 1.2. Since we're discussing dropping JDK 1.2 support, it just
>>> seemed natural to set the bytecode target appropriately.
>>
>> I've never read about the difference between bytecode targeted for 1.1, 1.2
>> and 1.3. Are there specific benefits to setting the target to 1.3?
>>
>>> Note - with Java 5 and Java 6, the javac defaults are now the same
>>> level as the JDK version and the ECJ follows these same defaults
>>>
>>> -Nathan
>>> [1] http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javac.html
>>> [2] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html
>>>
>>> >
>>> >> Anything else?
>>> >
>>> > That's about it.
>>> >
>>> >> +1 (non-binding) for that
>>> >>
>>> >> -Nathan
>>> >
>>> > 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-dev-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-dev-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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
For the most part, the difference is usually only in the class file
version. 1.1 has a version of 45.3, 1.2 has a version of 46.0 and 1.3
has a version of 47.0. If the target is set to 1.3, then if the class
files are loaded by a JRE < 1.3, they'll get a class loading error.
>From the detailed comparisons I've done on a few examples, the class
file differences between a 1.1 target and a 1.3 target are in the
constant pool. The constant pool of 1.3 class files is generally
slightly smaller.
-Nathan
On Thu, Nov 13, 2008 at 9:43 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> Hi Nathan,
>
> nbeyer@gmail.com wrote on 11/13/2008 09:54:57 AM:
>
> <snip/>
>
>> Personally, I like to set the source and targets, as the defaults
>> prior to Java 5 were surprising, at least to me. If you don't set
>> target=1.3 and use the J2SE 1.3 javac [1], the default bytecode target
>> is 1.1. If you use a J2SE 1.4 javac [2], the default bytecode target
>> is 1.2. Since we're discussing dropping JDK 1.2 support, it just
>> seemed natural to set the bytecode target appropriately.
>
> I've never read about the difference between bytecode targeted for 1.1, 1.2
> and 1.3. Are there specific benefits to setting the target to 1.3?
>
>> Note - with Java 5 and Java 6, the javac defaults are now the same
>> level as the JDK version and the ECJ follows these same defaults
>>
>> -Nathan
>> [1] http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javac.html
>> [2] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html
>>
>> >
>> >> Anything else?
>> >
>> > That's about it.
>> >
>> >> +1 (non-binding) for that
>> >>
>> >> -Nathan
>> >
>> > 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-dev-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-dev-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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Nathan,
nbeyer@gmail.com wrote on 11/13/2008 09:54:57 AM:
<snip/>
> Personally, I like to set the source and targets, as the defaults
> prior to Java 5 were surprising, at least to me. If you don't set
> target=1.3 and use the J2SE 1.3 javac [1], the default bytecode target
> is 1.1. If you use a J2SE 1.4 javac [2], the default bytecode target
> is 1.2. Since we're discussing dropping JDK 1.2 support, it just
> seemed natural to set the bytecode target appropriately.
I've never read about the difference between bytecode targeted for 1.1, 1.2
and 1.3. Are there specific benefits to setting the target to 1.3?
> Note - with Java 5 and Java 6, the javac defaults are now the same
> level as the JDK version and the ECJ follows these same defaults
>
> -Nathan
> [1] http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javac.html
> [2] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html
>
> >
> >> Anything else?
> >
> > That's about it.
> >
> >> +1 (non-binding) for that
> >>
> >> -Nathan
> >
> > 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-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
On Wed, Nov 12, 2008 at 10:14 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> Hi Nathan,
>
> nbeyer@gmail.com wrote on 11/12/2008 09:50:52 PM:
>
>> So, to the specific question of dropping support for Java 1.2, are
>> these the specific items that would be enacted.
>>
>> * Update web site, future release notes and any other doc
>
> Yes.
>
>> * Set source and target compile values at 1.3 for javac
>
> The distributed binaries are compiled with Java 1.3 and will continue to be.
> I see no reason to change the build.xml. It's been working fine.
>
> If you compile with source/target=1.3 on a later JDK that does not guarantee
> that it will actually run on JDK 1.3. For example, try compiling this on JDK
> 1.3 and running it, and then compiling it again on JDK 1.4 and running it on
> JDK 1.3:
>
> StringBuffer s = new StringBuffer();
> s.append("foo");
> StringBuffer t = new StringBuffer();
> t.append(s);
> t.append("bar");
> System.err.println(t.toString());
>
> I expect you'll get a NoSuchMethodError for the
> StringBuffer.append(StringBuffer) method which was added in JDK 1.4. The way
> around this is to guard your code against binding to overloaded methods
> introduced in later JDKs by adding casts (e.g. t.append((Object)s)) all over
> the place but who would ever write their code that way. I certainly don't.
Yeah, I know. I've felt that exact pain before. :) I probably should
have added "compile against a 1.3 class library".
Personally, I like to set the source and targets, as the defaults
prior to Java 5 were surprising, at least to me. If you don't set
target=1.3 and use the J2SE 1.3 javac [1], the default bytecode target
is 1.1. If you use a J2SE 1.4 javac [2], the default bytecode target
is 1.2. Since we're discussing dropping JDK 1.2 support, it just
seemed natural to set the bytecode target appropriately.
Note - with Java 5 and Java 6, the javac defaults are now the same
level as the JDK version and the ECJ follows these same defaults
-Nathan
[1] http://java.sun.com/j2se/1.3/docs/tooldocs/win32/javac.html
[2] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html
>
>> Anything else?
>
> That's about it.
>
>> +1 (non-binding) for that
>>
>> -Nathan
>
> 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-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Nathan,
nbeyer@gmail.com wrote on 11/12/2008 09:50:52 PM:
> So, to the specific question of dropping support for Java 1.2, are
> these the specific items that would be enacted.
>
> * Update web site, future release notes and any other doc
Yes.
> * Set source and target compile values at 1.3 for javac
The distributed binaries are compiled with Java 1.3 and will continue to
be. I see no reason to change the build.xml. It's been working fine.
If you compile with source/target=1.3 on a later JDK that does not
guarantee that it will actually run on JDK 1.3. For example, try compiling
this on JDK 1.3 and running it, and then compiling it again on JDK 1.4 and
running it on JDK 1.3:
StringBuffer s = new StringBuffer();
s.append("foo");
StringBuffer t = new StringBuffer();
t.append(s);
t.append("bar");
System.err.println(t.toString());
I expect you'll get a NoSuchMethodError for the
StringBuffer.append(StringBuffer) method which was added in JDK 1.4. The
way around this is to guard your code against binding to overloaded methods
introduced in later JDKs by adding casts (e.g. t.append((Object)s)) all
over the place but who would ever write their code that way. I certainly
don't.
> Anything else?
That's about it.
> +1 (non-binding) for that
>
> -Nathan
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
So, to the specific question of dropping support for Java 1.2, are
these the specific items that would be enacted.
* Update web site, future release notes and any other doc
* Set source and target compile values at 1.3 for javac
Anything else?
+1 (non-binding) for that
-Nathan
On Tue, Nov 11, 2008 at 11:05 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> Xerces doesn't have maintenance releases in the sense that we'll ever have a
> 2.[x].y release after a 2.[x+1].0. The codebase is constantly moving forward
> with new development. It just happens that over some periods of time the
> only changes were bug fixes and minor improvements and if we have a release
> before something significant hits the trunk it ends up being a point release
> instead of the next in the series of 2.x. With the limited resources we have
> on the project (I find myself with less and less time for Xerces each year;
> the other developers have less than that) I'd say -1 to creating and
> maintaining branches ahead of time for hypothetical maintenance releases we
> may never have. I remember someone asking for a branch for JDK 1.1 based
> releases when we dropped support for that level. The need to have such
> releases never materialized. If there were to be a compelling reason to have
> one in the future the tags from the previous Xerces releases will always be
> there and we could create a branch from them if necessary. If it's just for
> the benefit of a handful of users (namely the individuals asking for the
> release) I would expect them to chip in in some way with patches and/or
> testing. If they really need it they'll help. If they're not willing to lift
> a finger then they don't need it badly enough yet.
>
> As for moving past Java 1.3, it's not just the features we could be using
> from later JDKs to improve the code and the user base still on old JDKs
> which would factor into a decision. I would expect a future version of JAXP
> [1] is going to start using generics [2] and APIs only available in Java 5
> and beyond. So it may get to a point where Xerces just has to jump to Java
> 5, 6 or ??? in order to keep up with JAXP. This already happened to JAXB.
> The 2.0 version of that spec is impossible to implement and use without Java
> 5. As some of you know we're currently working on an implementation of XML
> Schema 1.1 and one of the significant features introduced in this new
> version of XML Schema is assertions [3]. For this feature to be of value to
> users you basically need a full-blown XPath 2.0 evaluator. Most likely we're
> going to have to rely on another processor for the XPath support and that
> other library may have a dependency on a later version of Java. So there are
> other things which could push Xerces past Java 1.3 and those may be coming
> sooner than some folks can move to later JDKs.
>
> Anyway, in the immediate future I only recommend that we officially drop
> support for JDK 1.2. So far the folks who've been responding seem to be on
> board with that.
>
> Thanks.
>
> [1] http://wiki.glassfish.java.net/Wiki.jsp?page=JaxpNextDiscussion
> [2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472193
> [3] http://www.w3.org/TR/xmlschema11-1/#cAssertions
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> nbeyer@gmail.com wrote on 11/11/2008 09:46:52 PM:
>
>> I doubt maintenance for the current codebase running on Java 1.3 would
>> be completely removed. I interpreted the original question as aimed at
>> new and future development. I don't want to speak for Michael, but
>> that's the way I read it.
>>
>> -Nathan
>>
>> On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <ho...@visi.com> wrote:
>> > On Tue, 11 Nov 2008 09:36:26 -0500
>> > "David Ezell" <Da...@VERIFONE.com> wrote:
>> >>
>> >> Well, one person's 4 is another person's 3.
>> >>
>> >> We're stuck on 1.3 for the foreseeable future.
>> >>
>> >> So -1 to drop 1.3.
>> >
>> > I partially agree with this. There's no reason 1.3 needs to be dropped
>> > for
>> > the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on
>> > to
>> > 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very
>> > stable. 1.3 and 1.4 users can continue to depend on it. I maintain the
>> > XMLC project, which is currently limited to JDK 1.3 anway. If critical
>> > issues are found in Xerces2, they can be fixed on the Xerces2 branch
>> > where
>> > 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3
>> > and
>> > 1.4 users are in maintenance mode and won't require fancy new features.
>> > All
>> > new feature development can take place on the trunk, which will
>> > represent
>> > the Xerces3 codebase, and will be able to take advantage of all the
>> > latest
>> > JDK features. Who knows, maybe Sun can eventually drop the
>> > com.sun.apache.xerces stuff and migrate back to the original, stable,
>> > Xerces
>> > product once it is not limited by old VM's.
>> >
>> > Jake
>> >
>> >>
>> >> David Ezell
>> >> VeriFone
>> >> Chair, XML Schema WG
>> >>
>> >>> -----Original Message-----
>> >>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
>> >>> Sent:
>> >>> Tuesday, November 11, 2008 5:35 AM
>> >>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
>> >>> Cc: general@xml.apache.org
>> >>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
>> >>> 1.3?
>> >>> 1.4? in the future)
>> >>>
>> >>> > a new infusion of activity and interest.
>> >>>
>> >>> you betcha, most of us would be up in arms!
>> >>>
>> >>> I personally am stuck on 1.4.2 for the foreseeable future.
>> >>>
>> >>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
>> >>>
>> >>>
>> >>> ______________________________
>> >>> Franck Schmidlin
>> >>> Corporate Integration Consultant
>> >>> Northgate Public Services
>> >>>
>> >>> Please consider the environment before printing this e-mail
>> >>>
>> >>>
>> >>> -----Original Message-----
>> >>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
>> >>> Beyer
>> >>> Sent: 11 November 2008 02:25
>> >>> To: j-users@xerces.apache.org
>> >>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
>> >>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
>> >>> 1.3?
>> >>> 1.4? in the future)
>> >>>
>> >>> +1
>> >>>
>> >>> I'd suggest just jumping to Java 5 library, source and target
>> >>> compilation. I think this would give the project a new infusion
>> of activity
>> >>> and interest.
>> >>>
>> >>> -Nathan
>> >>>
>> >>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
>> >>> <mr...@ca.ibm.com> wrote:
>> >>> > 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=ant-dev&m=122596549809889&w=2
>> >>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>> >>> >
>> >>> > Michael Glavassevich
>> >>> > XML Parser Development
>> >>> > IBM Toronto Lab
>> >>> > E-mail: mrglavas@ca.ibm.com
>> >>> > E-mail: mrglavas@apache.org
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
>> >>> For additional commands, e-mail: j-dev-help@xerces.apache.org
>> >>>
>> >>>
>> >>>
>> >>> Scanned for viruses by BlackSpider MailControl
>> >>>
>> >>>
>> >>> This email is sent on behalf of Northgate Information Solutions
>> >>> Limited
>> >>> and its associated companies ("Northgate") and is strictly
>> confidential and
>> >>> intended solely for the addressee(s).
>> >>> If you are not the intended recipient of this email you must: (i) not
>> >>> disclose, copy or distribute its contents to any other person nor use
>> >>> its
>> >>> contents in any way or you may be acting unlawfully; (ii)
>> contact Northgate
>> >>> immediately on +44 (0)1442 232424 quoting the name of the sender and
>> >>> the
>> >>> addressee then delete it from your system.
>> >>>
>> >>> Northgate has taken reasonable precautions to ensure that no viruses
>> >>> are
>> >>> contained in this email, but does not accept any responsibility once
>> >>> this
>> >>> email has been transmitted. You should scan attachments (if any) for
>> >>> viruses.
>> >>>
>> >>> Northgate Information Solutions Limited. Registered in England no.
>> >>> 06442582 - Northgate Information Solutions UK Limited. Registered in
>> >>> England no. 968498 - NorthgateArinso UK Limited. Registered in
>> England no.
>> >>> 1587537 - Moorepay Limited. Registered in England no. 891686 -
>> >>> Northgate Land & Property Solutions Limited - Registered in England
>> >>> no.
>> >>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
>> Estate, Maylands
>> >>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
>> >>> Northgate Managed Services Limited (NI). Registered in Northern
>> >>> Ireland
>> >>> no. NI032979 - LearnServe Limited (NI). Registered in Northern
>> >>> Ireland
>> >>> no. NI043825 Registered Office: Hillview House, 61 Church Road,
>> >>> Newtownabbey, Co. Antrim, BT36 7LQ
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> >>> For additional commands, e-mail: j-users-help@xerces.apache.org
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> >> For additional commands, e-mail: j-users-help@xerces.apache.org
>> >>
>> >>
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> > For additional commands, e-mail: j-users-help@xerces.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Xerces doesn't have maintenance releases in the sense that we'll ever have
a 2.[x].y release after a 2.[x+1].0. The codebase is constantly moving
forward with new development. It just happens that over some periods of
time the only changes were bug fixes and minor improvements and if we have
a release before something significant hits the trunk it ends up being a
point release instead of the next in the series of 2.x. With the limited
resources we have on the project (I find myself with less and less time for
Xerces each year; the other developers have less than that) I'd say -1 to
creating and maintaining branches ahead of time for hypothetical
maintenance releases we may never have. I remember someone asking for a
branch for JDK 1.1 based releases when we dropped support for that level.
The need to have such releases never materialized. If there were to be a
compelling reason to have one in the future the tags from the previous
Xerces releases will always be there and we could create a branch from them
if necessary. If it's just for the benefit of a handful of users (namely
the individuals asking for the release) I would expect them to chip in in
some way with patches and/or testing. If they really need it they'll help.
If they're not willing to lift a finger then they don't need it badly
enough yet.
As for moving past Java 1.3, it's not just the features we could be using
from later JDKs to improve the code and the user base still on old JDKs
which would factor into a decision. I would expect a future version of JAXP
[1] is going to start using generics [2] and APIs only available in Java 5
and beyond. So it may get to a point where Xerces just has to jump to Java
5, 6 or ??? in order to keep up with JAXP. This already happened to JAXB.
The 2.0 version of that spec is impossible to implement and use without
Java 5. As some of you know we're currently working on an implementation of
XML Schema 1.1 and one of the significant features introduced in this new
version of XML Schema is assertions [3]. For this feature to be of value to
users you basically need a full-blown XPath 2.0 evaluator. Most likely
we're going to have to rely on another processor for the XPath support and
that other library may have a dependency on a later version of Java. So
there are other things which could push Xerces past Java 1.3 and those may
be coming sooner than some folks can move to later JDKs.
Anyway, in the immediate future I only recommend that we officially drop
support for JDK 1.2. So far the folks who've been responding seem to be on
board with that.
Thanks.
[1] http://wiki.glassfish.java.net/Wiki.jsp?page=JaxpNextDiscussion
[2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472193
[3] http://www.w3.org/TR/xmlschema11-1/#cAssertions
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
nbeyer@gmail.com wrote on 11/11/2008 09:46:52 PM:
> I doubt maintenance for the current codebase running on Java 1.3 would
> be completely removed. I interpreted the original question as aimed at
> new and future development. I don't want to speak for Michael, but
> that's the way I read it.
>
> -Nathan
>
> On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <ho...@visi.com> wrote:
> > On Tue, 11 Nov 2008 09:36:26 -0500
> > "David Ezell" <Da...@VERIFONE.com> wrote:
> >>
> >> Well, one person's 4 is another person's 3.
> >>
> >> We're stuck on 1.3 for the foreseeable future.
> >>
> >> So -1 to drop 1.3.
> >
> > I partially agree with this. There's no reason 1.3 needs to be dropped
for
> > the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on
to
> > 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very
> > stable. 1.3 and 1.4 users can continue to depend on it. I maintain
the
> > XMLC project, which is currently limited to JDK 1.3 anway. If critical
> > issues are found in Xerces2, they can be fixed on the Xerces2 branch
where
> > 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3
and
> > 1.4 users are in maintenance mode and won't require fancy new features.
All
> > new feature development can take place on the trunk, which will
represent
> > the Xerces3 codebase, and will be able to take advantage of all the
latest
> > JDK features. Who knows, maybe Sun can eventually drop the
> > com.sun.apache.xerces stuff and migrate back to the original, stable,
Xerces
> > product once it is not limited by old VM's.
> >
> > Jake
> >
> >>
> >> David Ezell
> >> VeriFone
> >> Chair, XML Schema WG
> >>
> >>> -----Original Message-----
> >>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
Sent:
> >>> Tuesday, November 11, 2008 5:35 AM
> >>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
> >>> Cc: general@xml.apache.org
> >>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3?
> >>> 1.4? in the future)
> >>>
> >>> > a new infusion of activity and interest.
> >>>
> >>> you betcha, most of us would be up in arms!
> >>>
> >>> I personally am stuck on 1.4.2 for the foreseeable future.
> >>>
> >>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
> >>>
> >>>
> >>> ______________________________
> >>> Franck Schmidlin
> >>> Corporate Integration Consultant
> >>> Northgate Public Services
> >>>
> >>> Please consider the environment before printing this e-mail
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
> >>> Beyer
> >>> Sent: 11 November 2008 02:25
> >>> To: j-users@xerces.apache.org
> >>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
> >>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3?
> >>> 1.4? in the future)
> >>>
> >>> +1
> >>>
> >>> I'd suggest just jumping to Java 5 library, source and target
> >>> compilation. I think this would give the project a new infusion
> of activity
> >>> and interest.
> >>>
> >>> -Nathan
> >>>
> >>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
> >>> <mr...@ca.ibm.com> wrote:
> >>> > 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=ant-dev&m=122596549809889&w=2
> >>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >>> >
> >>> > Michael Glavassevich
> >>> > XML Parser Development
> >>> > IBM Toronto Lab
> >>> > E-mail: mrglavas@ca.ibm.com
> >>> > E-mail: mrglavas@apache.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-dev-help@xerces.apache.org
> >>>
> >>>
> >>>
> >>> Scanned for viruses by BlackSpider MailControl
> >>>
> >>>
> >>> This email is sent on behalf of Northgate Information Solutions
Limited
> >>> and its associated companies ("Northgate") and is strictly
> confidential and
> >>> intended solely for the addressee(s).
> >>> If you are not the intended recipient of this email you must: (i)
not
> >>> disclose, copy or distribute its contents to any other person nor use
its
> >>> contents in any way or you may be acting unlawfully; (ii)
> contact Northgate
> >>> immediately on +44 (0)1442 232424 quoting the name of the sender and
the
> >>> addressee then delete it from your system.
> >>>
> >>> Northgate has taken reasonable precautions to ensure that no viruses
are
> >>> contained in this email, but does not accept any responsibility once
this
> >>> email has been transmitted. You should scan attachments (if any) for
> >>> viruses.
> >>>
> >>> Northgate Information Solutions Limited. Registered in England no.
> >>> 06442582 - Northgate Information Solutions UK Limited. Registered
in
> >>> England no. 968498 - NorthgateArinso UK Limited. Registered in
> England no.
> >>> 1587537 - Moorepay Limited. Registered in England no. 891686 -
> >>> Northgate Land & Property Solutions Limited - Registered in
England no.
> >>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
> Estate, Maylands
> >>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
> >>> Northgate Managed Services Limited (NI). Registered in Northern
Ireland
> >>> no. NI032979 - LearnServe Limited (NI). Registered in Northern
Ireland
> >>> no. NI043825 Registered Office: Hillview House, 61 Church Road,
> >>> Newtownabbey, Co. Antrim, BT36 7LQ
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Xerces doesn't have maintenance releases in the sense that we'll ever have
a 2.[x].y release after a 2.[x+1].0. The codebase is constantly moving
forward with new development. It just happens that over some periods of
time the only changes were bug fixes and minor improvements and if we have
a release before something significant hits the trunk it ends up being a
point release instead of the next in the series of 2.x. With the limited
resources we have on the project (I find myself with less and less time for
Xerces each year; the other developers have less than that) I'd say -1 to
creating and maintaining branches ahead of time for hypothetical
maintenance releases we may never have. I remember someone asking for a
branch for JDK 1.1 based releases when we dropped support for that level.
The need to have such releases never materialized. If there were to be a
compelling reason to have one in the future the tags from the previous
Xerces releases will always be there and we could create a branch from them
if necessary. If it's just for the benefit of a handful of users (namely
the individuals asking for the release) I would expect them to chip in in
some way with patches and/or testing. If they really need it they'll help.
If they're not willing to lift a finger then they don't need it badly
enough yet.
As for moving past Java 1.3, it's not just the features we could be using
from later JDKs to improve the code and the user base still on old JDKs
which would factor into a decision. I would expect a future version of JAXP
[1] is going to start using generics [2] and APIs only available in Java 5
and beyond. So it may get to a point where Xerces just has to jump to Java
5, 6 or ??? in order to keep up with JAXP. This already happened to JAXB.
The 2.0 version of that spec is impossible to implement and use without
Java 5. As some of you know we're currently working on an implementation of
XML Schema 1.1 and one of the significant features introduced in this new
version of XML Schema is assertions [3]. For this feature to be of value to
users you basically need a full-blown XPath 2.0 evaluator. Most likely
we're going to have to rely on another processor for the XPath support and
that other library may have a dependency on a later version of Java. So
there are other things which could push Xerces past Java 1.3 and those may
be coming sooner than some folks can move to later JDKs.
Anyway, in the immediate future I only recommend that we officially drop
support for JDK 1.2. So far the folks who've been responding seem to be on
board with that.
Thanks.
[1] http://wiki.glassfish.java.net/Wiki.jsp?page=JaxpNextDiscussion
[2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472193
[3] http://www.w3.org/TR/xmlschema11-1/#cAssertions
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
nbeyer@gmail.com wrote on 11/11/2008 09:46:52 PM:
> I doubt maintenance for the current codebase running on Java 1.3 would
> be completely removed. I interpreted the original question as aimed at
> new and future development. I don't want to speak for Michael, but
> that's the way I read it.
>
> -Nathan
>
> On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <ho...@visi.com> wrote:
> > On Tue, 11 Nov 2008 09:36:26 -0500
> > "David Ezell" <Da...@VERIFONE.com> wrote:
> >>
> >> Well, one person's 4 is another person's 3.
> >>
> >> We're stuck on 1.3 for the foreseeable future.
> >>
> >> So -1 to drop 1.3.
> >
> > I partially agree with this. There's no reason 1.3 needs to be dropped
for
> > the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on
to
> > 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very
> > stable. 1.3 and 1.4 users can continue to depend on it. I maintain
the
> > XMLC project, which is currently limited to JDK 1.3 anway. If critical
> > issues are found in Xerces2, they can be fixed on the Xerces2 branch
where
> > 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3
and
> > 1.4 users are in maintenance mode and won't require fancy new features.
All
> > new feature development can take place on the trunk, which will
represent
> > the Xerces3 codebase, and will be able to take advantage of all the
latest
> > JDK features. Who knows, maybe Sun can eventually drop the
> > com.sun.apache.xerces stuff and migrate back to the original, stable,
Xerces
> > product once it is not limited by old VM's.
> >
> > Jake
> >
> >>
> >> David Ezell
> >> VeriFone
> >> Chair, XML Schema WG
> >>
> >>> -----Original Message-----
> >>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
Sent:
> >>> Tuesday, November 11, 2008 5:35 AM
> >>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
> >>> Cc: general@xml.apache.org
> >>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3?
> >>> 1.4? in the future)
> >>>
> >>> > a new infusion of activity and interest.
> >>>
> >>> you betcha, most of us would be up in arms!
> >>>
> >>> I personally am stuck on 1.4.2 for the foreseeable future.
> >>>
> >>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
> >>>
> >>>
> >>> ______________________________
> >>> Franck Schmidlin
> >>> Corporate Integration Consultant
> >>> Northgate Public Services
> >>>
> >>> Please consider the environment before printing this e-mail
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
> >>> Beyer
> >>> Sent: 11 November 2008 02:25
> >>> To: j-users@xerces.apache.org
> >>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
> >>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3?
> >>> 1.4? in the future)
> >>>
> >>> +1
> >>>
> >>> I'd suggest just jumping to Java 5 library, source and target
> >>> compilation. I think this would give the project a new infusion
> of activity
> >>> and interest.
> >>>
> >>> -Nathan
> >>>
> >>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
> >>> <mr...@ca.ibm.com> wrote:
> >>> > 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=ant-dev&m=122596549809889&w=2
> >>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >>> >
> >>> > Michael Glavassevich
> >>> > XML Parser Development
> >>> > IBM Toronto Lab
> >>> > E-mail: mrglavas@ca.ibm.com
> >>> > E-mail: mrglavas@apache.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-dev-help@xerces.apache.org
> >>>
> >>>
> >>>
> >>> Scanned for viruses by BlackSpider MailControl
> >>>
> >>>
> >>> This email is sent on behalf of Northgate Information Solutions
Limited
> >>> and its associated companies ("Northgate") and is strictly
> confidential and
> >>> intended solely for the addressee(s).
> >>> If you are not the intended recipient of this email you must: (i)
not
> >>> disclose, copy or distribute its contents to any other person nor use
its
> >>> contents in any way or you may be acting unlawfully; (ii)
> contact Northgate
> >>> immediately on +44 (0)1442 232424 quoting the name of the sender and
the
> >>> addressee then delete it from your system.
> >>>
> >>> Northgate has taken reasonable precautions to ensure that no viruses
are
> >>> contained in this email, but does not accept any responsibility once
this
> >>> email has been transmitted. You should scan attachments (if any) for
> >>> viruses.
> >>>
> >>> Northgate Information Solutions Limited. Registered in England no.
> >>> 06442582 - Northgate Information Solutions UK Limited. Registered
in
> >>> England no. 968498 - NorthgateArinso UK Limited. Registered in
> England no.
> >>> 1587537 - Moorepay Limited. Registered in England no. 891686 -
> >>> Northgate Land & Property Solutions Limited - Registered in
England no.
> >>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
> Estate, Maylands
> >>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
> >>> Northgate Managed Services Limited (NI). Registered in Northern
Ireland
> >>> no. NI032979 - LearnServe Limited (NI). Registered in Northern
Ireland
> >>> no. NI043825 Registered Office: Hillview House, 61 Church Road,
> >>> Newtownabbey, Co. Antrim, BT36 7LQ
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Xerces doesn't have maintenance releases in the sense that we'll ever have
a 2.[x].y release after a 2.[x+1].0. The codebase is constantly moving
forward with new development. It just happens that over some periods of
time the only changes were bug fixes and minor improvements and if we have
a release before something significant hits the trunk it ends up being a
point release instead of the next in the series of 2.x. With the limited
resources we have on the project (I find myself with less and less time for
Xerces each year; the other developers have less than that) I'd say -1 to
creating and maintaining branches ahead of time for hypothetical
maintenance releases we may never have. I remember someone asking for a
branch for JDK 1.1 based releases when we dropped support for that level.
The need to have such releases never materialized. If there were to be a
compelling reason to have one in the future the tags from the previous
Xerces releases will always be there and we could create a branch from them
if necessary. If it's just for the benefit of a handful of users (namely
the individuals asking for the release) I would expect them to chip in in
some way with patches and/or testing. If they really need it they'll help.
If they're not willing to lift a finger then they don't need it badly
enough yet.
As for moving past Java 1.3, it's not just the features we could be using
from later JDKs to improve the code and the user base still on old JDKs
which would factor into a decision. I would expect a future version of JAXP
[1] is going to start using generics [2] and APIs only available in Java 5
and beyond. So it may get to a point where Xerces just has to jump to Java
5, 6 or ??? in order to keep up with JAXP. This already happened to JAXB.
The 2.0 version of that spec is impossible to implement and use without
Java 5. As some of you know we're currently working on an implementation of
XML Schema 1.1 and one of the significant features introduced in this new
version of XML Schema is assertions [3]. For this feature to be of value to
users you basically need a full-blown XPath 2.0 evaluator. Most likely
we're going to have to rely on another processor for the XPath support and
that other library may have a dependency on a later version of Java. So
there are other things which could push Xerces past Java 1.3 and those may
be coming sooner than some folks can move to later JDKs.
Anyway, in the immediate future I only recommend that we officially drop
support for JDK 1.2. So far the folks who've been responding seem to be on
board with that.
Thanks.
[1] http://wiki.glassfish.java.net/Wiki.jsp?page=JaxpNextDiscussion
[2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6472193
[3] http://www.w3.org/TR/xmlschema11-1/#cAssertions
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
nbeyer@gmail.com wrote on 11/11/2008 09:46:52 PM:
> I doubt maintenance for the current codebase running on Java 1.3 would
> be completely removed. I interpreted the original question as aimed at
> new and future development. I don't want to speak for Michael, but
> that's the way I read it.
>
> -Nathan
>
> On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <ho...@visi.com> wrote:
> > On Tue, 11 Nov 2008 09:36:26 -0500
> > "David Ezell" <Da...@VERIFONE.com> wrote:
> >>
> >> Well, one person's 4 is another person's 3.
> >>
> >> We're stuck on 1.3 for the foreseeable future.
> >>
> >> So -1 to drop 1.3.
> >
> > I partially agree with this. There's no reason 1.3 needs to be dropped
for
> > the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on
to
> > 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very
> > stable. 1.3 and 1.4 users can continue to depend on it. I maintain
the
> > XMLC project, which is currently limited to JDK 1.3 anway. If critical
> > issues are found in Xerces2, they can be fixed on the Xerces2 branch
where
> > 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3
and
> > 1.4 users are in maintenance mode and won't require fancy new features.
All
> > new feature development can take place on the trunk, which will
represent
> > the Xerces3 codebase, and will be able to take advantage of all the
latest
> > JDK features. Who knows, maybe Sun can eventually drop the
> > com.sun.apache.xerces stuff and migrate back to the original, stable,
Xerces
> > product once it is not limited by old VM's.
> >
> > Jake
> >
> >>
> >> David Ezell
> >> VeriFone
> >> Chair, XML Schema WG
> >>
> >>> -----Original Message-----
> >>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
Sent:
> >>> Tuesday, November 11, 2008 5:35 AM
> >>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
> >>> Cc: general@xml.apache.org
> >>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3?
> >>> 1.4? in the future)
> >>>
> >>> > a new infusion of activity and interest.
> >>>
> >>> you betcha, most of us would be up in arms!
> >>>
> >>> I personally am stuck on 1.4.2 for the foreseeable future.
> >>>
> >>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
> >>>
> >>>
> >>> ______________________________
> >>> Franck Schmidlin
> >>> Corporate Integration Consultant
> >>> Northgate Public Services
> >>>
> >>> Please consider the environment before printing this e-mail
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
> >>> Beyer
> >>> Sent: 11 November 2008 02:25
> >>> To: j-users@xerces.apache.org
> >>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
> >>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3?
> >>> 1.4? in the future)
> >>>
> >>> +1
> >>>
> >>> I'd suggest just jumping to Java 5 library, source and target
> >>> compilation. I think this would give the project a new infusion
> of activity
> >>> and interest.
> >>>
> >>> -Nathan
> >>>
> >>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
> >>> <mr...@ca.ibm.com> wrote:
> >>> > 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=ant-dev&m=122596549809889&w=2
> >>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >>> >
> >>> > Michael Glavassevich
> >>> > XML Parser Development
> >>> > IBM Toronto Lab
> >>> > E-mail: mrglavas@ca.ibm.com
> >>> > E-mail: mrglavas@apache.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-dev-help@xerces.apache.org
> >>>
> >>>
> >>>
> >>> Scanned for viruses by BlackSpider MailControl
> >>>
> >>>
> >>> This email is sent on behalf of Northgate Information Solutions
Limited
> >>> and its associated companies ("Northgate") and is strictly
> confidential and
> >>> intended solely for the addressee(s).
> >>> If you are not the intended recipient of this email you must: (i)
not
> >>> disclose, copy or distribute its contents to any other person nor use
its
> >>> contents in any way or you may be acting unlawfully; (ii)
> contact Northgate
> >>> immediately on +44 (0)1442 232424 quoting the name of the sender and
the
> >>> addressee then delete it from your system.
> >>>
> >>> Northgate has taken reasonable precautions to ensure that no viruses
are
> >>> contained in this email, but does not accept any responsibility once
this
> >>> email has been transmitted. You should scan attachments (if any) for
> >>> viruses.
> >>>
> >>> Northgate Information Solutions Limited. Registered in England no.
> >>> 06442582 - Northgate Information Solutions UK Limited. Registered
in
> >>> England no. 968498 - NorthgateArinso UK Limited. Registered in
> England no.
> >>> 1587537 - Moorepay Limited. Registered in England no. 891686 -
> >>> Northgate Land & Property Solutions Limited - Registered in
England no.
> >>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
> Estate, Maylands
> >>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
> >>> Northgate Managed Services Limited (NI). Registered in Northern
Ireland
> >>> no. NI032979 - LearnServe Limited (NI). Registered in Northern
Ireland
> >>> no. NI043825 Registered Office: Hillview House, 61 Church Road,
> >>> Newtownabbey, Co. Antrim, BT36 7LQ
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >>> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >> For additional commands, e-mail: j-users-help@xerces.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
I doubt maintenance for the current codebase running on Java 1.3 would
be completely removed. I interpreted the original question as aimed at
new and future development. I don't want to speak for Michael, but
that's the way I read it.
-Nathan
On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <ho...@visi.com> wrote:
> On Tue, 11 Nov 2008 09:36:26 -0500
> "David Ezell" <Da...@VERIFONE.com> wrote:
>>
>> Well, one person's 4 is another person's 3.
>>
>> We're stuck on 1.3 for the foreseeable future.
>>
>> So -1 to drop 1.3.
>
> I partially agree with this. There's no reason 1.3 needs to be dropped for
> the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on to
> 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very
> stable. 1.3 and 1.4 users can continue to depend on it. I maintain the
> XMLC project, which is currently limited to JDK 1.3 anway. If critical
> issues are found in Xerces2, they can be fixed on the Xerces2 branch where
> 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3 and
> 1.4 users are in maintenance mode and won't require fancy new features. All
> new feature development can take place on the trunk, which will represent
> the Xerces3 codebase, and will be able to take advantage of all the latest
> JDK features. Who knows, maybe Sun can eventually drop the
> com.sun.apache.xerces stuff and migrate back to the original, stable, Xerces
> product once it is not limited by old VM's.
>
> Jake
>
>>
>> David Ezell
>> VeriFone
>> Chair, XML Schema WG
>>
>>> -----Original Message-----
>>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com] Sent:
>>> Tuesday, November 11, 2008 5:35 AM
>>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
>>> Cc: general@xml.apache.org
>>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3?
>>> 1.4? in the future)
>>>
>>> > a new infusion of activity and interest.
>>>
>>> you betcha, most of us would be up in arms!
>>>
>>> I personally am stuck on 1.4.2 for the foreseeable future.
>>>
>>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
>>>
>>>
>>> ______________________________
>>> Franck Schmidlin
>>> Corporate Integration Consultant
>>> Northgate Public Services
>>>
>>> Please consider the environment before printing this e-mail
>>>
>>>
>>> -----Original Message-----
>>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
>>> Beyer
>>> Sent: 11 November 2008 02:25
>>> To: j-users@xerces.apache.org
>>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
>>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3?
>>> 1.4? in the future)
>>>
>>> +1
>>>
>>> I'd suggest just jumping to Java 5 library, source and target
>>> compilation. I think this would give the project a new infusion of activity
>>> and interest.
>>>
>>> -Nathan
>>>
>>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
>>> <mr...@ca.ibm.com> wrote:
>>> > 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=ant-dev&m=122596549809889&w=2
>>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>>> >
>>> > Michael Glavassevich
>>> > XML Parser Development
>>> > IBM Toronto Lab
>>> > E-mail: mrglavas@ca.ibm.com
>>> > E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-dev-help@xerces.apache.org
>>>
>>>
>>>
>>> Scanned for viruses by BlackSpider MailControl
>>>
>>>
>>> This email is sent on behalf of Northgate Information Solutions Limited
>>> and its associated companies ("Northgate") and is strictly confidential and
>>> intended solely for the addressee(s).
>>> If you are not the intended recipient of this email you must: (i) not
>>> disclose, copy or distribute its contents to any other person nor use its
>>> contents in any way or you may be acting unlawfully; (ii) contact Northgate
>>> immediately on +44 (0)1442 232424 quoting the name of the sender and the
>>> addressee then delete it from your system.
>>>
>>> Northgate has taken reasonable precautions to ensure that no viruses are
>>> contained in this email, but does not accept any responsibility once this
>>> email has been transmitted. You should scan attachments (if any) for
>>> viruses.
>>>
>>> Northgate Information Solutions Limited. Registered in England no.
>>> 06442582 - Northgate Information Solutions UK Limited. Registered in
>>> England no. 968498 - NorthgateArinso UK Limited. Registered in England no.
>>> 1587537 - Moorepay Limited. Registered in England no. 891686 -
>>> Northgate Land & Property Solutions Limited - Registered in England no.
>>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding Estate, Maylands
>>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
>>> Northgate Managed Services Limited (NI). Registered in Northern Ireland
>>> no. NI032979 - LearnServe Limited (NI). Registered in Northern Ireland
>>> no. NI043825 Registered Office: Hillview House, 61 Church Road,
>>> Newtownabbey, Co. Antrim, BT36 7LQ
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
I doubt maintenance for the current codebase running on Java 1.3 would
be completely removed. I interpreted the original question as aimed at
new and future development. I don't want to speak for Michael, but
that's the way I read it.
-Nathan
On Tue, Nov 11, 2008 at 9:08 AM, Jacob Kjome <ho...@visi.com> wrote:
> On Tue, 11 Nov 2008 09:36:26 -0500
> "David Ezell" <Da...@VERIFONE.com> wrote:
>>
>> Well, one person's 4 is another person's 3.
>>
>> We're stuck on 1.3 for the foreseeable future.
>>
>> So -1 to drop 1.3.
>
> I partially agree with this. There's no reason 1.3 needs to be dropped for
> the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on to
> 3.x development which would be 1.5+ (or even 1.6+). Xerces2 is very
> stable. 1.3 and 1.4 users can continue to depend on it. I maintain the
> XMLC project, which is currently limited to JDK 1.3 anway. If critical
> issues are found in Xerces2, they can be fixed on the Xerces2 branch where
> 1.3 and 1.4 users can benefit. Of course, we can also expect that 1.3 and
> 1.4 users are in maintenance mode and won't require fancy new features. All
> new feature development can take place on the trunk, which will represent
> the Xerces3 codebase, and will be able to take advantage of all the latest
> JDK features. Who knows, maybe Sun can eventually drop the
> com.sun.apache.xerces stuff and migrate back to the original, stable, Xerces
> product once it is not limited by old VM's.
>
> Jake
>
>>
>> David Ezell
>> VeriFone
>> Chair, XML Schema WG
>>
>>> -----Original Message-----
>>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com] Sent:
>>> Tuesday, November 11, 2008 5:35 AM
>>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
>>> Cc: general@xml.apache.org
>>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3?
>>> 1.4? in the future)
>>>
>>> > a new infusion of activity and interest.
>>>
>>> you betcha, most of us would be up in arms!
>>>
>>> I personally am stuck on 1.4.2 for the foreseeable future.
>>>
>>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
>>>
>>>
>>> ______________________________
>>> Franck Schmidlin
>>> Corporate Integration Consultant
>>> Northgate Public Services
>>>
>>> Please consider the environment before printing this e-mail
>>>
>>>
>>> -----Original Message-----
>>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
>>> Beyer
>>> Sent: 11 November 2008 02:25
>>> To: j-users@xerces.apache.org
>>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
>>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3?
>>> 1.4? in the future)
>>>
>>> +1
>>>
>>> I'd suggest just jumping to Java 5 library, source and target
>>> compilation. I think this would give the project a new infusion of activity
>>> and interest.
>>>
>>> -Nathan
>>>
>>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
>>> <mr...@ca.ibm.com> wrote:
>>> > 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=ant-dev&m=122596549809889&w=2
>>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>>> >
>>> > Michael Glavassevich
>>> > XML Parser Development
>>> > IBM Toronto Lab
>>> > E-mail: mrglavas@ca.ibm.com
>>> > E-mail: mrglavas@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-dev-help@xerces.apache.org
>>>
>>>
>>>
>>> Scanned for viruses by BlackSpider MailControl
>>>
>>>
>>> This email is sent on behalf of Northgate Information Solutions Limited
>>> and its associated companies ("Northgate") and is strictly confidential and
>>> intended solely for the addressee(s).
>>> If you are not the intended recipient of this email you must: (i) not
>>> disclose, copy or distribute its contents to any other person nor use its
>>> contents in any way or you may be acting unlawfully; (ii) contact Northgate
>>> immediately on +44 (0)1442 232424 quoting the name of the sender and the
>>> addressee then delete it from your system.
>>>
>>> Northgate has taken reasonable precautions to ensure that no viruses are
>>> contained in this email, but does not accept any responsibility once this
>>> email has been transmitted. You should scan attachments (if any) for
>>> viruses.
>>>
>>> Northgate Information Solutions Limited. Registered in England no.
>>> 06442582 - Northgate Information Solutions UK Limited. Registered in
>>> England no. 968498 - NorthgateArinso UK Limited. Registered in England no.
>>> 1587537 - Moorepay Limited. Registered in England no. 891686 -
>>> Northgate Land & Property Solutions Limited - Registered in England no.
>>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding Estate, Maylands
>>> Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
>>> Northgate Managed Services Limited (NI). Registered in Northern Ireland
>>> no. NI032979 - LearnServe Limited (NI). Registered in Northern Ireland
>>> no. NI043825 Registered Office: Hillview House, 61 Church Road,
>>> Newtownabbey, Co. Antrim, BT36 7LQ
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Jacob Kjome <ho...@visi.com>.
On Tue, 11 Nov 2008 09:36:26 -0500
"David Ezell" <Da...@VERIFONE.com> wrote:
> Well, one person's 4 is another person's 3.
>
> We're stuck on 1.3 for the foreseeable future.
>
> So -1 to drop 1.3.
I partially agree with this. There's no reason 1.3 needs to be dropped for
the current 2.x.x codebase. Why not maintain 2.x.x at 1.3 and move on to 3.x
development which would be 1.5+ (or even 1.6+). Xerces2 is very stable. 1.3
and 1.4 users can continue to depend on it. I maintain the XMLC project,
which is currently limited to JDK 1.3 anway. If critical issues are found in
Xerces2, they can be fixed on the Xerces2 branch where 1.3 and 1.4 users can
benefit. Of course, we can also expect that 1.3 and 1.4 users are in
maintenance mode and won't require fancy new features. All new feature
development can take place on the trunk, which will represent the Xerces3
codebase, and will be able to take advantage of all the latest JDK features.Â
Who knows, maybe Sun can eventually drop the com.sun.apache.xerces stuff and
migrate back to the original, stable, Xerces product once it is not limited by
old VM's.
Jake
>
> David Ezell
> VeriFone
> Chair, XML Schema WG
>
>> -----Original Message-----
>> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
>> Sent: Tuesday, November 11, 2008 5:35 AM
>> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
>> Cc: general@xml.apache.org
>> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and
>> possibly JDK 1.3? 1.4? in the future)
>>
>> > a new infusion of activity and interest.
>>
>> you betcha, most of us would be up in arms!
>>
>> I personally am stuck on 1.4.2 for the foreseeable future.
>>
>> So +1 to drop 1.2/3 support, but let's not get too drastic please.
>>
>>
>> ______________________________
>> Franck Schmidlin
>> Corporate Integration Consultant
>> Northgate Public Services
>>
>> Please consider the environment before printing this e-mail
>>
>>
>> -----Original Message-----
>> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of
>> Nathan Beyer
>> Sent: 11 November 2008 02:25
>> To: j-users@xerces.apache.org
>> Cc: j-dev@xerces.apache.org; general@xml.apache.org
>> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and
>> possibly JDK 1.3? 1.4? in the future)
>>
>> +1
>>
>> I'd suggest just jumping to Java 5 library, source and target
>> compilation. I think this would give the project a new
>> infusion of activity and interest.
>>
>> -Nathan
>>
>> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
>> <mr...@ca.ibm.com> wrote:
>> > 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=ant-dev&m=122596549809889&w=2
>> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>> >
>> > Michael Glavassevich
>> > XML Parser Development
>> > IBM Toronto Lab
>> > E-mail: mrglavas@ca.ibm.com
>> > E-mail: mrglavas@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-dev-help@xerces.apache.org
>>
>>
>>
>> Scanned for viruses by BlackSpider MailControl
>>
>>
>> This email is sent on behalf of Northgate Information
>> Solutions Limited and its associated companies ("Northgate")
>> and is strictly confidential and intended solely for the
>> addressee(s).
>>
>> If you are not the intended recipient of this email you
>> must: (i) not disclose, copy or distribute its contents to
>> any other person nor use its contents in any way or you may
>> be acting unlawfully; (ii) contact Northgate immediately on
>> +44 (0)1442 232424 quoting the name of the sender and the
>> addressee then delete it from your system.
>>
>> Northgate has taken reasonable precautions to ensure that no
>> viruses are contained in this email, but does not accept any
>> responsibility once this email has been transmitted. You
>> should scan attachments (if any) for viruses.
>>
>> Northgate Information Solutions Limited. Registered in
>> England no. 06442582 - Northgate Information Solutions UK
>> Limited. Registered in England no. 968498 - NorthgateArinso
>> UK Limited. Registered in England no. 1587537 - Moorepay
>> Limited. Registered in England no. 891686 - Northgate Land
>> & Property Solutions Limited - Registered in England no.
>> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
>> Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
>>
>> Northgate Managed Services Limited (NI). Registered in
>> Northern Ireland no. NI032979 - LearnServe Limited (NI).
>> Registered in Northern Ireland no. NI043825 Registered
>> Office: Hillview House, 61 Church Road, Newtownabbey, Co.
>> Antrim, BT36 7LQ
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by David Ezell <Da...@VERIFONE.com>.
Well, one person's 4 is another person's 3.
We're stuck on 1.3 for the foreseeable future.
So -1 to drop 1.3.
David Ezell
VeriFone
Chair, XML Schema WG
> -----Original Message-----
> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
> Sent: Tuesday, November 11, 2008 5:35 AM
> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
> Cc: general@xml.apache.org
> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and
> possibly JDK 1.3? 1.4? in the future)
>
> > a new infusion of activity and interest.
>
> you betcha, most of us would be up in arms!
>
> I personally am stuck on 1.4.2 for the foreseeable future.
>
> So +1 to drop 1.2/3 support, but let's not get too drastic please.
>
>
> ______________________________
> Franck Schmidlin
> Corporate Integration Consultant
> Northgate Public Services
>
> Please consider the environment before printing this e-mail
>
>
> -----Original Message-----
> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of
> Nathan Beyer
> Sent: 11 November 2008 02:25
> To: j-users@xerces.apache.org
> Cc: j-dev@xerces.apache.org; general@xml.apache.org
> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and
> possibly JDK 1.3? 1.4? in the future)
>
> +1
>
> I'd suggest just jumping to Java 5 library, source and target
> compilation. I think this would give the project a new
> infusion of activity and interest.
>
> -Nathan
>
> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
> <mr...@ca.ibm.com> wrote:
> > 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=ant-dev&m=122596549809889&w=2
> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
>
>
>
> Scanned for viruses by BlackSpider MailControl
>
>
> This email is sent on behalf of Northgate Information
> Solutions Limited and its associated companies ("Northgate")
> and is strictly confidential and intended solely for the
> addressee(s).
>
> If you are not the intended recipient of this email you
> must: (i) not disclose, copy or distribute its contents to
> any other person nor use its contents in any way or you may
> be acting unlawfully; (ii) contact Northgate immediately on
> +44 (0)1442 232424 quoting the name of the sender and the
> addressee then delete it from your system.
>
> Northgate has taken reasonable precautions to ensure that no
> viruses are contained in this email, but does not accept any
> responsibility once this email has been transmitted. You
> should scan attachments (if any) for viruses.
>
> Northgate Information Solutions Limited. Registered in
> England no. 06442582 - Northgate Information Solutions UK
> Limited. Registered in England no. 968498 - NorthgateArinso
> UK Limited. Registered in England no. 1587537 - Moorepay
> Limited. Registered in England no. 891686 - Northgate Land
> & Property Solutions Limited - Registered in England no.
> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
> Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
>
> Northgate Managed Services Limited (NI). Registered in
> Northern Ireland no. NI032979 - LearnServe Limited (NI).
> Registered in Northern Ireland no. NI043825 Registered
> Office: Hillview House, 61 Church Road, Newtownabbey, Co.
> Antrim, BT36 7LQ
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by David Ezell <Da...@VERIFONE.com>.
Well, one person's 4 is another person's 3.
We're stuck on 1.3 for the foreseeable future.
So -1 to drop 1.3.
David Ezell
VeriFone
Chair, XML Schema WG
> -----Original Message-----
> From: Schmidlin, Franck [mailto:Franck.Schmidlin@northgate-is.com]
> Sent: Tuesday, November 11, 2008 5:35 AM
> To: j-dev@xerces.apache.org; j-users@xerces.apache.org
> Cc: general@xml.apache.org
> Subject: RE: Dropping JDK 1.2 support for Xerces-J (and
> possibly JDK 1.3? 1.4? in the future)
>
> > a new infusion of activity and interest.
>
> you betcha, most of us would be up in arms!
>
> I personally am stuck on 1.4.2 for the foreseeable future.
>
> So +1 to drop 1.2/3 support, but let's not get too drastic please.
>
>
> ______________________________
> Franck Schmidlin
> Corporate Integration Consultant
> Northgate Public Services
>
> Please consider the environment before printing this e-mail
>
>
> -----Original Message-----
> From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of
> Nathan Beyer
> Sent: 11 November 2008 02:25
> To: j-users@xerces.apache.org
> Cc: j-dev@xerces.apache.org; general@xml.apache.org
> Subject: Re: Dropping JDK 1.2 support for Xerces-J (and
> possibly JDK 1.3? 1.4? in the future)
>
> +1
>
> I'd suggest just jumping to Java 5 library, source and target
> compilation. I think this would give the project a new
> infusion of activity and interest.
>
> -Nathan
>
> On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
> <mr...@ca.ibm.com> wrote:
> > 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=ant-dev&m=122596549809889&w=2
> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
>
>
>
> Scanned for viruses by BlackSpider MailControl
>
>
> This email is sent on behalf of Northgate Information
> Solutions Limited and its associated companies ("Northgate")
> and is strictly confidential and intended solely for the
> addressee(s).
>
> If you are not the intended recipient of this email you
> must: (i) not disclose, copy or distribute its contents to
> any other person nor use its contents in any way or you may
> be acting unlawfully; (ii) contact Northgate immediately on
> +44 (0)1442 232424 quoting the name of the sender and the
> addressee then delete it from your system.
>
> Northgate has taken reasonable precautions to ensure that no
> viruses are contained in this email, but does not accept any
> responsibility once this email has been transmitted. You
> should scan attachments (if any) for viruses.
>
> Northgate Information Solutions Limited. Registered in
> England no. 06442582 - Northgate Information Solutions UK
> Limited. Registered in England no. 968498 - NorthgateArinso
> UK Limited. Registered in England no. 1587537 - Moorepay
> Limited. Registered in England no. 891686 - Northgate Land
> & Property Solutions Limited - Registered in England no.
> 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding
> Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
>
> Northgate Managed Services Limited (NI). Registered in
> Northern Ireland no. NI032979 - LearnServe Limited (NI).
> Registered in Northern Ireland no. NI043825 Registered
> Office: Hillview House, 61 Church Road, Newtownabbey, Co.
> Antrim, BT36 7LQ
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by "Schmidlin, Franck" <Fr...@northgate-is.com>.
> a new infusion of activity and interest.
you betcha, most of us would be up in arms!
I personally am stuck on 1.4.2 for the foreseeable future.
So +1 to drop 1.2/3 support, but let's not get too drastic please.
______________________________
Franck Schmidlin
Corporate Integration Consultant
Northgate Public Services
Please consider the environment before printing this e-mail
-----Original Message-----
From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
Beyer
Sent: 11 November 2008 02:25
To: j-users@xerces.apache.org
Cc: j-dev@xerces.apache.org; general@xml.apache.org
Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3? 1.4? in the future)
+1
I'd suggest just jumping to Java 5 library, source and target
compilation. I think this would give the project a new infusion of
activity and interest.
-Nathan
On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Scanned for viruses by BlackSpider MailControl
This email is sent on behalf of Northgate Information Solutions Limited and its associated companies ("Northgate") and is strictly confidential and intended solely for the addressee(s).
If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully; (ii) contact Northgate immediately on +44 (0)1442 232424 quoting the name of the sender and the addressee then delete it from your system.
Northgate has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted. You should scan attachments (if any) for viruses.
Northgate Information Solutions Limited. Registered in England no. 06442582 - Northgate Information Solutions UK Limited. Registered in England no. 968498 - NorthgateArinso UK Limited. Registered in England no. 1587537 - Moorepay Limited. Registered in England no. 891686 - Northgate Land & Property Solutions Limited - Registered in England no. 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
Northgate Managed Services Limited (NI). Registered in Northern Ireland no. NI032979 - LearnServe Limited (NI). Registered in Northern Ireland no. NI043825 Registered Office: Hillview House, 61 Church Road, Newtownabbey, Co. Antrim, BT36 7LQ
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by "Schmidlin, Franck" <Fr...@northgate-is.com>.
> a new infusion of activity and interest.
you betcha, most of us would be up in arms!
I personally am stuck on 1.4.2 for the foreseeable future.
So +1 to drop 1.2/3 support, but let's not get too drastic please.
______________________________
Franck Schmidlin
Corporate Integration Consultant
Northgate Public Services
Please consider the environment before printing this e-mail
-----Original Message-----
From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
Beyer
Sent: 11 November 2008 02:25
To: j-users@xerces.apache.org
Cc: j-dev@xerces.apache.org; general@xml.apache.org
Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3? 1.4? in the future)
+1
I'd suggest just jumping to Java 5 library, source and target
compilation. I think this would give the project a new infusion of
activity and interest.
-Nathan
On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Scanned for viruses by BlackSpider MailControl
This email is sent on behalf of Northgate Information Solutions Limited and its associated companies ("Northgate") and is strictly confidential and intended solely for the addressee(s).
If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully; (ii) contact Northgate immediately on +44 (0)1442 232424 quoting the name of the sender and the addressee then delete it from your system.
Northgate has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted. You should scan attachments (if any) for viruses.
Northgate Information Solutions Limited. Registered in England no. 06442582 - Northgate Information Solutions UK Limited. Registered in England no. 968498 - NorthgateArinso UK Limited. Registered in England no. 1587537 - Moorepay Limited. Registered in England no. 891686 - Northgate Land & Property Solutions Limited - Registered in England no. 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
Northgate Managed Services Limited (NI). Registered in Northern Ireland no. NI032979 - LearnServe Limited (NI). Registered in Northern Ireland no. NI043825 Registered Office: Hillview House, 61 Church Road, Newtownabbey, Co. Antrim, BT36 7LQ
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by "Schmidlin, Franck" <Fr...@northgate-is.com>.
> a new infusion of activity and interest.
you betcha, most of us would be up in arms!
I personally am stuck on 1.4.2 for the foreseeable future.
So +1 to drop 1.2/3 support, but let's not get too drastic please.
______________________________
Franck Schmidlin
Corporate Integration Consultant
Northgate Public Services
Please consider the environment before printing this e-mail
-----Original Message-----
From: nbeyer@gmail.com [mailto:nbeyer@gmail.com] On Behalf Of Nathan
Beyer
Sent: 11 November 2008 02:25
To: j-users@xerces.apache.org
Cc: j-dev@xerces.apache.org; general@xml.apache.org
Subject: Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK
1.3? 1.4? in the future)
+1
I'd suggest just jumping to Java 5 library, source and target
compilation. I think this would give the project a new infusion of
activity and interest.
-Nathan
On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Scanned for viruses by BlackSpider MailControl
This email is sent on behalf of Northgate Information Solutions Limited and its associated companies ("Northgate") and is strictly confidential and intended solely for the addressee(s).
If you are not the intended recipient of this email you must: (i) not disclose, copy or distribute its contents to any other person nor use its contents in any way or you may be acting unlawfully; (ii) contact Northgate immediately on +44 (0)1442 232424 quoting the name of the sender and the addressee then delete it from your system.
Northgate has taken reasonable precautions to ensure that no viruses are contained in this email, but does not accept any responsibility once this email has been transmitted. You should scan attachments (if any) for viruses.
Northgate Information Solutions Limited. Registered in England no. 06442582 - Northgate Information Solutions UK Limited. Registered in England no. 968498 - NorthgateArinso UK Limited. Registered in England no. 1587537 - Moorepay Limited. Registered in England no. 891686 - Northgate Land & Property Solutions Limited - Registered in England no. 2149536 Registered Office: Peoplebuilding 2, Peoplebuilding Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire HP2 4NW
Northgate Managed Services Limited (NI). Registered in Northern Ireland no. NI032979 - LearnServe Limited (NI). Registered in Northern Ireland no. NI043825 Registered Office: Hillview House, 61 Church Road, Newtownabbey, Co. Antrim, BT36 7LQ
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
+1
I'd suggest just jumping to Java 5 library, source and target
compilation. I think this would give the project a new infusion of
activity and interest.
-Nathan
On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> 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
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Mark,
Mark Goodhand <mg...@gmail.com> wrote on 11/11/2008 03:49:43 AM:
<snip/>
> We have long since moved to Java 5, and would love to see Xerces drop
> support for old versions of Java (I believe 1.4 just reached EOSL [1]).
>
> The move to Java 5 would allow the code to be cleaned up considerably,
> and the availability of Java 5 libraries and language features would
> make the project much more attractive to developers.
>
> If a compromise is necessary, would you consider making Xerces-J 3.x
> require Java 5, while 2.9.x would continue to support old versions of
> Java (possibly even 1.2), but receive only crucial bug fixes?
I think I already answered that in the reply to Nathan and Jake's most
recent e-mails.
> Mark.
>
> [1] http://java.sun.com/products/archive/eol.policy.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Mark Goodhand <ma...@goodhand.ca>.
On 10 Nov 2008, at 03:51, Michael Glavassevich wrote:
> 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.
>
>
We have long since moved to Java 5, and would love to see Xerces drop
support for old versions of Java (I believe 1.4 just reached EOSL [1]).
The move to Java 5 would allow the code to be cleaned up considerably,
and the availability of Java 5 libraries and language features would
make the project much more attractive to developers.
If a compromise is necessary, would you consider making Xerces-J 3.x
require Java 5, while 2.9.x would continue to support old versions of
Java (possibly even 1.2), but receive only crucial bug fixes?
Mark.
[1] http://java.sun.com/products/archive/eol.policy.html
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Yes, Michael, I was the driving force behind that. I wanted to make sure
that we've made an informed decision before dropping support for one JDK
or another. Developers obviously like the new stuff but users are
sometimes stuck with old stuff. It often takes them a bit longer to
migrate although they usually skip a generation when they migrate.
Anyway. First, we talked about the questions we wanted to ask:
http://markmail.org/message/y6h6lfzcupbvuww3
Then I set up the survey with one of the online survey service providers.
I chose one that was free.
http://markmail.org/message/xz72bqpkqy6dg5l5
At the end of the survey, I downloaded the data and visualized selected
items with OpenOffice. All put together that resulted in the Wiki page
mentioned by Ludger Buenger:
http://wiki.apache.org/xmlgraphics/UserPollOct2007
I believe this survey, though took some time and effort to do, was worth
it and it wasn't difficult to do. And I'll push for one again when we
want to drop Java 1.4 support within the XML Graphics project. I expect
it won't take too long until we do another as Java 1.4 has reached EOL
last month. It's going to be interesting to see how the survey results
change over time. But given the small data base, don't assume the
results are 100% representative.
HTH
On 12.11.2008 06:42:33 Michael Glavassevich wrote:
>
> Any idea how this poll was done? A form you could submit on a website?
> Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
> had something to do with it. Was this poll easy to set up?
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> "Ludger Buenger" <lu...@realobjects.com> wrote on 11/11/2008
> 09:34:08 AM:
>
> > 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.
> >
> > 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=ant-dev&m=122596549809889&w=2
> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >
> > 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.
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Yes, Michael, I was the driving force behind that. I wanted to make sure
that we've made an informed decision before dropping support for one JDK
or another. Developers obviously like the new stuff but users are
sometimes stuck with old stuff. It often takes them a bit longer to
migrate although they usually skip a generation when they migrate.
Anyway. First, we talked about the questions we wanted to ask:
http://markmail.org/message/y6h6lfzcupbvuww3
Then I set up the survey with one of the online survey service providers.
I chose one that was free.
http://markmail.org/message/xz72bqpkqy6dg5l5
At the end of the survey, I downloaded the data and visualized selected
items with OpenOffice. All put together that resulted in the Wiki page
mentioned by Ludger Buenger:
http://wiki.apache.org/xmlgraphics/UserPollOct2007
I believe this survey, though took some time and effort to do, was worth
it and it wasn't difficult to do. And I'll push for one again when we
want to drop Java 1.4 support within the XML Graphics project. I expect
it won't take too long until we do another as Java 1.4 has reached EOL
last month. It's going to be interesting to see how the survey results
change over time. But given the small data base, don't assume the
results are 100% representative.
HTH
On 12.11.2008 06:42:33 Michael Glavassevich wrote:
>
> Any idea how this poll was done? A form you could submit on a website?
> Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
> had something to do with it. Was this poll easy to set up?
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> "Ludger Buenger" <lu...@realobjects.com> wrote on 11/11/2008
> 09:34:08 AM:
>
> > 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.
> >
> > 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=ant-dev&m=122596549809889&w=2
> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >
> > 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.
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Yes, Michael, I was the driving force behind that. I wanted to make sure
that we've made an informed decision before dropping support for one JDK
or another. Developers obviously like the new stuff but users are
sometimes stuck with old stuff. It often takes them a bit longer to
migrate although they usually skip a generation when they migrate.
Anyway. First, we talked about the questions we wanted to ask:
http://markmail.org/message/y6h6lfzcupbvuww3
Then I set up the survey with one of the online survey service providers.
I chose one that was free.
http://markmail.org/message/xz72bqpkqy6dg5l5
At the end of the survey, I downloaded the data and visualized selected
items with OpenOffice. All put together that resulted in the Wiki page
mentioned by Ludger Buenger:
http://wiki.apache.org/xmlgraphics/UserPollOct2007
I believe this survey, though took some time and effort to do, was worth
it and it wasn't difficult to do. And I'll push for one again when we
want to drop Java 1.4 support within the XML Graphics project. I expect
it won't take too long until we do another as Java 1.4 has reached EOL
last month. It's going to be interesting to see how the survey results
change over time. But given the small data base, don't assume the
results are 100% representative.
HTH
On 12.11.2008 06:42:33 Michael Glavassevich wrote:
>
> Any idea how this poll was done? A form you could submit on a website?
> Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
> had something to do with it. Was this poll easy to set up?
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> "Ludger Buenger" <lu...@realobjects.com> wrote on 11/11/2008
> 09:34:08 AM:
>
> > 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.
> >
> > 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=ant-dev&m=122596549809889&w=2
> > [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
> >
> > 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.
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Any idea how this poll was done? A form you could submit on a website?
Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
had something to do with it. Was this poll easy to set up?
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
"Ludger Buenger" <lu...@realobjects.com> wrote on 11/11/2008
09:34:08 AM:
> 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.
>
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> 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.
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Any idea how this poll was done? A form you could submit on a website?
Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
had something to do with it. Was this poll easy to set up?
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
"Ludger Buenger" <lu...@realobjects.com> wrote on 11/11/2008
09:34:08 AM:
> 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.
>
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> 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.
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Any idea how this poll was done? A form you could submit on a website?
Jeremias, seeing your name as the last editor on the Wiki I'm guessing you
had something to do with it. Was this poll easy to set up?
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
"Ludger Buenger" <lu...@realobjects.com> wrote on 11/11/2008
09:34:08 AM:
> 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.
>
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> 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.
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Ludger Buenger <lu...@realobjects.com>.
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.
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
<http://xerces.apache.org/xerces2-j/faq-general.html#faq-11>
[2] http://issues.apache.org/jira/browse/XERCESJ-1297
<http://issues.apache.org/jira/browse/XERCESJ-1297>
[3] http://marc.info/?l=ant-dev&m=122596549809889&w=2
<http://marc.info/?l=ant-dev&m=122596549809889&w=2>
[4] http://marc.info/?l=fop-user&m=119244442600564&w=2
<http://marc.info/?l=fop-user&m=119244442600564&w=2>
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.
<http://mailfilter.nc-sb.de/cgi-bin/learn-msg.cgi?id=A2B9C27F01.AE332>
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
+1
I'd suggest just jumping to Java 5 library, source and target
compilation. I think this would give the project a new infusion of
activity and interest.
-Nathan
On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Nathan Beyer <nd...@apache.org>.
+1
I'd suggest just jumping to Java 5 library, source and target
compilation. I think this would give the project a new infusion of
activity and interest.
-Nathan
On Sun, Nov 9, 2008 at 9:51 PM, Michael Glavassevich
<mr...@ca.ibm.com> wrote:
> 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=ant-dev&m=122596549809889&w=2
> [4] http://marc.info/?l=fop-user&m=119244442600564&w=2
>
> 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
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Bill Michell <bi...@bbc.co.uk>.
We've been on Java 6 for quite some time. Any performance enhancements
you can get by dropping support for earlier JVMs would be much
appreciated.
--
Bill Michell
Development Team Leader, Broadcast Platforms, BBC FM&T (Journalism).
________________________________
From: Michael Glavassevich [mailto:mrglavas@ca.ibm.com]
Sent: 10 November 2008 03:52
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=ant-dev&m=122596549809889&w=2
[4] http://marc.info/?l=fop-user&m=119244442600564&w=2
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Worth nothing that although Java 1.4 may have passed Sun's EOL date there
are other JDK vendors who may have end of service dates that are still in
the future. So it may be that a user who is still stuck on that JDK level
is still getting support and bug fixes that they wouldn't be getting
anymore for the Sun version. I wouldn't assume that the eventual releases
out of Apache Harmony would bind themselves to Sun's dates either (for when
they'd stop maintenance).
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Jeremias Maerki <de...@jeremias-maerki.ch> wrote on 11/11/2008 08:59:38 AM:
> On 11.11.2008 14:52:52 sebb wrote:
> > On 11/11/2008, Shane Curcuru <as...@shanecurcuru.org> wrote:
> > > +1 to dropping 1.2 support.
> >
> > +1 to dropping 1.2
> >
> > +0 to dropping 1.3
> >
> > I think 1.4 support should be kept if possible for a while yet.
>
> Agreed. Xerces is such a basic library and so many companies are still
> stuck with Java 1.4 even though it's past EOL.
>
> > > Please - be sure that the main website clearly lists the last
release we
> > > think that Xerces worked on JDK version x.y. Xerces is ubiquitous,
and is
> > > used directly or within other products virtually everywhere.
> While we don't
> > > need to spend developer time worrying about ancient JDK
> versions, we should
> > > make it clear where people who have to stay on legacy systems can get
an
> > > appropriate release.
> >
> > +1
> >
> > > I'd love it if we ensured that we feature a prominent link and host
the
> > > download for the zip/targz plus it's key file for "the last known
good
> > > Xerces with JDK x.y" as we drop support for earlier releases.
> > >
> >
> > +1
> >
> > > Thanks for bringing the item up!
> > >
> > > - Shane
>
> Jeremias Maerki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Worth nothing that although Java 1.4 may have passed Sun's EOL date there
are other JDK vendors who may have end of service dates that are still in
the future. So it may be that a user who is still stuck on that JDK level
is still getting support and bug fixes that they wouldn't be getting
anymore for the Sun version. I wouldn't assume that the eventual releases
out of Apache Harmony would bind themselves to Sun's dates either (for when
they'd stop maintenance).
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Jeremias Maerki <de...@jeremias-maerki.ch> wrote on 11/11/2008 08:59:38 AM:
> On 11.11.2008 14:52:52 sebb wrote:
> > On 11/11/2008, Shane Curcuru <as...@shanecurcuru.org> wrote:
> > > +1 to dropping 1.2 support.
> >
> > +1 to dropping 1.2
> >
> > +0 to dropping 1.3
> >
> > I think 1.4 support should be kept if possible for a while yet.
>
> Agreed. Xerces is such a basic library and so many companies are still
> stuck with Java 1.4 even though it's past EOL.
>
> > > Please - be sure that the main website clearly lists the last
release we
> > > think that Xerces worked on JDK version x.y. Xerces is ubiquitous,
and is
> > > used directly or within other products virtually everywhere.
> While we don't
> > > need to spend developer time worrying about ancient JDK
> versions, we should
> > > make it clear where people who have to stay on legacy systems can get
an
> > > appropriate release.
> >
> > +1
> >
> > > I'd love it if we ensured that we feature a prominent link and host
the
> > > download for the zip/targz plus it's key file for "the last known
good
> > > Xerces with JDK x.y" as we drop support for earlier releases.
> > >
> >
> > +1
> >
> > > Thanks for bringing the item up!
> > >
> > > - Shane
>
> Jeremias Maerki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Worth nothing that although Java 1.4 may have passed Sun's EOL date there
are other JDK vendors who may have end of service dates that are still in
the future. So it may be that a user who is still stuck on that JDK level
is still getting support and bug fixes that they wouldn't be getting
anymore for the Sun version. I wouldn't assume that the eventual releases
out of Apache Harmony would bind themselves to Sun's dates either (for when
they'd stop maintenance).
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Jeremias Maerki <de...@jeremias-maerki.ch> wrote on 11/11/2008 08:59:38 AM:
> On 11.11.2008 14:52:52 sebb wrote:
> > On 11/11/2008, Shane Curcuru <as...@shanecurcuru.org> wrote:
> > > +1 to dropping 1.2 support.
> >
> > +1 to dropping 1.2
> >
> > +0 to dropping 1.3
> >
> > I think 1.4 support should be kept if possible for a while yet.
>
> Agreed. Xerces is such a basic library and so many companies are still
> stuck with Java 1.4 even though it's past EOL.
>
> > > Please - be sure that the main website clearly lists the last
release we
> > > think that Xerces worked on JDK version x.y. Xerces is ubiquitous,
and is
> > > used directly or within other products virtually everywhere.
> While we don't
> > > need to spend developer time worrying about ancient JDK
> versions, we should
> > > make it clear where people who have to stay on legacy systems can get
an
> > > appropriate release.
> >
> > +1
> >
> > > I'd love it if we ensured that we feature a prominent link and host
the
> > > download for the zip/targz plus it's key file for "the last known
good
> > > Xerces with JDK x.y" as we drop support for earlier releases.
> > >
> >
> > +1
> >
> > > Thanks for bringing the item up!
> > >
> > > - Shane
>
> Jeremias Maerki
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 11.11.2008 14:52:52 sebb wrote:
> On 11/11/2008, Shane Curcuru <as...@shanecurcuru.org> wrote:
> > +1 to dropping 1.2 support.
>
> +1 to dropping 1.2
>
> +0 to dropping 1.3
>
> I think 1.4 support should be kept if possible for a while yet.
Agreed. Xerces is such a basic library and so many companies are still
stuck with Java 1.4 even though it's past EOL.
> > Please - be sure that the main website clearly lists the last release we
> > think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and is
> > used directly or within other products virtually everywhere. While we don't
> > need to spend developer time worrying about ancient JDK versions, we should
> > make it clear where people who have to stay on legacy systems can get an
> > appropriate release.
>
> +1
>
> > I'd love it if we ensured that we feature a prominent link and host the
> > download for the zip/targz plus it's key file for "the last known good
> > Xerces with JDK x.y" as we drop support for earlier releases.
> >
>
> +1
>
> > Thanks for bringing the item up!
> >
> > - Shane
> >
> >
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by sebb <se...@gmail.com>.
On 11/11/2008, Shane Curcuru <as...@shanecurcuru.org> wrote:
> +1 to dropping 1.2 support.
+1 to dropping 1.2
+0 to dropping 1.3
I think 1.4 support should be kept if possible for a while yet.
> Please - be sure that the main website clearly lists the last release we
> think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and is
> used directly or within other products virtually everywhere. While we don't
> need to spend developer time worrying about ancient JDK versions, we should
> make it clear where people who have to stay on legacy systems can get an
> appropriate release.
+1
> I'd love it if we ensured that we feature a prominent link and host the
> download for the zip/targz plus it's key file for "the last known good
> Xerces with JDK x.y" as we drop support for earlier releases.
>
+1
> Thanks for bringing the item up!
>
> - Shane
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Shane Curcuru <as...@shanecurcuru.org> wrote on 11/11/2008 08:08:50 AM:
> +1 to dropping 1.2 support.
>
> Please - be sure that the main website clearly lists the last release we
> think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and
> is used directly or within other products virtually everywhere. While
> we don't need to spend developer time worrying about ancient JDK
> versions, we should make it clear where people who have to stay on
> legacy systems can get an appropriate release.
There's already an FAQ [1] and release notes [2] which say where we moved
from JDK 1.1 to 1.2. We'll just add to it.
> I'd love it if we ensured that we feature a prominent link and host the
> download for the zip/targz plus it's key file for "the last known good
> Xerces with JDK x.y" as we drop support for earlier releases.
If someone wants to pick up an old version they will always be in the
archives [3].
> Thanks for bringing the item up!
>
> - Shane
Thanks.
[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
[2] http://xerces.apache.org/xerces2-j/releases.html
[3] http://archive.apache.org/dist/xml/xerces-j/
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Shane Curcuru <as...@shanecurcuru.org> wrote on 11/11/2008 08:08:50 AM:
> +1 to dropping 1.2 support.
>
> Please - be sure that the main website clearly lists the last release we
> think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and
> is used directly or within other products virtually everywhere. While
> we don't need to spend developer time worrying about ancient JDK
> versions, we should make it clear where people who have to stay on
> legacy systems can get an appropriate release.
There's already an FAQ [1] and release notes [2] which say where we moved
from JDK 1.1 to 1.2. We'll just add to it.
> I'd love it if we ensured that we feature a prominent link and host the
> download for the zip/targz plus it's key file for "the last known good
> Xerces with JDK x.y" as we drop support for earlier releases.
If someone wants to pick up an old version they will always be in the
archives [3].
> Thanks for bringing the item up!
>
> - Shane
Thanks.
[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
[2] http://xerces.apache.org/xerces2-j/releases.html
[3] http://archive.apache.org/dist/xml/xerces-j/
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in
the future)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Shane Curcuru <as...@shanecurcuru.org> wrote on 11/11/2008 08:08:50 AM:
> +1 to dropping 1.2 support.
>
> Please - be sure that the main website clearly lists the last release we
> think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and
> is used directly or within other products virtually everywhere. While
> we don't need to spend developer time worrying about ancient JDK
> versions, we should make it clear where people who have to stay on
> legacy systems can get an appropriate release.
There's already an FAQ [1] and release notes [2] which say where we moved
from JDK 1.1 to 1.2. We'll just add to it.
> I'd love it if we ensured that we feature a prominent link and host the
> download for the zip/targz plus it's key file for "the last known good
> Xerces with JDK x.y" as we drop support for earlier releases.
If someone wants to pick up an old version they will always be in the
archives [3].
> Thanks for bringing the item up!
>
> - Shane
Thanks.
[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-11
[2] http://xerces.apache.org/xerces2-j/releases.html
[3] http://archive.apache.org/dist/xml/xerces-j/
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Re: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3?
1.4? in the future)
Posted by Shane Curcuru <as...@shanecurcuru.org>.
+1 to dropping 1.2 support.
Please - be sure that the main website clearly lists the last release we
think that Xerces worked on JDK version x.y. Xerces is ubiquitous, and
is used directly or within other products virtually everywhere. While
we don't need to spend developer time worrying about ancient JDK
versions, we should make it clear where people who have to stay on
legacy systems can get an appropriate release.
I'd love it if we ensured that we feature a prominent link and host the
download for the zip/targz plus it's key file for "the last known good
Xerces with JDK x.y" as we drop support for earlier releases.
Thanks for bringing the item up!
- Shane
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Ludger Buenger <lu...@realobjects.com>.
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.
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
<http://xerces.apache.org/xerces2-j/faq-general.html#faq-11>
[2] http://issues.apache.org/jira/browse/XERCESJ-1297
<http://issues.apache.org/jira/browse/XERCESJ-1297>
[3] http://marc.info/?l=ant-dev&m=122596549809889&w=2
<http://marc.info/?l=ant-dev&m=122596549809889&w=2>
[4] http://marc.info/?l=fop-user&m=119244442600564&w=2
<http://marc.info/?l=fop-user&m=119244442600564&w=2>
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.
<http://mailfilter.nc-sb.de/cgi-bin/learn-msg.cgi?id=A2B9C27F01.AE332>
RE: Dropping JDK 1.2 support for Xerces-J (and possibly JDK 1.3? 1.4? in the future)
Posted by Ludger Buenger <lu...@realobjects.com>.
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.
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
<http://xerces.apache.org/xerces2-j/faq-general.html#faq-11>
[2] http://issues.apache.org/jira/browse/XERCESJ-1297
<http://issues.apache.org/jira/browse/XERCESJ-1297>
[3] http://marc.info/?l=ant-dev&m=122596549809889&w=2
<http://marc.info/?l=ant-dev&m=122596549809889&w=2>
[4] http://marc.info/?l=fop-user&m=119244442600564&w=2
<http://marc.info/?l=fop-user&m=119244442600564&w=2>
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.
<http://mailfilter.nc-sb.de/cgi-bin/learn-msg.cgi?id=A2B9C27F01.AE332>