I've got the following problem :

I'm stuck with an existing DB-system that wasn't too well designed.
Now i'm trying to build a web-application to access it.
What i'm trying to do now is build a search-page.

I have two tables called Applmod & Communicator
Both contain entities called 'Modules' to the system, but the Communicator ones have more specific members.

With regular hibernate mapping files, i was able to do the following :
- create an abstract entitity called Module that contains the common members of both Applmod & Communicator (like applmodid, etc.)
The configuration Module.hbm.xml is something like :

<class name="Module" abstract="true">
<property name="applmodid"></property>
...
<union-subclass name="Applmod" table="APPLMOD">
...
</union-subclass>
<union-subclass name="Communicator" table="COMMUNICATOR">
...
</union-subclass>
</class>

Now what i was able to do is to do a hibernate query on Module, where the respons that i got was a list containing both Applmod & Communicator objects mixed together.

Now with the new annotations i don't succeed in querying the Module class anymore, since, as it turns out, if a class is not annotated as Entity , it's not loaded by an AnnotatedSessionFactory.

In the documentation they talk about MappedSuperClasses and the likes , but they have the same problem. Mapping Module as @Entity doesn't work, since it doesn't exist as a physical table.

Does anyone have experience/ideas about how i can get it to work with Annotations ?

Thanks !

Jeroen