PrePersist « Map « JPA Q&A

  1. JPA Q&A
  2. Map
  3. PrePersist




1. @PrePersist with entity inheritance    stackoverflow.com

I'm having some problems with inheritance and the @PrePersist annotation. My source code looks like the following: _the 'base' class with the annotated updateDates() method: 

@javax.persistence.Entity
@Inheritance(strategy = InheritanceType.TABLE_PER_CLASS)
public class Base implements Serializable{

   ...

2. @PreUpdate and @Prepersist in hibernate/JPA (using session)    stackoverflow.com

I've hit a blocker adding a fix to an existing project.the main problem is that i'll like to use @Prepersist and @PreUpdate in the POJO to take care of LastModified field ...

3. JPA / Hibernate question ( @PrePersist, Session API clarification)    stackoverflow.com

I am working currently on creation of some tests on my app. I have faced an issue which needs to involve @PrePersist feature from JPA. Unfortunately those interceptors aren't fired, while persisting, updating ...

4. Help create AspectJ equivellent to @PrePersist and @PreUpdate for audit use case    stackoverflow.com

In JPA, there is @PrePersist and @PreUpdate annotations that allow operations before CRUD operations. I am trying to find out the ApsectJ equivalent to this. My use case is a JPA application that ...

5. JPA are being ignored but the @PrePersist and @PreUpdate work fine    stackoverflow.com

I ran into strange problem. I have the whole domain model defined in the orm.xml file. All my entities in my project are just simple POJOs (no jpa annotations at all). ...

6. JPA not creating columns when using @PrePersist & @PreUpdate    stackoverflow.com

I am attempting to resolve the same old issue with having a reusable set of Created and Updated time stamp fields. I have attempted to implement this solution: using ...

7. @PrePersist / @PreUpdate not firing    forum.hibernate.org

8. Override or ignore @PrePersist via configuration -possible?    forum.hibernate.org

I am writing a stand-alone add-on module for an application that uses a library with JPA-annotated domain entity objects. The application itself is already in Production, it has been deployed at the customer site, and no libraries should be modified/redeployed. Here's the issue I am facing. My new module has to use the exact same version/instance of the domain library the ...