Re: Re: Possible Bug: Xerces 2.12.1 for XML Validation with XSD 1.1 Schema under Java - Plain Text

Mukul Gandhi <[email protected]> Fri, 28 Aug 2020 09:17:12 +0530
Newsgroups gmane.text.xml.xerces-j.user
Message-ID <CABuuzNN4nN02WCyuR=T6x0skSpsYq0VYnjAGe40AU6ghyFJcNA@mail.gmail.com>
--00000000000064aabd05ade7e9a8
Content-Type: text/plain; charset="UTF-8"

Hi John,

On Wed, Aug 26, 2020 at 7:47 PM JOHN Morris <[email protected]> wrote:

Also, I wonder whether I could get you to send me the exact outputs from
> your jaxp.SourceValidator runs on the two files test1.xml (9 errors) and
> test2.xml (18 errors).


I just saw that, you've created a Jira issue XERCESJ-1726 for this
discussion. Thanks.

I'm now able to reproduce the issues described by you within this
discussion.

I've now used, the XML documents (test1.xml & test2.xml) and an XSD
document (test.xsd) that you've attached to the above mentioned Jira issue.
With those files, the XML document test1.xml gives me 9 XSD validation
errors, and the file test2.xml gives me no XSD validation errors.

When I remove the XML comment from line 40 of the file test2.xml, I get 9
XSD validation errors for the file test2.xml after removal of XML comment.
This looks to me strange, and may be a bug with Xerces-J and should be
investigated I believe.


> Is there a command-line option for jaxp.SourceValidator which would
> produce additional lines in the output for the original XML from each line
> in the input file, whether valid or not?
>

I guess that, there's no such command line option
with jaxp.SourceValidator. Inherently, after validation using
jaxp.SourceValidator, either we see line and column numbers with error
descriptions for the instances that are involved in invalidity assessment
for the XML and XSD documents, or if the XML document is valid the output
displays nothing (except the time it took for the XSD validation to take
place).



-- 
Regards,
Mukul Gandhi

--00000000000064aabd05ade7e9a8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi=
 John,</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Wed, Aug 26, 2020 at 7:47 PM JOHN Morris &lt;<a href=3D"mailto:j.m=
[email protected]" target=3D"_blank">[email protected]</a>&gt; wro=
te:</div><div dir=3D"ltr" class=3D"gmail_attr"><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
Also, I wonder whether I could get you to send me the exact outputs from yo=
ur jaxp.SourceValidator runs on the two files test1.xml (9 errors) and test=
2.xml (18 errors).</blockquote><div><br></div><div>I just saw that, you&#39=
;ve created a Jira issue=C2=A0XERCESJ-1726 for this discussion. Thanks.</di=
v><div><br></div><div>I&#39;m now able to reproduce the issues described by=
 you within this discussion.</div><div><br></div><div>I&#39;ve now used, th=
e XML documents (test1.xml &amp; test2.xml) and an XSD document (test.xsd) =
that you&#39;ve attached to the above mentioned Jira issue. With those file=
s, the XML document test1.xml gives me 9 XSD validation errors, and the fil=
e test2.xml gives me no XSD validation errors.</div><div><br></div><div>Whe=
n I remove the XML comment from line 40 of the file test2.xml, I get 9 XSD =
validation errors for the file test2.xml after removal of XML comment. This=
 looks to me strange, and may be a bug with Xerces-J and should be investig=
ated I believe.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">
Is there a command-line option for jaxp.SourceValidator which would produce=
 additional lines in the output for the original XML from each line in the =
input file, whether valid or not?<br></blockquote><div><br></div><div>I gue=
ss that, there&#39;s no such command line option with=C2=A0jaxp.SourceValid=
ator. Inherently, after validation using jaxp.SourceValidator, either we se=
e line and column numbers with error descriptions for the instances that ar=
e involved in invalidity assessment for the XML and XSD documents,=C2=A0or =
if the XML document is valid the output displays nothing (except the time i=
t took for the XSD validation to take place).</div><div><br></div><div>=C2=
=A0</div></div><div><br></div>-- <br><div dir=3D"ltr"><div dir=3D"ltr"><div=
>Regards,<br>Mukul Gandhi<br></div></div></div></div></div></div></div>

--00000000000064aabd05ade7e9a8--