STAGING - 22.0.0.2 GA Blog

[ryan-storey]

Draft: https://blogs-draft-openlibertyio.mybluemix.net/blog/2022/02/15/ga-release-post.html

[ryan-storey]

Added all devs to review their respective blog issue/bug fix sections.

[dmuelle]

a few suggestions- in general, it's better to address the reader directly as "you" rather than referring to a 3rd person "user" (unless you expect the reader and the user to be different people)

[dmuelle]

minor nit but I don't think you need quotes around "default", here or elsewhere

[dmuelle]

shouldn't this be an anchor-link to the #bugs section of this post? The GitHub list is already linked from line 132

[dmuelle]

prob not an issue for today but should the GA blog template include podman alternative to docker?

[dmuelle]

don't need commas around the dependent clause here

This new JPA enhancement adds the ability to declare default JPA persistence properties to all container-managed persistence contexts as a Liberty server.xml configuration.

[dmuelle]

suggested edit

Previously, to set persistence property for all persistence.xml configuration files, you had to update each persistence.xml file in all applications.

[dmuelle]

With this enhancement, you can specify persistence properties in the server.xml file that will propagate to all container-managed persistence units for all applications installed on that server.

[dmuelle]

suggested edit

To start using the new feature, add the new defaultProperties element to the jpa element configuration in your server.xml file. Use this element to specify the persistence properties that you want to apply to all container-managed persistence units:

[dmuelle]

don't need a comma

These defaultProperties integration-level persistence properties will be supplied to the persistence provider specified when the PersistenceProvider.createContainerEntityManagerFactory method is called by the JPA Container.

[epj]

JSP item looks good

[Azquelt]

This doesn't really describe what the issue was. I'll rewrite it tomorrow morning.

[Azquelt]

Also, some scenarios will still be impacted by OpenLiberty/open-liberty#19991 which will be fixed in the next release - should that be mentioned here?

[mbroz2]

Suggested change

	* link:https://github.com/OpenLiberty/open-liberty/issues/19860[Updating MicroProfile versions on server.xml causes issues with install manager]
	+
	Previously, updating to MicroProfile 5.0 in the `server.xml` and `pom.xml` would cause issues with the install manager. After resolving the features which are needed, the `RepositoryResolver` has to create lists of which features to install. There's a list of everything needed for each requested feature and one for each auto-feature. When creating the install lists, it traversed the dependencies but stopped traversing when it founds a dependency which was installed. If `distributedMap-1.0` is installed but `distributedMapInternal-1.0` is not, it stops traversing dependencies when it hits `distributedMap-1.0` and `distributedMapInternal-1.0` is not added to the list. This bug was fixed by tracing down the entire dependency tree, building the list and finally removing any features which are already installed.

[Azquelt]

Here's an updated description for OpenLiberty/open-liberty#19860. I'm not sure whether you want to include this or not, since the fix for OpenLiberty/open-liberty#19991 (which has similar symptoms) won't be included until next release.

• link:https://github.com/OpenLiberty/open-liberty/issues/19860[Updating MicroProfile versions on server.xml causes issues with install manager]

In situations where some features are already installed, running featureUtility installServerFeatures would not install all the features required to start the server. Trying to start the server would result in an error like this:

[INFO] [ERROR ] CWWKF0044E: The cdi-3.0 and io.openliberty.distributedMapInternal-1.0 features cannot be loaded at the same time. The cdi-3.0 feature of Jakarta EE 9 is incompatible with the io.openliberty.distributedMapInternal-1.0 feature of Java EE 6. The microProfile-5.0 and microProfile-5.0 configured features include an incompatible combination of features. Your configuration is not supported. Update the configuration to use features that support either the Jakarta EE or Java EE programming models, but not both.

One example where the problem would occur is if the openliberty-jakartaee8 package was extracted, a server was created which required jakartaee-9.1 and featureUtility installServerFeatures was run against that server.

The problem was fixed by updating the install resolver to ensure that the right versions of tolerated dependencies are added to the list of features to install, even if the feature that declares the dependency is already installed.

Note that there is another issue link:https://github.com/OpenLiberty/open-liberty/issues/19991[featureUtility does not pass all features from server.xml to repository resolver] which is still present in this release which can cause similar symptoms if some of the features listed in the server.xml are already installed but others are not.