Re: Inheritance and DefaultBeanPropertyTableProvider

Hmm.. As far as I can see it should work (properties of the first class being shown)..

However, is it possible your JPA mappings are not correct (in other words: causing the JPA query not to be correctly built?). I've never actually used JPA inheritance like you show, so I'm not sure it's correct.

The second possibility is of course that this is a genuine bug - I found a bug related to validation of composite id's a few days ago as well.
I guess this goes onto my list of things to look at and potentially fix, although I probably won't be able to do so until the weekend (although a new release is in the works).

In the meantime, I think if it is not a problem with the JPA mappings (double check this with the docs), the best option is probably to implement your own tableprovider that fixes this issue, and/or use the Wicket RAD source for the table provider you do use and fix it there (if you do the latter, please send me the fix! :D).
I'm pretty sure if this is a bug (which I will double check) - the problem lies in the tableprovider, as you say you can see the headings but no  results (indicating the problem is in the JPA lookup and/or count).