Jake, Jacob Kjome <[EMAIL PROTECTED]> wrote on 08/30/2006 12:15:36 AM:
<snip/> > >> If this is not objectionable, could this be done before the next > >release? > > > >The HTML DOM [1] should probably be calling that method too and would need > >this change in order to call it. I'll put it on my TODO list. Just > >remember, you're taking a risk by extending or referencing Xerces' > >internals. Any class or interface marked with @xerces.internal could go > >away or have methods on them change in the future. > > > > Yep, no problem. If Xerces goes some other direction that I can't > follow, then I'll roll it up into my own namespace. Actually, that > is what I'm doing now. I'll have the chance to quit wrapping it in > my own namespace as soon as the next version of Xerces is released > (along with a new version of xmlcommons-resolver). There's been no movement on a new resolver release. I don't think there are any technical issues blocking one. Just nobody has stepped up to make it happen yet. If you're interested in seeing one get into the next Xerces release (I've been thinking of proposing one for September) you should try stirring up a conversation on the xml-commons list (and probably pinging Norm). > Thanks! > > Jake Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
