Ex­tremeTrans­ac­tions 5.0.107

Fea­ture188756

Spring Boot Starter

Con­tributed by the Spring (Boot) team, we are hap­py to an­nounce our new Spring Boot starter mod­ule! You can now use our re­leas­es 5.0 with the lat­est re­leas­es from Spring Boot.

Tech­ni­cal de­tails

Our re­leas­es 5.0 were not com­pat­i­ble with the Spring Boot starter code as it was im­ple­ment­ed by the Spring Boot team (and in­clud­ed in the "na­tive" starters for Spring Boot).

So based on a gen­er­ous con­tri­bu­tion from the Spring Boot team and Piv­otal, we now have our own starter mod­ule for you to use: just add trans­ac­tions-spring-boot-starter to your pom and off you go.

See https://www.atom­ikos.com/Doc­u­men­ta­tion/SpringBootIn­te­gra­tion for ad­di­tion­al de­tails.

Changes im­pact­ing client API

No oth­er changes: we have pre­served the Spring Boot con­fig­u­ra­tion op­tions.

Fea­ture194218

Restruc­ture mod­ule trans­ac­tions-spring­boot2

This mod­ule has been re­named and part of the code in­side has been moved.

Tech­ni­cal de­tails

With the new Spring Boot starter mod­ule (see 188756 above) the name of mod­ule trans­ac­tions-spring­boot2 seemed awk­ward and over­lap­ping with the Spring Boot starter code. So we have de­cid­ed to:

• Move the meta­da­ta class­es from pack­age com.atom­ikos.spring­boot.au­to­con­fig­ure.jdbc.meta­da­ta from mod­ule trans­ac­tions-spring­boot2 into the new mod­ule trans­ac­tions-spring-boot (this mod­ule was added per 188756 above).
• Re­name the mod­ule trans­ac­tions-spring­boot2 to trans­ac­tions-spring-boot-log­cloud to re­flect the true in­ten­tion of the re­main­ing code in this mod­ule.

Changes im­pact­ing client API

This is a break­ing change if you were us­ing trans­ac­tions-spring­boot2 al­ready.

Bug190245

Com­pat­i­bil­i­ty with JDK 11

Sever­i­ty:	4
Af­fect­ed ver­sion(s):	4.0.x, 5.0.x

De­scrip­tion

You can now run our ex­am­ple pro­grams with JDK 11.

Tech­ni­cal de­tails

Our ex­am­ples did not build well with JDK 11 due to the new Java mod­ule sys­tem in­tro­duced, and the fact that some pack­ages are no longer vis­i­ble (by de­fault) in the JDK. This has now been fixed.

Changes im­pact­ing client API

None: there is a sep­a­rate maven build pro­file that ac­ti­vates it­self when a re­cent JDK is found, and tunes the mod­ules ac­cord­ing­ly.

Is­sue194408

Javadoc is­sue dur­ing re­lease up­load

Sever­i­ty:	4
Af­fect­ed ver­sion(s):	5.0.107

De­scrip­tion

This re­lease does not in­clude the full javadoc.

Tech­ni­cal de­tails

The javadoc gen­er­a­tion failed dur­ing the up­load of the re­lease due to in­com­pat­i­bil­i­ty is­sues with the Spring Boot starter's in­te­gra­tion tests. To avoid ad­di­tion­al de­lays, we have for now up­loaded this re­lease with­out most of the javadoc.

About Sever­i­ty

The sever­i­ty lev­els we use are de­fined in our sup­port terms and con­di­tions.