This project shows Hibernate's implementation of Jakarta Data used from Quarkus RESTEasy Classic.
Here we observe:
- Jakarta Persistence annotations used to declare and map entity types like
Book
,Author
, andPublisher
, - Jakarta Data annotations used to declare a
Library
repository acting as a facade to Hibernate'sStatelessSession
, and - JAX-RS annotations used to declare the frontend
LibraryResource
, withLibrary
injected via CDI.
- Quarkus 3.15.1 or above, with RESTEasy Classic and Jackson
- Jakarta Data 1.0.0
- Hibernate Metamodel Generator 6.6.0.Final
You can run your application in dev mode that enables live coding using:
./mvnw compile quarkus:dev
NOTE: Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.
The application can be packaged using:
./mvnw package
It produces the quarkus-run.jar
file in the target/quarkus-app/
directory.
Be aware that it’s not an über-jar as the dependencies are copied into the target/quarkus-app/lib/
directory.
The application is now runnable using java -jar target/quarkus-app/quarkus-run.jar
.
If you want to build an über-jar, execute the following command:
./mvnw package -Dquarkus.package.type=uber-jar
The application, packaged as an über-jar, is now runnable using java -jar target/*-runner.jar
.
You can create a native executable using:
./mvnw package -Dnative
Or, if you don't have GraalVM installed, you can run the native executable build in a container using:
./mvnw package -Dnative -Dquarkus.native.container-build=true
You can then execute your native executable with: ./target/data-demo-quarkus-mvn-1.0-SNAPSHOT-runner
If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.