anonymous wrote : I've annotated the class as MappedSuperclass AND Entity
I'm thinking that this will possibly cause some strange behaviour, you could
also check out the inheritence strategies such as single table, or table per
subclass
Cheers,
Andy
View the original post :
http://www.jboss.
anonymous wrote : Try declaring ArticleConsumeSchemaTemplate as a
mappedSuperclass (so long as you don't need the template class persisted)
|
That seems to be the solution. I've annotated the class as MappedSuperclass AND
Entity and it went through the Initializing. So I will do now some tes
Or you could try experimenting with the targetEntity in @OneToMany side ??
Andy
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981720#3981720
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981720
__
Try declaring ArticleConsumeSchemaTemplate as a mappedSuperclass (so long as
you don't need the template class persisted)
Have a look here
http://opensource.atlassian.com/projects/hibernate/browse/ANN-390 as it seems
to be similar to your problem.
Andy
View the original post :
http://www.jbo
Tried that, the result is
mappedBy reference an unknown target entity property:
.ArticleConsumeSchema.schema in
.ConsumeSchema.articleSchemas
schema is an inherited attribute - and that worked earlier.
Next suggestion, please?
Kai
View the original post :
http://www.jboss.com/index.html?mod
I would try moving the annotations to the getter method(s). This is because i
experienced the same problem/exception in 4.0.4GA when i was annotating at the
variable declaration, moving it to the getter sloved the problem.
Andy
View the original post :
http://www.jboss.com/index.html?module=b
