Hi Mark, No, the class exists, and the annotations apparently were fine as well - I could resolve this issue, but the solution is as weird as the issue itself:
I used to have a subset of classes present in my persistence.xml (assume there are entities A-Z, and A-C were listed in persistence.xml). However scanning was not turned off, so OpenJPA would deal with both sets (and presumably merge them). In fact, those few entity classes listed in persistence.xml were an oversight on my part, as I rely on scanning for entity classes for the application. After frusttrating long hours I finally discovered those remaining listed classes and removed them from persistence.xml - and that made it work... No idea why that would cause a problem, but apparently it did, and only after adding another entity.. I can only speculate about what the reasons were, maybe there is interference with OpenJPA's runtime class enhancement (I'm not using build-time enhancement so the built app is not bound to OpenJPA). Sorry I can't be more specific, I'm just glad it's resolved now.. Cheers, Uwe
