<?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 Vs interface in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954239#M945063</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;refer to these links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="459377"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="489460"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2008 03:36:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-05T03:36:28Z</dc:date>
    <item>
      <title>Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954234#M945058</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 have to buid a report in ECM with complete details of the engineering as well as production. This include workflow as well as various fucntionality depends upon the criterion and user's event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am implementating in OOPS and I Want to know that when I should use the Abstract class and when interface  ?&lt;/P&gt;&lt;P&gt;Because as per me both serve the same purpose. Kindly send me the exact difference so that i can efficiently use the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Prince&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2008 06:46:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954234#M945058</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-04T06:46:00Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954235#M945059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Abstract Class&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;Interface :&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;Diff. b/w Abstract Class and Interface :&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;The methods of an abstract class may contain default implementations for the sub-classes. The same is not possible with interface methods which are always empty.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2008 06:49:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954235#M945059</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-04T06:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954236#M945060</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;abstract class :  in these class we can declare the metthods and &lt;STRONG&gt;optionally can give definition of method.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;STRONG&gt;but at least one method must be there which is not defined&lt;/STRONG&gt; &lt;STRONG&gt;in this class.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  so that we can describe this class as ABSTRACT.&lt;/P&gt;&lt;P&gt;class who define definition of its methods called CONCRETE CLASS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INTERFACE :  &lt;STRONG&gt;u cannot give definition of method in it , u can&lt;/STRONG&gt; only declare methods here .&lt;/P&gt;&lt;P&gt; &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>Wed, 04 Jun 2008 06:55:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954236#M945060</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-04T06:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954237#M945061</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;How can we take decision about when we have to use Interface and when Abstract Class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basicly abstact class is a abstract view of any realword entity and interface is more abstract one. When we thinking about the entity there are two things one is intention and one is implemntation. Intention means I know about the entity and  also may have idea about its state as well as behaviour but donu2019t know about how its looks or works or may know partially. Implementation means actual state and behaviour of entity.   &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;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;preet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2008 09:13:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954237#M945061</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-04T09:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954238#M945062</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have a superclass and subclasses.  It there is at least one method in the superclass that will always be implemented differently in subclasses, &lt;STRONG&gt;and&lt;/STRONG&gt; you never want the superclass instantiated, then define the superclass as abstract, along with those methods that always be implemented differently in subclasses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An interface &lt;EM&gt;can&lt;/EM&gt; be viewed as an all-abstract class.  But it's more than that.  Interfaces are used to enabling the handling of quite different objects which still have a set of shared characteristics.  Imagines classes A and B that both implement interface I,.  I can then create a method in class C that takes as an importing parameter a reference to a type I object.  This means I can pass both A and B to the method in class C.  Even though A and B might be completely different.  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Interfaces are also used to mark classes with a particular property - e.g. serializable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, it's not really "abtract classes" vs "interfaces".  You use whichever is appropriate to whatever it is that you're trying to program.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2008 12:11:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954238#M945062</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2008-06-04T12:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954239#M945063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;refer to these links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="459377"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="489460"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 03:36:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954239#M945063</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T03:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954240#M945064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When inheriting A Interface We have to inherit all the methods of the Interface there's no other option whereas with abstract classes we can inherit the members that we are in need of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just the interface has to have body of the method and the method is to be used by the classes inheriting it. Whereas in the case of Abstract Class it can have declarations (Other than the abstract method) and it can be further extended in the classes inheriting the Abstract Class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Interface contains all abstract methods,all methods compulsory implemented by particular class, interface does not contain Constructor&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;abstract classes are designed with implemantion gaps for sub-class to fill in.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;interfaces are sintacticlly similar to classes but they lack insance variables &amp;amp; methods.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;abstract classes can also have both abstract methods &amp;amp; non-abstract methods. where as in interface methods are abstract only, &amp;amp; variables are implicitly static&amp;amp;final&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Preetesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 04:56:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954240#M945064</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T04:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: Abstract class Vs interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954241#M945065</link>
      <description>Abstract classInterface Abstract class contains both abstract and non abstract methods.Interface contains only abstract methods.Multiple inheritance is not possible.Multiple inheritance is possible.Need to use abstract keyword for abstract methods inside abstract class.No need of using abstract keyword , by default all the methods are abstract only.Visibility of the abstract components may be public or protected.By default all the interface components are public only.No need of prefixing the abstract components.Outside interface , interface components must be prefixed with the name of interface.&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tanuja.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Aug 2021 15:01:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abstract-class-vs-interface/m-p/3954241#M945065</guid>
      <dc:creator>former_member695272</dc:creator>
      <dc:date>2021-08-06T15:01:36Z</dc:date>
    </item>
  </channel>
</rss>

