[ 
https://issues.apache.org/jira/browse/XERCESJ-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mukul Gandhi updated XERCESJ-1694:
----------------------------------
    Affects Version/s:     (was: 2.12.0)

setting "Affects Version/s" to null (what was there originally in bug report). 
I hope that is more correct. Someone, who will actually work on this bug 
report, will likely set a correct "Affects Version/s". Or the bug reporter 
could himself set the right "Affects Version/s".

> Avoid stack overflow when using xpointer between two resources
> --------------------------------------------------------------
>
>                 Key: XERCESJ-1694
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1694
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: SAX
>            Reporter: Radu Coravu
>            Priority: Major
>
> Let' say I have two documents:
> 1) "a.xml":
> {code}<book xmlns="http://docbook.org/ns/docbook";
>     xmlns:xlink="http://www.w3.org/1999/xlink";
>     xmlns:xi="http://www.w3.org/2001/XInclude";
>     xml:id="a-book"
>     version="5.0">
>     <title>A</title>
>     <chapter xml:id="a-chapter">
>         <title>a chapter</title>
>         <para>foo</para>
>     </chapter>
>     <xi:include href="b.xml" xpointer="b-chapter"/>
> </book>{code}
> 2) "b.xml":
> {code}<book xmlns="http://docbook.org/ns/docbook";
>     xmlns:xlink="http://www.w3.org/1999/xlink";
>     xmlns:xi="http://www.w3.org/2001/XInclude";
>     xml:id="b-book"
>     version="5.0">
>     <title>B</title>
>     <chapter xml:id="b-chapter">
>         <title>b chapter</title>
>         <para>foo</para>
>     </chapter>
>     <xi:include href="a.xml" xpointer="a-chapter"/>
> </book>{code}
> When using a SAX parser to parse "a.xml" a stack overflow occurs although 
> according to the XInclude specs this is a legal situation, the xpointer parts 
> to a part of b.xml.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to