There is a PoJo class which is mapped to a PoJo table via PoJo.hbm.xml. Everything is managed by PoJoDAO and works fine. Until...

Someone writes a test case using a MockPoJo object which extends PoJo. They call PoJoDAO.save(mockPoJo) and Hibernate complains that the MockPoJo class is not mapped.

I have encountered sub-classes of mapped persistent classes before. This is the first time the sub-classing seemed legimate.

Is there an efficient way to get Hibernate to be polymorphic about this and persist the super class?

Hum, maybe we could allow that... there are probably consequences
Post a JIRA feature request on H3, I'd like to hear Gavin's opinion.