On 13 December 2015 at 10:42, Stephen Cameron <[email protected]> wrote:
> > that the troublesome class is passed in for Schema creation in the > 'persistableClassNameSet' param, however though its marked as > @PersistenceCapable its not a persisted class in the true sense as its > abstract with InheritanceStrategy.SUBCLASS_TABLE. So I assume DN then > gets confused as it cannot find a DB table to validate it against. > > Off the top of the head, it would seem (and I think you are saying the same thing) that SUBCLASS_TABLE with abstract is contradictory, at least it is if there are no subclasses in turn. I'd suggest removing abstract modifier; if that doesn't help then I'd play around with different inheritance strategies, eg NEW_TABLE, just to get a position that's working. If necessary, we can escalate to Andy Jefferson on the DN forum, he presumably would know exactly what is valid and is invalid. Cheers Dan
