Name: sample.javaee7.jta
Owner: WASdev
Description: Demonstrates the use of @ Transactional annotations to declaratively control transaction boundaries, along with using the @ TransactionScoped annotation to scope a bean lifecycle to a transaction.
Created: 2016-02-11 15:16:35.0
Updated: 2017-06-07 20:18:58.0
Pushed: 2017-12-07 16:36:10.0
Size: 100
Language: Java
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
This application demonstrates the use of @Transactional annotations to declaratively control transaction boundaries, along with using the @TransactionScoped annotation to scope a bean lifecycle to a transaction.
The sample can be built using Apache Maven. In the directory where you cloned the repository issue the following command to build the source.
$ mvn install
Then, in the jta-webapp directory issue the following command to run it on a Liberty server.
$ mvn liberty:run-server
The WebSphere Development Tools (WDT) for Eclipse can be used to control the server (start/stop/dump/etc.), it also supports incremental publishing with minimal restarts, working with a debugger to step through your applications, etc. WDT also provides:
Installing WDT on Eclipse is as simple as a drag-and-drop, but the process is explained on wasdev.net.
The sample can be built using Gradle and the Liberty Gradle Plug-in. In the directory where you cloned the repository issue the following command to build and run the project.
$ gradle build
To start the application use the command:
$ gradle libertyStart
To stop the application use the command:
$ gradle libertyStop
Verify that a Derby JDBC Provider instance exists. In the administrative console, click Resources > JDBC > JDBC providers.
If that provider does not exist, create one with a Connection pool datasource implementation type, and point to the Derby.jar file; for example: ${WAS_INSTALL_ROOT}/derby/lib
Verify that a Default datasource instance is configured. Click Resources > JDBC > Data sources.
If that datasource does not exist, create one with the name “Default datasource” and the JNDI name “DefaultDatasource” that points to the Derby JDBC Provider and “${WAS_INSTALL_ROOT}/derby/DefaultDB” database.
To create the actual database, remotely connect to your machine hosting WebSphere Classic using SSH.
Navigate to ${WAS_INSTALL_ROOT}/derby/bin/embedded/
Run “./ij.sh”. When you see the prompt “ij>“, enter the following command: $ connect 'jdbc:derby:DefaultDB;create=true';
The default Derby database is created in the following directory: ${WAS_INSTALL_ROOT}/derby/DefaultDB
© Copyright IBM Corporation 2016, 2017.
This information contains sample code provided in source code form. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample code is written.
Notwithstanding anything to the contrary, IBM PROVIDES THE SAMPLE SOURCE CODE ON AN “AS IS” BASIS AND IBM DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. IBM SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR ECONOMIC CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR OPERATION OF THE SAMPLE SOURCE CODE. IBM SHALL NOT BE LIABLE FOR LOSS OF, OR DAMAGE TO, DATA, OR FOR LOST PROFITS, BUSINESS REVENUE, GOODWILL, OR ANTICIPATED SAVINGS. IBM HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS OR MODIFICATIONS TO THE SAMPLE SOURCE CODE.