andrey alekseenko

Just some cleanup no new functionality

When should play! migrate to jakarta-jpa?

6

[JPA 3.0](https://jakarta.ee/specifications/persistence/3.0/) don't have backward compatibility with 1.x-2.x versions because of renaming of all packages. As possible solution I see extracting play.db.jpa package in independent module and make two versions...

https://github.com/playframework/play1/blob/9308a98f897f6c172b36f06fec56d4ef2d81e7e7/framework/src/play/jobs/Job.java#L246-L247 should looks like this ```java after(); onSuccess(); return result; ```

cleanup code

2

* use primitive type instead of wrapper; * close keystore after loading; * extract methods and constants for readability; * X509TrustManager#getAcceptedIssuers() must return non null value.

Migration of framework infrastructure classes to modern mechanisms provided by the JVM, replacing custom implementations. The goal could be considered to replace all framework specific implementations of abstractions that were...