ABAP Objects - Super/SubClass Inheritance of Interface Methods

[Dart, Jocelyn]

Hi Mike/Florin, 
 
Please remember that Delegation only refers to BOR objects and only permits one subtype to one supertype relationship.
 
With ABAP Objects with use narrowing/widening cast e.g. by adjusting the options in the bindings (by pressing the arrow head button in the binding window).  This allows the use of many subtype/supertype relationships.  The only thing we don't use is ABAP Interfaces - you need to do class to class bindings. 
 
Regards,
Jocelyn

________________________________

From: sap-wug-bounces at mit.edu on behalf of Florin Wach
Sent: Fri 3/04/2009 1:51 AM
To: SAP Workflow Users' Group
Subject: Re: ABAP Objects - Super/SubClass Inheritance of Interface Methods



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
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug