[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [xml] Question about error reporting when using key / keyref constraints in Schema
- From: Kasimier Buchcik <kbuchcik 4commerce de>
- To: Daniel Veillard <veillard redhat com>
- Cc: "xml gnome org" <xml gnome org>
- Subject: Re: [xml] Question about error reporting when using key / keyref constraints in Schema
- Date: Thu, 11 Aug 2005 15:55:42 +0200
Hi,
On Thu, 2005-08-11 at 09:40 -0400, Daniel Veillard wrote:
> On Thu, Aug 11, 2005 at 03:31:50PM +0200, Kasimier Buchcik wrote:
> > This is expected, but I understand that it does not help chasing
> > instance errors.
> > We changed the behaviour due to streaming validation. Keyrefs
[...]
>
> maybe the line of the reference can be saved at the same time of the
> value, that's what I did for ID in DTD validation when streaming. And
> it is sufficient for the error report you don't need to keep a pointer
> to the node.
This would be anchored in _xmlSchemaPSVIIDCNode. We still have a
"node" field there - a remainder. So remove "node" and add "int line"?
> > By the way, I tested this with Xerces-J 2.7.1:
> >
> > keyref.xml:7,12: (Error) Key 'keyref' with value 'test' not found for
> > identity constraint of element 'ELEMENTS'.
> > (the line number points to the end tag of ELEMENTS by the way)
> >
> > Xerces uses the same mechanism as we do.
>
> We can certainly improve over xerces user-friendlyness ;-)
OK, I'll try.
Regards,
Kasimier
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]