Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
RES: Dropping JDK 1.1. Support for Xerces2

RES: Dropping JDK 1.1. Support for Xerces2

2004-01-12       - By Rubens Del Monte

Elena,


    I'm developing an application for palmtops and the VMs compatible with
palms support only JDK 1.1.
    I'm using Xerces 2.5, and  I use DOM with the PSVI document
implementation.

Rubens Del Monte


-----Mensagem original-----
De: Elena Litani [mailto:elitani@(protected)]
Enviada em: segunda-feira, 12 de janeiro de 2004 14:06
Para: xerces-j-user@(protected); xerces-j-dev@(protected)
Assunto: Dropping JDK 1.1. Support for Xerces2






I would like to propose to drop JDK 1.1 support in the upcoming Xerces2
release (end of January).

As you know, each new level of JDK provides better performance and includes
more functionality, some of which we would like to start using in Xerces.
For example, JDK 1.2 includes new utility classes, e.g. Arrays class that
provides useful methods for manipulating arrays and HashMap class which is
roughly equivalent to Hashtable, except that it is unsynchronized.
In the future, if we choose to support character normalization in Xerces
[1] we might need JDK 1.4 which includes some support for internalization.

Just to point out, we are probably the last project in XML Apache that
still supports JDK 1.1:
Ant 1.6.0 requires JDK 1.2 or higher (http://ant.apache.org/)
Batik requires JDK 1.3 or higher
(http://xml.apache.org/batik/faqs.html#faq-17)
FOP 0.20.3 requires JDK 1.2 or higher
(http://xml.apache.org/fop/relnotes.html)
Xindice requires JDK 1.3 or higher
(http://xml.apache.org/xindice/faq.html#faq-N10067)
Xalan requires JDK 1.2 or higher
(http://xml.apache.org/xalan-j/downloads.html)

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

I ask all committers to vote on this proposal.

Here is my +1.

[1] http://www.w3.org/TR/2003/WD-charmod-20030822/

Thank you,
--
Elena Litani/ IBM Toronto


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)