The previous votes were cancelled after an issue was found with TomEE 7.1.2
(https://issues.apache.org/jira/browse/TOMEE-2758) and the release for
7.0.7 had incorrect artifacts. This binary should be the same as the
previous one, with the exception of the addition of jakarta.activation jar,
which was included in TomEE 7.1.1 and removing it potentially would cause
Please note that this version does not include Xalan or serializer as TomEE
does not require these for normal operation. If your application uses
Xalan, you will need to include it, and its dependencies (e.g. serializer)
in your application itself.
[+1] Yes, release it
[+0] Not fussed
[-1] Don't release, there's a showstopper (please specify what the
Tried this Apache TomEE+ 7.1.2 with plenty of web apps, on Linux
CentOS 7.6 & Windows Server 2016, with various AdoptOpenJDK (8 Open9,
11 OpenJ9 and 11 HotSpot flavors).
Found no other issues than JAX-RS ones caused by few of our Java web
methods signatures not being strictly Java Beans-compliant.
For example, we had Java beans using isXXX() method when XXX is a
java.lang.Boolean instead of native type boolean. Also we had some
'case' errors like getxXX() accessor for property XXX. These mistakes
in our beans were accepted by TomEE+ 7.1.1, but not by 7.1.2 which is
more strict ((like TomEE 8.0.x), and we know that it's our webapps'
fault, hence my +1 anyway.
Le mer. 8 janv. 2020 à 11:23, Jonathan Gallimore
<[hidden email]> a écrit :