Hi,

I didn't see this addressed anywhere in the FAQ, nor could I find any other forum posts about this.

Is there a technical or philosophical reason that declaring 2nd-level caching policy is not supported at the subclass level rather than only at the class level?

I.e., it seems that hibernate, in the case of subclasses, knows it is looking for FooSubOne.class or FooSubTwo.class when it goes to load the data.

Just curious, we sort of need it or a workaround, wondering if it made sense to think about trying to add this capability.