Your annotations look fine. Here are the things to check: make sure the annotation is javax.persistence.Entity, and not org.hibernate.annotations.Entity. The former makes the entity detectable. The latter is just an addition. if you are manually listing your entities (in persistence.xml, in hibernate.cfg.xml, or when configuring your session factory), then make sure you have also listed … Read more
I found this by doing a search on “Hibernate fixtures” : Hibernate will create the database when the entity manager factory is created (actually when Hibernate’s SessionFactory is created by the entity manager factory). If a file named import.sql exists in the root of the class path (‘/import.sql’) Hibernate will execute the SQL statements read … Read more
Explanation: A ClassDefNotFound exception means that your program was unable to find a required .class file from the referenced libraries. In your case the hibernateX.jar file isn’t packaged inside your war file. What you need to do is to add it to the WEB-INF/lib folder of your war file. Solution (using IntelliJ): open up project … Read more
An entityManager manages a persistence context, in other word an in memory snapshot of the database state. See What is a persistence object? Every object loaded using the entityManager will be in managed state (see entity life cycle) until you close the EM. When an entity is managed, all change made to it will be … Read more
Why do you need to do it in the query? Why not just handle it in the java code. for example: From RandomThing Where randomTime is not null and randomTime >= :currentTimestamp and randomTime <= :maxTimestamp And then just set the parameters.
As @Korgen mentioned in comments hibernate-validator-5.x.x isn’t compatible with validation-api-1.0.x. This is because of moving to new specification JSR-303 -> JSR-349. There are two ways to solve this issue: 1. Downgrade hibernate validator version (which is implements JSR-303): <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> <version>4.3.1.Final</version> </dependency> 2. If you don’t want to move back from hibernate validator 5 … Read more
Dialect means “the variant of a language”. Hibernate, as we know, is database agnostic. It can work with different databases. However, databases have proprietary extensions/native SQL variations, and set/sub-set of SQL standard implementations. Therefore at some point hibernate has to use database specific SQL. Hibernate uses “dialect” configuration to know which database you are using … Read more
Two easy options spring to mind: Evict oldEntity before saving newEntity Use session.merge() on oldEntity to replace the version in the session cache (newEntity) with the original (oldEntity) EDIT: to elaborate a little, the problem here is that Hibernate keeps a persistence context, which is the objects being monitored as part of each session. You … Read more
Updated answer for Hibernate Search 6 Short answer: don’t use wildcard queries, use a custom analyzer with an EdgeNGramFilterFactory. Also, don’t try to analyze the query yourself (that’s what you did by splitting the query into terms): Lucene will do it much better (with a WhitespaceTokenizerFactory, an ASCIIFoldingFilterFactory and a LowercaseFilterFactory in particular). Long answer: … Read more
@axtavt: It appears as if your answer wasn’t correct. I’ve just received an email from the authors of “Pro JPA 2.0”, who were also working on the JPA spec themselves. “In your example the Zip class has a relationship to a Country: public class Zip implements Serializable { @Id @Column(name = “code”) private String code; … Read more