logo       

Re: Re: Enhydra: support for xerces 2.x in XMLc: msg#00059

java.enhydra.general

Subject: Re: Re: Enhydra: support for xerces 2.x in XMLc

I don't have a detailed plan yet. However, the current alpha 4 has solved most of the problems of using XMLC in a environment with Xerces1/2.

Moving to Xerces 2 is only good if we can use Xerces 2 (or any DOM Level 2 compliant packages) "unmodified." Otherwise, we are going to have to same problem as we facing right now.

Will post more when I get a chance to look into in detail about what needs to be done.

David


On Wednesday, Mar 19, 2003, at 20:46 Asia/Shanghai, Alfred Madl wrote:

Hi David !

Would it be possible from your side to draw a detailled plan for updating to Xerces 2 ?

Since we will have the need for Xerces 2 in Enhydra 6.0 (which will support Tomcat 4.x and other servlet servers) we would like to do that move in XMLC. But we can definitely need your help for outlining the detailled plan.

Please tell us what you always wanted to do...

Greetings.

Alfred


From: David Li <david@xxxxxxxxxxxxxxxxx>
Reply-To: enhydra@xxxxxxxxxxx
To: enhydra@xxxxxxxxxxx
Subject: Re: Enhydra: support for xerces 2.x in XMLc
Date: Wed, 19 Mar 2003 19:00:20 +0800

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


_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise