Instrumentation: Dealing with subclasses

At the moment the system doesn't know what to do with subclasses. The
safest way to use subclasses atm it to use some abstract superclass without
any fields. This is a serious limitation and needs to be fixed.

What is the problem with subclasses?
- initialisation logic like the the extra generated handle could cause
problems because it is placed in the superclass (if it is a tmentity) and
in the subclass.

- mapping of fields.. (and do the fields of a non TmEntity super class also
need to be mapped if the subclass is a tmentity?) And what if there is a 

@TmEntity
class A{}

class B extends A{}

@TmEntity
class C extends B{}

So the system at the moment is not able do deal with subclasses.

Original issue reported on code.google.com by alarmnum...@gmail.com on 19 May 2009 at 4:53

dezbyte / multiverse

Instrumentation: Dealing with subclasses #82