Re: Moving XMLC to Xerces 2 won't help...

On Thursday 23 January 2003 12:08, David Li wrote:
[ ... snip ... ]
> I think we should just move the patched Xerces into the
> org.enhydra.xmlc name space. From the point of LazyDOM, I'd argue that
> it makes perfect senses to do so. LazyDOM depends not on interfaces but
> implementations of the particular Xerces it uses. We can not really
> move LazyDOM among different versions of Xerces 1 and expect it to just
> work.

Great idea, at least to get it working short-time.

For the next major release, I think we should consider moving to Dom4J as the 
basis for XMLC's DOM implementation. Pros are:

- The Dom4J API is (IMO) easier to work with than the DOM API (small wonder,
  as Dom4J is designed to be a lot more Java-centric than DOM)
- Dom4J gives access to the same document tree both using its own API and the
  org.w3c.dom APIs
- Dom4J has builtin XPath support.

Cons:
- Need to redesign the LazyDOM based on Dom4J
- Lots of work changing XMLC to the new DOM implementation

Actually, we'd have to do both of these in the long run anyway, even if we 
stay with Xerces. The LazyDOM as it is doesn't play very nice with the new 
reloading code (the main problem is that LazyDOM is optimized for the case of 
constructing the template DOM "by hand" in the methods generated in each 
class, whereas the new reloading code parses the DOM template from a file), 
and I think we're all agreed that XMLC needs a bit of refactoring to 
disentangle its internals :-)

-- 
Richard Kunze 

[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de, kunze@xxxxxxxxx