just call it?
public MarkupContainer getAlternateParent(...)
{
return super.getAlternateParent(...);
}
}
MyBorder already implements IAlternateParentProvider
because border does it which it extends..
so this is not really needed:
class MyBorder extends Border implement IAlternateParentProvider
that could be just
class MyBorder extends Border
On 11/4/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
Assume
class Border implements IAlternateParentProvider
{
...
public MarkupContainer getAlternateParent(...)
{
return whatever;
}
}
class MyBorder extends Border implement IAlternateParentProvider
{
....
public MarkupContainer getAlternateParent(...)
{
return ??? How to call the super implementation?
}
}
Juergen
On 11/4/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> Class.getInterfaces() ?
> That gives the interfaces that that class implements.
>
> But if you extend a class. Then you already know at compile time that it
> implements the interface or not.
> So why do you want to check for that at runtime?
> And you can always do an instanceof check
>
> johan
>
>
> On 11/4/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> >
> > IAlternateParentProvider is an interface and Border for example
> > implements it. The disadvantage is that no subclass of Border is able
> > to reliably change the IAlternateParentProvider implementation as
> > super.XXX is not available. Or does anyone know a means to check that
> > a superclass implements the interface and than call the superclass'
> > implementation from the subclass?
> >
> > Juergen
> >
>
>
