Reflection.

Getting the implemented interfaces from a Class is a reflection activity.

Class.getInterfaces(!) and Class.getGenericInterfaces are the methods
you don't want.

Without reflection. Well, I suppose you could use a debugging interface,
 looks at class files or indirectly use reflection (serialisation,
beans, etc).

Tom Hawtin

Are you asking someone who write you a little command line utility
that does the dirty deed for you so you won't feel so guilty?

Hi ravi,

How do you read a book without opening it?

There may be solutions (perhaps x-ray, computertomography, ... which
Thomas, Roedy and paul mentioned) but (IMHO) the one and only practical
solution is just to open the book the way it is supposed to.

That means, concerning your problem: IMHO, there is no (practical)
possibility to solve your problem.

Why do you want to use no reflection? You seem to have a good reason
(which I do not understand).

Ciao,
Ingo

   Do you have to find out at runtime, or could you find out earlier? E.g.
could you perhaps read the JavaDocs to find out what interfaces the class
implements?

   - Oliver