ABAP Objects - Super/SubClass Inheritance of Interface Methods

[Florin Wach]

that's how it workes and why it's designed that way.

To exchange one object for another at runtime you can use the "Delegation", which is aliasing a subtype of an object with the supertype. (Which is kind non-conform to object oriented approaches, but ...well, we're not talking about object orientation with POR's anyhow :-)

Best wishes,
   Florin

-------- Original-Nachricht --------
> Datum: Thu, 2 Apr 2009 10:09:13 -0400
> Von: "Michael McInerney" <michaelm at duke.edu>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: ABAP Objects - Super/SubClass Inheritance of Interface Methods

> I have an ABAP object which is workflow enabled.
> 
> All is good.
> 
> I would like to create a few different flavors of this object via
> subclasses/inheritance, using the original workflow enabled object as the
> superclass.
> 
> The key definition will remain the same.
> 
> I'm expecting that my interface methods and their implementation (POR
> stuff) will hold up just fine, and can remain at the upper level, but I wanted
> to make sure.
> 
>  
> 
> Thanks.
> 
>  
> 
> .Mike
>