<?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: Abstract Class and Interface in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337705#M800060</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An abstract class is the one that is not used to create objects. An abstract class is designed to act as a base class (to be inherited by other classes). Abstract class is a design concept in program development and provides a base upon which other classes are built. Abstract classes are similar to interfaces. After declaring an abstract class, it cannot be instantiated on it's own, it must be inherited. Like interfaces, abstract classes can specify members that must be implemented in inheriting classes. Unlike interfaces, a class can inherit only one abstract class. Abstract classes can only specify members that should be implemented by all inheriting classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces&lt;/P&gt;&lt;P&gt;Under the hood, an interface is like a class with some restrictions.&lt;/P&gt;&lt;P&gt;1. All its methods must be abstract instance methods, no static methods allowed.&lt;/P&gt;&lt;P&gt;2. Yet, all the variables defined in an interface must be static final, i.e. constants. Happily the values need not be known at compile time. You can do some computation at class load time to compute the values. The variables need not be just simple ints and Strings. They can be any type.&lt;/P&gt;&lt;P&gt;3. No static initialiser blocks. You must do your initialisations in one line per variable. And, of course, no static initialiser helper methods defined in the interface. If you need them, them must be defined outside the interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 09 Mar 2008 18:25:54 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-09T18:25:54Z</dc:date>
    <item>
      <title>Abstract Class and Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337704#M800059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please tell me what is Abstract Class and Interface. Please explain with help of  simple example and also tell me difference between them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Jan 2008 08:33:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337704#M800059</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-27T08:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract Class and Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337705#M800060</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An abstract class is the one that is not used to create objects. An abstract class is designed to act as a base class (to be inherited by other classes). Abstract class is a design concept in program development and provides a base upon which other classes are built. Abstract classes are similar to interfaces. After declaring an abstract class, it cannot be instantiated on it's own, it must be inherited. Like interfaces, abstract classes can specify members that must be implemented in inheriting classes. Unlike interfaces, a class can inherit only one abstract class. Abstract classes can only specify members that should be implemented by all inheriting classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces&lt;/P&gt;&lt;P&gt;Under the hood, an interface is like a class with some restrictions.&lt;/P&gt;&lt;P&gt;1. All its methods must be abstract instance methods, no static methods allowed.&lt;/P&gt;&lt;P&gt;2. Yet, all the variables defined in an interface must be static final, i.e. constants. Happily the values need not be known at compile time. You can do some computation at class load time to compute the values. The variables need not be just simple ints and Strings. They can be any type.&lt;/P&gt;&lt;P&gt;3. No static initialiser blocks. You must do your initialisations in one line per variable. And, of course, no static initialiser helper methods defined in the interface. If you need them, them must be defined outside the interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Mar 2008 18:25:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337705#M800060</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-09T18:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract Class and Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337706#M800061</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The methods of an abstract class may contain &lt;STRONG&gt;default implementations&lt;/STRONG&gt; for the sub-classes. The same is not possible with interface methods which are always empty.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 09 Mar 2008 19:51:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337706#M800061</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-03-09T19:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract Class and Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337707#M800062</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;i am sending the link.That contains the information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/java/when-we-go-for-abstract-and-interface.htm" target="test_blank"&gt;http://www.sap-img.com/java/when-we-go-for-abstract-and-interface.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Mar 2008 05:30:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337707#M800062</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-10T05:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract Class and Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337708#M800063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;  i will suggest u to refer some basic java book , to clear ur basic concept of OOPS , because these principal remain same for all languages that follow OOPS concept .&lt;/P&gt;&lt;P&gt;    and under standing these with java is easier then with ABAP .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Abstract Class&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;         class which have atleast 1 method which is declared only , (no definition is given for it in this class is mentioned as Abstract Method )  &lt;/P&gt;&lt;P&gt;            and that class is defined as Abstract class&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Interface :&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;         only declaration of method done here , no method will be defined here ,  class which will implement this interface will give definition .&lt;/P&gt;&lt;P&gt;       &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Diff. b/w   Abstract Class and Interface :&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;               ABS Class can have method with there definition , but one method should be there with declartion only.&lt;/P&gt;&lt;P&gt;              Interface will have all method with out definition .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hpoe this help u .&lt;/P&gt;&lt;P&gt;&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>Mon, 10 Mar 2008 05:48:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-and-interface/m-p/3337708#M800063</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-10T05:48:51Z</dc:date>
    </item>
  </channel>
</rss>

