My problem is, that i am not sure if i have done everything the right way. I am still
not sure that this was/is a missing feature. I still think i have configured the parse
kinda the wrong way. I was only able to spend 3-4 hours on this.
I cant deliver a patch because i cant test this one different plattforms. I have no
clue how the resources under Unix/Linux are managed. Of course i could read the source
but i dont get the time for this :/
Is there a maintainer for that code part ?
Regards
Kai-Uwe
Am Mo 15.03.2004 15:13, Alberto Massari <[EMAIL PROTECTED]> schrieb:
> At 14.56 15/03/2004 +0100, you wrote:
> >Can anyone help/comment this ?
>
> From your message it looks like you solved the problem; if you want to ask
> for this enhancement to be merged with the official code base, please file
> a bug in Bugzilla, adding a patch if possible
>
> Alberto
>
>
> >regards
> >Kai-Uwe
> >
> >Am Do 11.03.2004 20:36, Kai-Uwe Schmidt <[EMAIL PROTECTED]> schrieb:
> >
> > > Hi folks,
> > >
> > > i am trying to parse a xml with a schema included. I have trouble with
> > the informations i get in my errorhandler.
> > > i am missing the attribute name in the case the xml doesnt conform to
> > the xsd.
> > >
> > > The SAXParseException doesnt contain any data about the position of the
> > attribute which caused the error. Is this a misconfiguration of the parse
> > or a bug in my xml/xsd definition ? Or is this feature actually not
> > implemented. I have back traced the parser up to
> > SchemaValidator::validateAttrValue where i can find the attribute name
> > with attDef->getFullName() but it doesnt seem that the following methodes
> > transport this information down to my error handler (at least not with my
> > actuall parser configuration). Cananyone help me out to get the name of
> > the misfitting attribute ?
> > >
> > >
> > > Just for the case its a missing feature.
> > >
> > > The Information can be delivered to the user by modifying the resource
> > String table ID 16430 like this:
> > > Datatype error: Type:{0}, Attribute: {2}, Message:{1}.
> > > and upgrading:
> > > emitError (XMLValid::DatatypeError, idve.getType(),
> > idve.getMessage(),attDef->getFullName());
> > > in SchemaValidator::validateAttrValue.
> > >
> > > No clue how to make this OS independent (but i hope its not such a bad
> > hack).
> > >
> > >
> > > thanks alot
> > > Kai-Uwe
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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]
>
>
>
> ---------------------------------------------------------------------
> 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]
