ClassCastException in PropertyFactory when deugging

caterham · **Posted:** Fri Mar 03, 2006 11:38 am

Hibernate version:
3.1.2
Mapping documents:
Annotations
Full stack trace of any exception that occurs:

Code:

Caused by: java.lang.ClassCastException: org.hibernate.type.StringType
   at org.hibernate.tuple.PropertyFactory.buildVersionProperty(PropertyFactory.java:83)
   at org.hibernate.tuple.EntityMetamodel.<init>(EntityMetamodel.java:157)
   at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:412)
   at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:108)
   at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)
   at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:215)
   at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1176)
   at de.innosystec.persistence.HibernateSessionFactory.createSessionFactoryIfNeeded(HibernateSessionFactory.java:162)
   at de.innosystec.persistence.HibernateSessionFactory.getSessionFactory(HibernateSessionFactory.java:179)
   at de.innosystec.persistence.HibernateSessionProvider.currentSession(HibernateSessionProvider.java:62)
   at de.innosystec.persistence.HibernateSessionFactory.currentSession(HibernateSessionFactory.java:130)

Name and version of the database you are using:
Oracle 10gR2

When I start my application in debug mode I get the above mentioned ClassCastException. If I start the application normally everything runs fine.

Can the reason be that we use Annotations? I can't find a real reaon for this behaviour. Maybe someone can help me.

Rgds,
Axel

kgignatyev · **Posted:** Fri Mar 03, 2006 12:05 pm

I think version property is supposed to be number like Long or Integer, but I see String type has been mentioned in the trace. Could it be that debug classpath holds some outdated mappings, classes etc. Watch for differences.

caterham · **Posted:** Mon Mar 06, 2006 9:16 am

kgignatyev wrote:

Could it be that debug classpath holds some outdated mappings, classes etc. Watch for differences.

The classpath for debugging and running the application is identical in Eclipse. But now the exception also occurs when starting the application in normal mode. I don't really understand the exception because all version column in my DB are Integers! Someone knows what to do against this exception?

kgignatyev · **Posted:** Mon Mar 06, 2006 11:28 am

It is about class property, or whatever do you have in the mapping file. The version property should be one of implementations of VersionType, namely IntegerType, LongType, TimestampType, etc.
StringType is not among them.

caterham · **Posted:** Mon Mar 06, 2006 11:43 am

kgignatyev wrote:

It is about class property, or whatever do you have in the mapping file. The version property should be one of implementations of VersionType, namely IntegerType, LongType, TimestampType, etc.
StringType is not among them.

I don't have mapping files, because I use Annotations. It looks like in the example below. What's wrong with this definiton?

Code:

@Version
@Column(name="VERSION", unique=false, nullable=false, insertable=true, updatable=true, precision=8, scale=0)
  public Integer getVersion() 
  {
    return this.version;
   }

kgignatyev · **Posted:** Mon Mar 06, 2006 12:05 pm

I do not use annotations because they feel buggy at this time and therefore could not help you here much, perhaps there is some bug in the annotation because yours looks OK for me
http://www.hibernate.org/hib_docs/annot ... tml#d0e235
Try to remove all the extras from column definition and leave column name only

caterham · **Posted:** Tue Mar 07, 2006 5:18 am

I found a fix for my problem. I just added a Type annotation to my Version column. Now it seems to be fixed and Version is always recognized as Integer column. The annotation now looks like below.

Code:

@Version
@Type(type="java.lang.Integer")
@Column(name="VERSION", unique=false, nullable=false, insertable=false, updatable=false, precision=8, scale=0)
  public Integer getVersion()
  {
    return this.version;
  } 

emmanuel · **Posted:** Tue Mar 07, 2006 2:09 pm

I don't reproduce your problem. What I do reproduce though is an insert issue since you column is not insertable and non nullable => when Hibernate inserts it is screwed up.

Why do annotations "feel" buggy?

kgignatyev · **Posted:** Tue Mar 07, 2006 3:25 pm

Hard to tell exactly why, as I said that is my feeling caused by reading posts.
Do not use them because our clients do not use Java5 yet :(

caterham · **Posted:** Tue Mar 07, 2006 5:40 pm

emmanuel wrote:

I don't reproduce your problem. What I do reproduce though is an insert issue since you column is not insertable and non nullable => when Hibernate inserts it is screwed up.

For me Annotations work well. We're going to use them in a production environment because of the better performance when starting the application. (It's a fat client Swing application).

The version column will be nullable in future. The ClassCastException is hard to reproduce. We had two clients which were running without any problem all the time. Two other clients had the ClassCastException always. It's identical hardware. On my laptop I had the ClassCastException sometimes, but I could not find out what caused it to appear or not. With the Type-annotation the Exception is not thrown any more. So this is the best case we could achieve.

Maybe a hint: Our entity class extends a base class which is annotated with

Code:

@MappedSuperClass

In this base class is the version property. Maybe you can reproduce in such an environment.