i have a base class that all the classes extend it.

Lets call it Base:

abstract Class Base
String id;
String Name

I dont want to have a table for this class because it will cause to bad performance (all the tables will need to join with this table and all the records will have to write also to this table)

So i used in strategy of table per class.

I all other classes i want to use join, because all the advantage in join strategy.

So how can i set the table per class strategy only for the base class ?
I dont want to use in @MappedSuperClass , because i need this class as an entity.

I read that there is some workaround for this issue, can any one help?

Does any one has a reference to the spec on mixing strategy?

Thank you

there is no other solution. use @MappedSuperclass or even better get rid of this bad practice of having a technical superclass. This was a mistake in EJB 2 and it's a mistake in your code.

There are some fields that are required in all the classes.

like:
name,id,version,status

Also, its help a lot in polymorfism, becasue i can write a generic API that retrun the Base class and get the Base class.

I will be very happy to understand why you think this is a bad practice.

Thank you

You should use inheritance for your business concerns, not your technical concerns in the domain model