<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: AXL bug within XBusyLampField since version 8 in Management</title>
    <link>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584626#M2429</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an existing defect that addresses this issue - CSCum90218. It's fix will be included in future 11.x release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Feb 2015 19:46:13 GMT</pubDate>
    <dc:creator>smupadhy</dc:creator>
    <dc:date>2015-02-27T19:46:13Z</dc:date>
    <item>
      <title>AXL bug within XBusyLampField since version 8</title>
      <link>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584624#M2427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are still hitting a bug within the AXLSoap.xsd. The choice tag is to low in the tree.&lt;/P&gt;&lt;P&gt;Because of this the AXL will always return a blfDest is missing.&lt;/P&gt;&lt;P&gt;On the left is the working solution, on the right is the 10.5 AXLSoap.xsd file.&lt;/P&gt;&lt;P&gt;The &amp;lt;xsd:choice minOccurs='1'&amp;gt; should be right after &amp;lt;xsd:sequence minOccurs='0'&amp;gt; instead of being after the &amp;lt;xsd:element maxOccurs='1' name='blfDest'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="AXLSoap.xsd bug.jpg" class="image-1 jive-image" src="/legacyfs/online/fusion/85756_AXLSoap.xsd bug.jpg" style="width: 620px; height: 286px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 16:23:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584624#M2427</guid>
      <dc:creator>Peter Buijsse</dc:creator>
      <dc:date>2015-02-09T16:23:05Z</dc:date>
    </item>
    <item>
      <title>Re: AXL bug within XBusyLampField since version 8</title>
      <link>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584625#M2428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will look into this and get back to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Feb 2015 22:20:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584625#M2428</guid>
      <dc:creator>smupadhy</dc:creator>
      <dc:date>2015-02-20T22:20:58Z</dc:date>
    </item>
    <item>
      <title>Re: AXL bug within XBusyLampField since version 8</title>
      <link>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584626#M2429</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an existing defect that addresses this issue - CSCum90218. It's fix will be included in future 11.x release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Feb 2015 19:46:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/3584626#M2429</guid>
      <dc:creator>smupadhy</dc:creator>
      <dc:date>2015-02-27T19:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: AXL bug within XBusyLampField since version 8</title>
      <link>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/4172831#M3510</link>
      <description>&lt;P&gt;It seems that it´s still not fixed in Version 12.5(1)SU2 as I ran into it but many thanks for solution &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/264526"&gt;@Peter Buijsse&lt;/a&gt; &lt;span class="lia-unicode-emoji" title=":grinning_face_with_big_eyes:"&gt;😃&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Oct 2020 22:13:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/4172831#M3510</guid>
      <dc:creator>sven.stubbe</dc:creator>
      <dc:date>2020-10-23T22:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: AXL bug within XBusyLampField since version 8</title>
      <link>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/4176207#M3514</link>
      <description>&lt;P&gt;Ya, it looks like the defect description wasn't the greatest, and the 'fix' wasn't what was needed.&amp;nbsp; I've opened a new defect with hopefully more specific guidance: CSCvw30202&lt;/P&gt;</description>
      <pubDate>Fri, 30 Oct 2020 02:37:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/m-p/4176207#M3514</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2020-10-30T02:37:31Z</dc:date>
    </item>
  </channel>
</rss>

