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.
DOM Level 3 APIs for Xalan-J and a new Xalan release (2.7.1)

DOM Level 3 APIs for Xalan-J and a new Xalan release (2.7.1)

2006-10-16       - By Brian Minchau
Reply:     1     2     3     4  


Fellow developers,

I had started some voting both on accepting some code to support DOM Level
3 APIs from the Apache Xerces team into Xalan-J. I had also started a vote
on having a new Apache Xalan release, 2.7.1.  All voting was on the
"pmc@(protected)"  ( pmc = Project Management Committee)  mailing list, since
the PMC has the ultimate vote on such issues.

A fellow PMC member has made me aware that the various PMC mailing lists
are now "private@(protected)" and the old "pmc@(protected)" lists are just aliases
to "private", and the "private" is for issues that cannot or should not be
discussed in public, such as security problems, or discussions that require
confidentiality.

Be assured that DOM Level 3 APIs and a new release are not issues that
Xalan wishes to hide from the public.  I was thinking "pmc" rather than
"private".

So before I put these to a vote (among the PMC members on *this* xalan-dev
mailing list), I'm going to open up the discussion.

The Apache Xerces project would like to use the serializer that is in Xalan
and deprecate their own serializer.  This has already been discussed on the
Xerces mailing lists. The biggest problem with this is that the Xalan
serializer does not support the DOM Level 3 APIs. Xerces would like to
donate some code to Xalan to make that happen and start using the Xalan
serializer.

Any thoughts on this?  I'm hoping that this will work out.

The second point of discussion is much more brief. Xalan 2.7.0 was released
on Aug 8, 2005, and I think it is high time to put out 2.7.1, hopefully
with the DOM Level 3 support.  Any thoughts on Xalan 2.7.1?

- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Apache Xalan PMC Member


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