Elena, Thanks, that does help, though I really should have put those two together and got four myself. My own myopia aside, this is an area of functionality I need post-haste. Has in memory validation work begun yet, or is it still planning stage? In other words, are there any classes to look at to determine where to begin, after rolling up the sleeves?
Thanks again, Yuri Gadow On Mon, 2002-03-25 at 11:59, Elena Litani wrote: > Yuri hi, > > Yuri Gadow wrote: > > Looking for verification that the getErrorNode functionality is not in > > place for DOMLocator (other than having an accessor method and > > constructor parameter.) That is, I cannot find where the errorNode is > > ever set. If not, where might I start digging to determine how to make > > it happen? > > errorNode is set only in the case the Node is available. Xerces is a > streaming processor - we validate data as we read it, the DOM nodes are > created after validation. Thus, errorNode will not be set. > In the future when we support revalidation of DOM tree in memory the > error node should be available. > > Hope it helps, > -- > Elena Litani / IBM Toronto > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
