Re: support for xerces 2.x in XMLc

LazyDOM is the least problem when it comes integrating with Xerces 2. 
To upgrade to Xerces 2, we are mostly dealing with the assumption XMLC 
made on DOM interface. I have posted a long discussion in the list 
explaining the problem.

"Moving XMLC to Xerces 2 won't help..."
http://xmlc.enhydra.org/project/mailingLists/xmlc/msg02059.html

We need to refactor XMLC first into the following modules and make sure 
each module uses only the standard DOM Level 2 API.

- Parsing
- DOM building
- DOM editing
- DOM output
- XMLC runtime

Then, upgrading to Xerces 2 would make sense. Otherwise, simply 
upgrading the DOM in XMLC to Xerces 2, we would encounter the exact 
same problem we had with XMLC right now. 2.2 alpha 4 partially solves 
the problem of using XMLC in a environment with Xerces 1/2 packages.

David

> > Moving to Xerces 2 is a big work and we still trying to figure out 
> > what's the best way to do this. I can't really give a schedule at 
> > this point.
> >
> > David
>
> Am I right to think that it's a big work due to LazyDOM ? Would it be 
> easier to have an XMLc with xerces 2.x without the lazyDOM as a 
> beginning ?
>
> New optimizations could be added afterward ?
>
> Gilles,
>
> --
> Gilles Sérasset
> GETA-CLIPS-IMAG (UJF, INPG & CNRS)
> BP 53 - F-38041 Grenoble Cedex 9
> Phone: +33 4 76 51 43 80
> Fax:   +33 4 76 44 66 75
>
>
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra