documenting GenerationGap-based classes

This is a design patterns question rather than a WO question, but I 
figure a lot of WO folks use eogenerator/Generation Gap to manager their 
EOs so this would be a good place to ask.

How do you manage documentation for EO classes based on Generation Gap?
Javadoc comments are required to be immediately adjacent to the methods 
they modify. By using Generation Gap, however, most of these methods 
only exist on the superclass and the only class you ever edit is the 
derived class.

So ... where do you / how do you document your EO attributes and 
relationships?

zak.