I checked the forums and the docs but cannot find an answer to this problem. It should work but it doesn't.

Hibernate version: 3.2.6 ga
Mapping documents: Annotation

I am using sessions (not entitymanager) with annotated classes.

I have an abstract root class (PersistentObject) which contains callback methods annotated with PrePersist and PreUpdate but they never seem to be called when an entity of a subclass is persisted or updated.

Are these annotations useless if one doesn't use entitymanager? This would be very strange because @Version works.

The root class for all entities:
-------------------
package limes.core;

/**
* The class containing the common properties of the persistent classes in
* the system.
*/
@MappedSuperclass
public abstract class PersistentObject {
private Long id;
private int version;
private Date created;
private Date lastModified;

public PersistentObject() { super(); }

@Id
@GeneratedValue(strategy = GenerationType.AUTO)
public Long getId() { return id; }
public void setId(Long id) { this.id = id; }

@Temporal(TemporalType.TIME)
public Date getCreated() { return created; }
public void setCreated(Date created) { this.created = created; }

@Temporal(TemporalType.TIME)
public Date getLastModified() { return lastModified; }
public void setLastModified(Date lastModified) { this.lastModified = lastModified; }

@Version
public int getVersion() { return version; }
public void setVersion(int version) { this.version = version; }

@PrePersist
public void prePersist() {
setCreated(new Date());
}
@PreUpdate
public void preUpdate() {
setLastModified(new Date());
}
}
----------------------------------------------------------------

Any help is appreciated!

Yes, this was my observation too.. Not sure if Hibernate has been JPA certified.. I see these @Prexx would play imp. lifecycle in JPA specification.

Regards,
Nagendra

As a temporary solution I did it the traditional way and registered an Interceptor on the Configuration.

However, I am still interested in how to use @PreXXX callbacks.

Guys,

Please reply as I also have the same issue and its not working with session.

Thanks,
Rahul

this is a bit silly as JPA standard has been created basing on Hibernate.

Anyway this looks like a JPA feature, so I think you should use Hibernate's EntityManager,
the Session is not required to be JPA compliant, so use Entitymanager if you need JPA.

I have the same issue too,waiting for your reply.
Thank you first.

Bump... anybody heard anything about this behaviour? I'm also experiencing it.

For the record:
Hibernate: 3.2.6
Annotations: 3.3.1
Validator: 3.0.0

Regards,
Robert