Matthias Müller <matthias.mueller@appng.org> 2020-03-31
The appNG development team is happy to announce the release of appNG 1.21.0.
With more than three dozen fixed issues, this release comes with a large set of noteworthy changes.
For a full list of changes check out the release notes on JIRA.
Let’s take a closer look at those.
In the past, the good old Ehcache has served us well when it came to caching.
Nonetheless, there were some limitations. To remove these, Hazelcast has been chosen as the new caching solution.
|
Tip
|
When upgrading an existing appNG instance, make sure hazelcast.xml is placed in |
Hazelcast enables appNG to provide a configurable page cache for each site, allowing to define a custom TTL for different paths and Ant-style path matching.
Check out the section about caching in the platform administration guide for details.
Another great benefit is the support for Spring’s Caching abstraction by providing a CacheManager that is available out-of-the-box for every application that want’s to use it.
Just add @EnableCaching to your @Configuration (<cache:annotation-driven/> when using beans.xml) and add some caching annotations to your business logic and you are ready to go!
Regarding user management, a few improvements have been made.
A user account now can be locked manually, automatically after X login attempts or after X days of inactivity. It can also have an expiry date.
It is now possible to define whether a user may or must (not) change it’s password, or if the password needs to be recovered.
For details about managing users and password policies, check out the administration guide.
The rules for how a password must be composed can now be configured in detail. KUDOS go to the great Passay library here.
Like for most minor releases, dependencies have been updated for this release:
|
Important
|
Note that also some new dependencies were added, so make sure you are using the latest version of the BOM |
For appNG’s repository mechanism, some performance improvements where made.
Scanning for artifacts is now way much faster. The same applies when uploading artifacts with appNGizer, that now also is able to install hidden an privileged applications.
The existing support for MySql now also includes version 8.x, which (in combination with mysql-connector-java 8.x) allows using the Java 8 Date Time API for JPA entities.
New on the other hand is the support for PostgreSQL >= 10 and MariaDB 10.x (useMysqlMetadata=true must be used for hibernate.connection.url in appNG.properties).