Re: Do you ever use reflection instead of OO?

I know I'm taking a chance posting a question like this on a java
newsgroiup...

There a lot of well known advantages to OO, but I have recently
started using the java reflection to take care of many simpler
situations. It gives up some of the advantages of OO, but saves a few
imports, the need for external libraries in some contexts and offers a
few other advantages.

For example, suppose I'm writing a library for producing HTML pages,
and my Table class has an Object obj in one of its cells. Then to
render it to HTML it could use the following pseudo code:

if (hasMethod(obj, "toHTML"))
  print(callMethod(obj), "toHTML"));
else
  print(obj.toString());

The OO alternative would be to create an interface "HTMLable", but the
above approach saves the user from having to implement that on every
type of object that he might want to stick into a table. As another
alternative, the Table code could use, if (instanceof HTMLable), but I
feel that that is neither here nor there.

How do feel about my "OO crime" for simple situations?