Hi, Several days ago, I submitted the following question: Hello,
When invalid value is specified for an element of the "restriction" type, the message reported by Xerces parser (SAX) does not contain the problematic element name - only the invalid value and line & column in the source XML. For example: Datatype error: Type:InvalidDatatypeValueException, Message:Value 'xxx2' is not in enumeration . Line: 2 Column: 361 Are improvements (specifically specification of the problematic element name) planned for error messages, which are reported by Xerces parser (SAX)? Regards, Shahar. I got the below reply and it looks like this is not clear enough. Can you please review the question above? Regards, Shahar. _____________________________________________________ Shahar Levy Software Engineer Voice: + 972 3 6451716 CONTROL-M/Enterprise Manager Fax: + 972 3 6451100 BMC Software [EMAIL PROTECTED] -----Original Message----- From: Gendelman, Marina Sent: Thursday, August 07, 2008 12:43 PM To: Levy, Shahar Subject: RE: [jira] Updated: (XERCESC-1825) Default value of QName type with non-empty prefix causes segfault Hi Shahar, I am not sure I understand how the reported bug in the provided link answers / refers our question - If I correctly understand it the reported bug affects versions 2.8 & 3.0 of Xerces and we are using 2.7 (as far as I remember) - does it mean it fixed in 2.8 / 3.0 or exists in these versions? Also, our issue is that the reported error message just missing problematic element name. Does it mean that this information is missing the received error message because this bug? Thanks, Marina -----Original Message----- From: Levy, Shahar Sent: Thursday, August 07, 2008 7:25 AM To: Gendelman, Marina Subject: FW: [jira] Updated: (XERCESC-1825) Default value of QName type with non-empty prefix causes segfault Importance: High Marina Hi, Apache finally replied to your question/request. I couldn't understand from their reply whether they treat the problem as a bug or not. Before I am sending them another question, asking for clarifications on this reply, can you please review it (open the URL that is written in the beginning of the mail below) and let me know if this fits your needs? Thanks, Shahar. _____________________________________________________ Shahar Levy Software Engineer Voice: + 972 3 6451716 CONTROL-M/Enterprise Manager Fax: + 972 3 6451100 BMC Software [EMAIL PROTECTED] -----Original Message----- From: Boris Kolpackov (JIRA) [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 5:53 PM To: [email protected] Subject: [jira] Updated: (XERCESC-1825) Default value of QName type with non-empty prefix causes segfault [ https://issues.apache.org/jira/browse/XERCESC-1825?page=com.atlassian.ji ra.plugin.system.issuetabpanels:all-tabpanel ] Boris Kolpackov updated XERCESC-1825: ------------------------------------- Attachment: test.xml test.xsd > Default value of QName type with non-empty prefix causes segfault > ----------------------------------------------------------------- > > Key: XERCESC-1825 > URL: https://issues.apache.org/jira/browse/XERCESC-1825 > Project: Xerces-C++ > Issue Type: Bug > Components: Validating Parser (XML Schema) > Affects Versions: 2.8.0, 3.0.0 > Reporter: Boris Kolpackov > Priority: Critical > Fix For: 3.1.0 > > Attachments: test.xml, test.xsd > > > See the attached test case. I am not even sure why we try to resolve the prefix in the default value in the context of schema. I always thought (perhaps wrongly) that those must resolve only in the context of the instance document. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- 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]
