<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:42 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-926] XMLStreamNormalizedNodeStreamWriter anyxml breaks with woodstox</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-926</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;As noted in &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-591&quot; title=&quot;Netconf connection failing in master (neon)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-591&quot;&gt;&lt;del&gt;NETCONF-591&lt;/del&gt;&lt;/a&gt; if we have a slightly different XMLOutputFactory in the picture anyxml serialization fails.&lt;/p&gt;

&lt;p&gt;This can be readily observed by dropping woodstox-core as a test dependency in yang-data-codec-xml - it will escalate multiple errors, some of which are showing &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-591&quot; title=&quot;Netconf connection failing in master (neon)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-591&quot;&gt;&lt;del&gt;NETCONF-591&lt;/del&gt;&lt;/a&gt; breakage with others being comparison errors.&lt;/p&gt;

&lt;p&gt;The most notable issue is anyxml encoding, which seems to be hacky at best and could probably be fixed by not using a transformer.&lt;/p&gt;</description>
                <environment></environment>
        <key id="31313">YANGTOOLS-926</key>
            <summary>XMLStreamNormalizedNodeStreamWriter anyxml breaks with woodstox</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Tue, 15 Jan 2019 14:27:35 +0000</created>
                <updated>Wed, 16 Jan 2019 22:33:04 +0000</updated>
                            <resolved>Wed, 16 Jan 2019 22:33:04 +0000</resolved>
                                    <version>2.1.7</version>
                                    <fixVersion>2.1.8</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="66201" author="rovarga" created="Tue, 15 Jan 2019 23:36:11 +0000"  >&lt;p&gt;So the hackiness of anyxml encoding comes from the fact we are using a Transformer to stream events from DOMSource to XMLStreamWriter and that implementation is definitely buggy &#8211; hence we should just ditch the transformer and never look back.&lt;/p&gt;

&lt;p&gt;Doing that requires some thought as to what we want to do, the options being:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;use DOMSourceXMLStreamReader (based on stax2-api) and pipe that into the writer&lt;/li&gt;
	&lt;li&gt;write a Element -&amp;gt; XMLStreamWriter transcriber&lt;/li&gt;
	&lt;li&gt;try to retain Transformer by attepting a DOM -&amp;gt; SAX -&amp;gt; StAX conversion with an intermediate XMLEventWriter&lt;/li&gt;
	&lt;li&gt;something completely different&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="66202" author="rovarga" created="Wed, 16 Jan 2019 03:15:00 +0000"  >&lt;p&gt;Option 1 is the simplest and seems to work okay.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="31267">NETCONF-591</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="23221">YANGTOOLS-801</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03m47:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>