Ошибка формата сообщения saxparseexception cvc pattern valid value

[78] Санкт-Петербург

[47] Ленинградская область

[77] г. Москва

[01] Республика Адыгея (Адыгея)

[03] Республика Бурятия

[04] Республика Алтай

[05] Республика Дагестан

[07] Кабардино-Балкарская Республика

[09] Карачаево-Черкесская Республика

[10] Республика Карелия

[11] Республика Коми

[12] Республика Марий Эл

[13] Республика Мордовия

[14] Республика Саха (Якутия)

[15] Республика Северная Осетия — Алания

[16] Республика Татарстан

[17] Республика Тыва

[18] Удмуртская Республика

[19] Республика Хакасия

[21] Чувашская Республика — Чувашия

[22] Алтайский край

[23] Краснодарский край

[24] Красноярский край

[25] Приморский край

[26] Ставропольский край

[27] Хабаровский край

[28] Амурская область

[29] Архангельская область

[30] Астраханская область

[31] Белгородская область

[32] Брянская область

[33] Владимирская область

[34] Волгоградская область

[35] Вологодская область

[36] Воронежская область

[37] Ивановская область

[38] Иркутская область

[39] Калининградская область

[40] Калужская область

[42] Кемеровская область

[43] Кировская область

[44] Костромская область

[45] Курганская область

[46] Курская область

[48] Липецкая область

[50] Московская область

[51] Мурманская область

[52] Нижегородская область

[53] Новгородская область

[55] Омская область

[56] Оренбургская область

[57] Орловская область

[58] Пензенская область

[59] Пермский край

[60] Псковская область

[61] Ростовская область

[62] Рязанская область

[63] Самарская область

[64] Саратовская область

[65] Сахалинская область

[66] Свердловская область

[67] Смоленская область

[68] Тамбовская область

[69] Тверская область

[70] Томская область

[71] Тульская область

[72] Тюменская область

[73] Ульяновская область

[74] Челябинская область

[75] Забайкальский край

[76] Ярославская область

[79] Еврейская автономная область

[83] Ненецкий автономный округ

[86] Ханты-Мансийский автономный округ — Югра

[89] Ямало-Ненецкий автономный округ

[91] Республика Крым

[92] Севастополь

Часовой пояс GMT +3, время: 07:58.

I’m validating against XMLSchema in Java, and getting SAXParseExceptions thrown when I have non-valid content models.

I’m going to be using these exceptions to highlight where the validation has failed — but the SAXParseExceptions seem to be a little too low-level.

For example, for a failure on an enumeration, I get the validity error that the value provided doesn’t match the content model in one exception, and the element it applies to in the next.

I’m thinking I need to have a utility that abstracts a little to merge related errors together and parse exception text into useable exception properties.

Is this a reasonable approach, or am I just missing something, or maybe a library or helper class?

Update @timgilbert, thanks for the response.

For example, a SAXParseException I found on t’internet

cvc-pattern-valid: Value 'en' is not facet-valid
with respect to pattern '([a-zA-Z]{1,8})(-[a-zA-Z0-9]{1,8})*'

The key things for me are

• Element ‘en’ to which this exception applies. Why can I not call exception.getElement() or something, and why not an XPath to the element in question? More useful with an in-memory document than the line and column number!
• It’s a pattern validation failure. Why can I not get something like a enumeration of possible types of failure and a reference to the appropriate one?
• The actual pattern that validation has failed against.
• There’ll be another exception thrown next to tell me the value of the ‘en’ element that caused the problem that I need to merge

An example of what I’d like to be able to do is have people submit a document and have the document highlighted where validation fails with a user friendly message — the error message above kinda doesn’t seem very friendly… having to parse by single quotes just feels like an accident waiting to happen

I think I’m maybe doing it wrong with the ‘reference-to-element’ thing, and perhaps I should have an identity transform of the document by default as part of the validation, and augment the transformation with validation-error attributes that I can pick out with CSS. That still won’t help if I need to parse the messages to make them more friendly though…

Re: tight binding, javax.xml.validation.Validator.validate() throws org.xml.sax.SAXException anyway — not sure how I can get away from assuming the binding…

Cheers

I’m validating against XMLSchema in Java, and getting SAXParseExceptions thrown when I have non-valid content models.

I’m going to be using these exceptions to highlight where the validation has failed — but the SAXParseExceptions seem to be a little too low-level.

For example, for a failure on an enumeration, I get the validity error that the value provided doesn’t match the content model in one exception, and the element it applies to in the next.

I’m thinking I need to have a utility that abstracts a little to merge related errors together and parse exception text into useable exception properties.

Is this a reasonable approach, or am I just missing something, or maybe a library or helper class?

Update @timgilbert, thanks for the response.

For example, a SAXParseException I found on t’internet

cvc-pattern-valid: Value 'en' is not facet-valid
with respect to pattern '([a-zA-Z]{1,8})(-[a-zA-Z0-9]{1,8})*'

The key things for me are

• Element ‘en’ to which this exception applies. Why can I not call exception.getElement() or something, and why not an XPath to the element in question? More useful with an in-memory document than the line and column number!
• It’s a pattern validation failure. Why can I not get something like a enumeration of possible types of failure and a reference to the appropriate one?
• The actual pattern that validation has failed against.
• There’ll be another exception thrown next to tell me the value of the ‘en’ element that caused the problem that I need to merge

An example of what I’d like to be able to do is have people submit a document and have the document highlighted where validation fails with a user friendly message — the error message above kinda doesn’t seem very friendly… having to parse by single quotes just feels like an accident waiting to happen

I think I’m maybe doing it wrong with the ‘reference-to-element’ thing, and perhaps I should have an identity transform of the document by default as part of the validation, and augment the transformation with validation-error attributes that I can pick out with CSS. That still won’t help if I need to parse the messages to make them more friendly though…

Re: tight binding, javax.xml.validation.Validator.validate() throws org.xml.sax.SAXException anyway — not sure how I can get away from assuming the binding…

Cheers