<?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 Strange quick fix suggestion for method implementation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775856#M1878374</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to follow the example from the &lt;A _jive_internal="true" href="https://answers.sap.com/docs/DOC-40668"&gt;REST How-to&lt;/A&gt;. When implementing the resource application class (chapter 2.3.2), I've noticed something I do not understand. I've created a new class (using AiE of course), set the base class and then used the quick fix to generate the missing methods. The quick fix then generated method implementations for REGISTER_RESOURCES and GET_APPLICATION_TITLE -- which are both abstract methods of the superclass CL_ADT_DISC_RES_APP_BASE, so this is not surprising. In addition to that, a redefinition of IF_REST_APPLICATION~GET_ROOT_HANDLER was generated, and I don't understand why. This method is implemented by CL_ADT_RES_APP_BASE, so there's no obvious reason to generate a redefinition. I figured that maybe some glitch occurred and deleted the method. I then added the redefinition for&amp;nbsp; IF_ADT_REST_RFC_APPLICATION~GET_STATIC_URI_PATH and opened the quick fix to create the method body. I was surprised by this suggestion:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/595918" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pressing Ctrl+1 while focused on the class header yields a similar result:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="jiveImage" src="https://community.sap.com/" style="max-width: 1200px; max-height: 900px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The warning that causes the yellow underline of the method looks strange as well:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/596065" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It shows GET_STATIC_URI_PATH twice, but the quick fix still suggests GET_ROOT_HANDLER. Did I trigger some kind of bug there?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp; Volker&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Nov 2014 21:51:57 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-11-27T21:51:57Z</dc:date>
    <item>
      <title>Strange quick fix suggestion for method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775856#M1878374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to follow the example from the &lt;A _jive_internal="true" href="https://answers.sap.com/docs/DOC-40668"&gt;REST How-to&lt;/A&gt;. When implementing the resource application class (chapter 2.3.2), I've noticed something I do not understand. I've created a new class (using AiE of course), set the base class and then used the quick fix to generate the missing methods. The quick fix then generated method implementations for REGISTER_RESOURCES and GET_APPLICATION_TITLE -- which are both abstract methods of the superclass CL_ADT_DISC_RES_APP_BASE, so this is not surprising. In addition to that, a redefinition of IF_REST_APPLICATION~GET_ROOT_HANDLER was generated, and I don't understand why. This method is implemented by CL_ADT_RES_APP_BASE, so there's no obvious reason to generate a redefinition. I figured that maybe some glitch occurred and deleted the method. I then added the redefinition for&amp;nbsp; IF_ADT_REST_RFC_APPLICATION~GET_STATIC_URI_PATH and opened the quick fix to create the method body. I was surprised by this suggestion:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/595918" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pressing Ctrl+1 while focused on the class header yields a similar result:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="jiveImage" src="https://community.sap.com/" style="max-width: 1200px; max-height: 900px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The warning that causes the yellow underline of the method looks strange as well:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/596065" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It shows GET_STATIC_URI_PATH twice, but the quick fix still suggests GET_ROOT_HANDLER. Did I trigger some kind of bug there?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp; Volker&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Nov 2014 21:51:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775856#M1878374</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-11-27T21:51:57Z</dc:date>
    </item>
    <item>
      <title>Re: Strange quick fix suggestion for method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775857#M1878375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Volker,&lt;/P&gt;&lt;P&gt;what is your ABAP backend release, support package level?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Thomas.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Nov 2014 06:55:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775857#M1878375</guid>
      <dc:creator>ThFiedler</dc:creator>
      <dc:date>2014-11-28T06:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: Strange quick fix suggestion for method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775858#M1878376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sorry - I'm used to SAPnet messages where that information is transferred automatically. The backend is SAP_BASIS/SAP_ABA 731 SP 13; it will be patched next week, but I'm not entirely sure to which level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;&amp;nbsp; Volker&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Nov 2014 08:16:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/strange-quick-fix-suggestion-for-method-implementation/m-p/10775858#M1878376</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-11-28T08:16:28Z</dc:date>
    </item>
  </channel>
</rss>

