The materials on this page are provided by the Maintenance Lead of this JSR
for evaluation and feedback.
These materials are not final, and are subject to change
as the JSR progresses through the process.
Java Transaction API Maintenance Release 1.3
Maintenance review of the JAVA Transaction (JTA) API 1.3 Specification
Stephen Felts, Oracle Corporation
Comments should be sent to firstname.lastname@example.org
Rationale for Changes:
Make it easier to use JTA with Java SE 9 and above.
Removal of the javax.transaction.xa package
This package will be subsumed into the Java Platform JSR and will no longer be part of the JTA specification:
Java SE has provided a subset of JTA since Java SE 1.3
javax.transaction.xa (XA) supports XA transactions in JDBC and is co-located with JDBC in the java.sql module in Java SE 9. Because the java.sql module is not upgradeable, it is not possible for a standalone version of JTA to override the Java SE version of the XA package, but this is generally acceptable to applications because the XA package has been stable for many years and the Java SE version is identical to the JTA javax.transaction.xa package
Eliminates the split package issue as the Java SE java.sql module provides javax.transaction.xa
Allows JTA to be specified on the module path
The java.transaction module in Java SE 9 is an upgradable module, and used by modules such as java.corba
Provides for the use of the full version of JTA, which includes additional types that are not in Java SE, that may be required by Java EE applications
Specify that the module name for JTA is java.transaction
This allows JTA to have a stable module name making it easier for applications to migrate to Java SE 9 and above.
Is the schedule for the JSR publicly available, current, and updated regularly? Not at this time.
Can the public read and/or write to a wiki for the JSR?
Not at this time
Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
We do not have a wiki currently set up. However we use https://javaee.groups.io/g/jta-spec for discussion of this specification.
Have you spoken at conferences and events about the JSR recently?
Are you using open-source processes for the development of the RI and/or the TCK?
Glassfish, which is hosted at https://github.com/javaee/glassfish, is used as the JTA RI. There is a standalone TCK for JTA, which is currently not opened sourced
What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state.
Where is the publicly-accessible document archive for your Expert Group?
Community Files under the Community tab.
Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR?
Do you have a Twitter account or other social networking feed which people can follow for updates on your JSR?
Which specific areas of feedback should interested community members (such as the Adopt-a-JSR program) provide to improve the JSR (please also post this to your Community tab)?
Since this is focused on integration with Java SE 9 and later releases, integration experience is relevant to this MR.
Transparency survey from August 2008:
RI is available as part of http://glassfish.dev.java.net
Recommended Areas for Providing Feedback
Use @Transactional on different Java EE components
Write @TransactionScoped beans and inject in bean-managed and container-managed transactions
Try integration with other Java EE technologies - such as EJB, CDI, JPA, and Servlets.