<?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 Please delete me in vSphere Guest SDK Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-Guest-SDK-Discussions/Please-delete-me/m-p/2905218#M565</link>
    <description>&lt;P&gt;Please delete, wrong topic.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Christian&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;Is there a long term (next 5 years) plan to deprecate the SOAP API (vSphere Web Services API) in future vCenter/ESXi versions?&lt;/STRIKE&gt;&lt;BR /&gt;&lt;STRIKE&gt;So if I have a new project, do I rather go straight to the REST API or can I confidently build on the latest SOAP API?&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;In addition, in the medium term (next 2 years), will the oldest supported SOAP version 4.0 (declared in SOAPAction, listed in ...vimServiceVersions.xml) no longer be supported? The question arises whether an old project/code (which uses SOAP 4.0 calls) should be adapted to version 6.0 or it is still compatible with future vCenter/iESX versions.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;The aim of the project/code is to read out all existing vSphere entities very deeply for the purpose of inventory.&lt;/STRIKE&gt;&lt;BR /&gt;&lt;STRIKE&gt;I would be very grateful for a brief assessment from the community.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;Thanks a lot&lt;/STRIKE&gt;&lt;BR /&gt;&lt;STRIKE&gt;Christian&lt;/STRIKE&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 10 May 2022 14:45:15 GMT</pubDate>
    <dc:creator>ChrSche</dc:creator>
    <dc:date>2022-05-10T14:45:15Z</dc:date>
    <item>
      <title>Please delete me</title>
      <link>https://communities.vmware.com/t5/vSphere-Guest-SDK-Discussions/Please-delete-me/m-p/2905218#M565</link>
      <description>&lt;P&gt;Please delete, wrong topic.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Christian&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;Is there a long term (next 5 years) plan to deprecate the SOAP API (vSphere Web Services API) in future vCenter/ESXi versions?&lt;/STRIKE&gt;&lt;BR /&gt;&lt;STRIKE&gt;So if I have a new project, do I rather go straight to the REST API or can I confidently build on the latest SOAP API?&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;In addition, in the medium term (next 2 years), will the oldest supported SOAP version 4.0 (declared in SOAPAction, listed in ...vimServiceVersions.xml) no longer be supported? The question arises whether an old project/code (which uses SOAP 4.0 calls) should be adapted to version 6.0 or it is still compatible with future vCenter/iESX versions.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;The aim of the project/code is to read out all existing vSphere entities very deeply for the purpose of inventory.&lt;/STRIKE&gt;&lt;BR /&gt;&lt;STRIKE&gt;I would be very grateful for a brief assessment from the community.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;Thanks a lot&lt;/STRIKE&gt;&lt;BR /&gt;&lt;STRIKE&gt;Christian&lt;/STRIKE&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 14:45:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Guest-SDK-Discussions/Please-delete-me/m-p/2905218#M565</guid>
      <dc:creator>ChrSche</dc:creator>
      <dc:date>2022-05-10T14:45:15Z</dc:date>
    </item>
  </channel>
</rss>

