 68 | To open and run the JPA Web Application tutorial project in IntelliJ IDEA: Download and extract the project zip file: JPA Web Application - Maven Project (6KB). Open the project in IntelliJ IDEA: Select File > Open Project.... Select the guestbook-web directory and click OK. Define the Server |
66 | To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the tutorial package node (in the [Projects] window) and selecting New > Java Class... Enter Point as the class name - use exactly that case sensitive |
66 | ] MEMBER [OF] and the [NOT] LIKE operator. Logical operators: AND, OR, NOT. In addition, JPA queries |
66 | .Object class in queries (as an extension to JPA), so the following query can be used to delete |
66 | The way a field of a persistable class is managed by JPA can be set by the following annotations: Additional annotations (and enum) are designated for enum fields: Other additional annotations (and enum) are designated for date and calendar fields: Chapter 2 of the ObjectDB manual explains how to use all the above annotations. |
66 | The following subsections explain how to use JPA for CRUD database operations: |
66 | The syntax of the Java Persistence Query Language (JPQL) is very similar to the syntax of SQL. Having a SQL like syntax in JPA queries is an important advantage because SQL is a very powerful query language and many developers are already familiar with it. The main difference between SQL and JPQL |
66 | The following annotations can mark methods as JPA callback methods: The Lifecycle Events section of the ObjectDB Manual explains how to use all these annotations on callback methods and with listener classes. |
66 | Relationships are persistent fields in persistable classes that reference other entity objects. The four relationship modes are represented by the following annotations: Unlike ORM JPA implementations, ObjectDB does not enforce specifying any of the annotations above. Specifying a relationship |
66 | The following interfaces and enum represent types in the JPA Metamodel API: See the Metamodel Type Interface Hierarchy section for more details and examples. |