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-17       - By Brian Minchau
Reply:     1     2     3     4  

Hi Michael,

Is there a bit of chicken and egg issue here?  Are you suggesting a 2.8.2
release of Xerces shortly before Xalan 2.7.1 and that 2.8.2 would include a
copy of the serializer inside of Xalan with the DOM Level 3 APIs?

FYI, I'm thinking that a Xalan 2.7.1 release could come out in late
November.  How would that work for Xerces?


- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau



                                                                         
            Michael                                                      
            Glavassevich/Toro                                            
            nto/IBM@(protected)                                              To
                                      j-dev@(protected)            
            10/17/2006 01:17                                           cc
            PM                        xalan-dev@(protected)            
                                                                  Subject
                                      Re: DOM Level 3 APIs for Xalan-J    
            Please respond to         and a new Xalan release (2.7.1)    
            j-dev@(protected)                                            
                 he.org                                                  
                                                                         
                                                                         
                                                                         
                                                                         




Brian Minchau/Toronto/IBM@(protected) wrote on 10/17/2006 12:37:41 AM:

<snip/>

> 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.

I believe Neil has been making progress on the DOM L3 work. It would be
great if this could make it into Xalan 2.7.1. There are a few changes
which would need to be made to the Xerces source to hook in the new
serializer so once the code is in place (and frozen) in Xalan we should
probably push out a Xerces 2.8.2 (maybe 2.9? if we're deprecating the old
Xerces serializer) shortly before Xalan 2.7.1.

> 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)

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@(protected)
E-mail: mrglavas@(protected)

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




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