This content has been marked as final. Show 2 replies
Thanks for helping us to diagnose this problem. As I mentioned in email, the workaround for this problem is to call EntityModel.registerClass for each entity subclass in your program. For example:
I strongly recommend that all users of JE 3.3.71 or earlier, who define entity subclasses, perform this workaround to guard against the problem.
// MyEntity is an @Entity class, while MyEntitySubclass is a @Persistent class that // extends MyEntity. StoreConfig storeConfig = new StoreConfig(); // configure the store as usual EntityModel model = new AnnotationModel(); model.registerClass(MyEntitySubclass.class); // register all entity subclasses storeConfig.setModel(model); EntityStore store = new EntityStore(..., storeConfig);
The problem has been fixed in JE 3.3.72 and greater. We won't be pushing this release to our servers until further changes warrant a new public release. If anyone would like a copy of this release before then, please send me email -- mark.hayes at the obvious .com.
Thanks again Jeff,