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

Hi Richard,

Richard Kunze <kunze@xxxxxxxxx> writes:
> 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), 

As I recall, the only dependency with the generated classes is being being
able to defined integer constants in advance that the get* methods use to
index the arrays of node pointers.  Essentially at compile time, an element id
gets associated with an integer constant to access the array.  If
these indexs where not final (but still static) in the generated class and the
reloading filled in the index values when it built the template DOM, it should
all work and add very little additional overhead.

and easier said than done..