<?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 interface in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845868#M666692</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do the Interface can contain static  componenets (static methods,attributes).Does the interface contains attributes like that of a class.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 23 Sep 2007 05:55:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-23T05:55:16Z</dc:date>
    <item>
      <title>interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845868#M666692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do the Interface can contain static  componenets (static methods,attributes).Does the interface contains attributes like that of a class.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Sep 2007 05:55:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845868#M666692</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-23T05:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845869#M666693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From a technical point of view, interfaces are simply superclasses that cannot be instantiated, do not have an implementation part, and only have public components.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In ABAP Objects, interfaces primarily serve to define uniform interfaces (protocols) for services. Various classes can offer (that is, implement) these services in different ways, but keep the same semantics. Interfaces contain no implementation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Sep 2007 14:01:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845869#M666693</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-24T14:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845870#M666694</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;Interfaces only describe the external point of contact of a class (protocols), they do not contain any implementation. &lt;/P&gt;&lt;P&gt;Interfaces are usually defined by a user. The user describes in the interface which services (technical and semantic) it needs in order to carry out a task.&lt;/P&gt;&lt;P&gt; The user never actually knows the providers of these services, but communicates with them through the interface.&lt;/P&gt;&lt;P&gt; In this way the user is protected from actual implementations and can work in the same way with different classes/objects, as long as they provide the services required. This is known as polymorphism with interfaces. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Interfaces features&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Sepearation of external point of contact ( intrafce ) and implementation(class)&lt;/P&gt;&lt;P&gt;     - the client defines the protocol , the server implements it&lt;/P&gt;&lt;P&gt;     - &amp;#147; Black Box Principle &amp;#147; client only knows the interface , not the implementation &lt;/P&gt;&lt;P&gt;     - lowest linkage between client and server &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Polymorphism&lt;/P&gt;&lt;P&gt;     - generic handling of objects of different classes &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Abstraction&lt;/P&gt;&lt;P&gt;     - interface as a generalization of the implementing class&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simulation of multiple inheritance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Working with Interface components&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;You can access interface components using an object reference, whose class implements the interface.  Syntactically this is done with the interface resolution operator, just as with the method definitions in the implementation part of the class.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Sep 2007 06:03:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845870#M666694</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-25T06:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845871#M666695</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;Yes&lt;/P&gt;&lt;P&gt;Interfaces can contain Static components.&lt;/P&gt;&lt;P&gt;Interface can contain all the Components like a class:&lt;/P&gt;&lt;P&gt;1. Attributes&lt;/P&gt;&lt;P&gt;2. Methods&lt;/P&gt;&lt;P&gt;3. Events&lt;/P&gt;&lt;P&gt;4. Interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But all these are PUBLIC components by default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if Helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Sep 2007 10:25:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2845871#M666695</guid>
      <dc:creator>varma_narayana</dc:creator>
      <dc:date>2007-09-25T10:25:09Z</dc:date>
    </item>
  </channel>
</rss>

