You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by Yuri Gadow <yu...@ieee.org> on 2002/03/25 19:42:28 UTC
DOM 3 DOMLocator.getErrorNode() Impl
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?
Thanks,
--
Yuri Gadow 0x6D21BAAE 1 720 323 3943
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: DOM 3 DOMLocator.getErrorNode() Impl
Posted by Elena Litani <el...@ca.ibm.com>.
Yuri Gadow wrote:
> 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?
No, we have not yet started to work on revalidation. It is on our to-do
list.
If you are interested to help out please send message to xerces-j-dev
list -- we will need to coordinate development.
Thanks!
--
Elena Litani / IBM Toronto
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: DOM 3 DOMLocator.getErrorNode() Impl
Posted by Yuri Gadow <yu...@ieee.org>.
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: xerces-j-user-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org
Re: DOM 3 DOMLocator.getErrorNode() Impl
Posted by Elena Litani <el...@ca.ibm.com>.
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: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org