The bmt quickstart demonstrates Bean-Managed Transactions (BMT), showing how to manually manage transaction demarcation while accessing JPA entities.
The bmt quickstart demonstrates how to manually manage transaction demarcation while accessing JPA entities in {productNameFull}.
On occasion, the application developer requires finer grained control over the lifecycle of JTA transactions and JPA Entity Managers than the defaults provided by the Jakarta EE container. This example shows how the developer can override these defaults and take control of aspects of the lifecycle of JPA and transactions.
When you run this example, you are presented with a Use bean managed Entity Managers checkbox.
-
If you check the checkbox, it shows the developer responsibilities when injecting an Entity Manager into a managed (stateless) bean.
-
If you uncheck the checkbox, shows the developer responsibilities when using JPA and transactions with an unmanaged component.
This example shows how to transactionally insert key value pairs into the database and demonstrates the requirements on the developer with respect to the JPA Entity Manager.
The application will be running at the following URL: http://localhost:8080/{artifactId}/.
You are presented with a simple form for adding key/value pairs, and a checkbox to indicate whether the updates should be executed using an unmanaged component. Effectively this will run the transaction and JPA updates in the servlet, not session beans. If the box is checked then the updates are executed within a session bean method.
-
To list all pairs leave the Key input field empty.
-
To add or update the value of a key, fill in the Key and Value input fields.
-
Click the Submit button to see the results.
You will see the following warnings in the server log. You can ignore these warnings.
WFLYJCA0091: -ds.xml file deployments are deprecated. Support may be removed in a future version.
HHH000431: Unable to determine H2 database version, certain features may not work