| Re: [jta-dev] EE9 Blocker? Java EE 7 (JTA 1.1 -> JTA 1.2) seems to have lost some information, do we need/want to do something for EE9? |
| Hi Lance and Tom, Yes, I see what happened. In 1.1 the following 3 mods were added to the spec but not to the javadoc…
The first two pertain to the same subject and the last is the one being cited. Indeed the idea in 1.2 was to reduce redundancy and get the javadoc out of the spec and unfortunately since the javadoc wasn’t synced with the spec in 1.1 these items were lost. That is a shame, and a good catch on Tom’s part, but since the differences are quite minimal and really just clarifications on implicitly known behaviors I do believe the behavior is defined and there is no need for any changes. Just to elaborate a bit… The first two deal with making it clear that a change in tx timeout affects future txs only and not those in situ /in-flight. This is true of all implementations. The existing javadoc states “Modify the timeout value that is associated with transactions started by the current thread with the begin method.” . I think we are safe here. The third/cited case is covered by the fact that the existing javadoc states “This call is executed with the transaction context of the transaction that is being committed.” and therefore implicitly any unchecked exception would result in marking for rollback. (Technically it should’ve read “thrown by a registered Synchronization’s beforeCompletion method” instead of “thrown by a registered Synchronization” anyway as that is not true for afterCompletion) Regards, Paul
|