<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:52:35 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-212] JSON in and out of MD-SAL is Inconsistent</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-212</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;&lt;a href=&quot;https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:EverythingYouWantedtoKNowaboutOnDataChanged_butWasAfraidToAsk#JSON_in_and_out_of_MD-SAL_is_Inconsistent&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:EverythingYouWantedtoKNowaboutOnDataChanged_butWasAfraidToAsk#JSON_in_and_out_of_MD-SAL_is_Inconsistent&lt;/a&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Mac OS&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="22632">YANGTOOLS-212</key>
            <summary>JSON in and out of MD-SAL is Inconsistent</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="repenno">Reinaldo Penno</reporter>
                        <labels>
                    </labels>
                <created>Sat, 12 Jul 2014 23:27:50 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:10 +0000</updated>
                            <resolved>Mon, 14 Jul 2014 08:17:07 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="42857" author="tony.tkacik@gmail.com" created="Mon, 14 Jul 2014 08:17:07 +0000"  >&lt;p&gt;Based on your description you used third-party reflection-based general-purposed JSON serializers. You could not expect output to conform to any YANG specific serialization or remotly be similar to Restconf one.&lt;/p&gt;

&lt;p&gt;It is out of scope of Binding Specification to support out-of-the box restconf compliant serialization to json using third-party libraries.&lt;/p&gt;

&lt;p&gt;Binding specification &lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;was design to provide compile-type representation of YANG modeled data&lt;/li&gt;
	&lt;li&gt;preserve semantical concepts (e.g. only one case applicable for choice,&lt;br/&gt;
    augmentations, identities| as much as possible in compilation type), not&lt;br/&gt;
    serialization specific ones.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Binding specification was never intended to provide easy RFC6020 or yang-json-api complient serialization to XML/JSON, but rather be independent from serialization to textual payload.&lt;/p&gt;

&lt;p&gt;If you want an utility to generate JSON out of binding DTO outside of restconf, please open enhancement bug for MD-SAL. We have utilities which provides you with XML output, but none for JSON.&lt;/p&gt;

&lt;p&gt;Opened folow-up enhancement &lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=1360&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=1360&lt;/a&gt;&lt;br/&gt;
 since this is out-of-scope of Binding Specification or YANGTools and may be fixed by introduction of utility service and not changing binding specification.&lt;/p&gt;</comment>
                    </comments>
                    <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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1358</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=1358]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10301"><![CDATA[Normal]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i025tz:</customfieldvalue>

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