Persistence Problem after upgrading to 4.0.5GA

[schlaufuchs]

Hi there,

I have switched today from 4.0.4GA to 4.0.5GA and now my persistence classes produce a problem I can't fix for myself.

These three classes are involved:

@Entity
public class ConsumeSchema implements Serializable {

 private static final long serialVersionUID = 369451547383041185L;

 private String name;

 private String comment;

 private int id;

 @OneToMany(mappedBy = "schema")
 private Set<ArticleConsumeSchema> articleSchemas;
...

@Entity
public class ArticleConsumeSchema extends ArticleConsumeSchemaTemplate {

 private static final long serialVersionUID = -5703518518625567286L;

}


@Entity
public class ArticleConsumeSchemaTemplate implements Serializable, Comparable<ArticleConsumeSchemaTemplate> {

 private static final long serialVersionUID = 1L;

 private long UTFtime;

 private long interval;

 private int id;

 @ManyToOne
 private Article article;

 /**
 * Zeigt auf die allgemeine Beschreibung des Schemas.
 */
 @ManyToOne
 private ConsumeSchema schema;

...

This construct worked well till my upgrade today. (Fresh install of 4.0.5GA in EJB3 config). Now I get:

ObjectName: persistence.units:jar=core-ejb3.ejb3.jar,unitName=core
 State: FAILED
 Reason: javax.persistence.PersistenceException: org.hibernate.MappingException: Could not determine type for: java.util.Set, for columns: [org.hibernate.mapping.Column(articleSchemas)]

What could be wrong?

Kind regards,
Kai

[andydale]

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

[schlaufuchs]

Tried that, the result is

mappedBy reference an unknown target entity property: <packagename>.ArticleConsumeSchema.schema in <packagename>.ConsumeSchema.articleSchemas

schema is an inherited attribute - and that worked earlier.

Next suggestion, please?

Kai

[andydale]

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

[andydale]

Or you could try experimenting with the targetEntity in @OneToMany side ??

Andy

[schlaufuchs]

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 tests if it still does behave as before.

Thanks!
Kai

[andydale]

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