jakarta.ee | Jakarta EE is the future of cloud native Java | Static Site Generator library

I'm trying to parse expressions from the Jakarta Expression Language. In summary, it is a simplified Java expressions, with addition of a few things:

• Support for creating maps like: {"foo": "bar"}
• Support for creating lists and sets like: [1,2,3,4] {1,2,3,4}
• Use some identifiers instead of symbols, like: foo gt bar (foo > bar), foo mod bar(foo % bar), and so on.

I'm struggling in the last bit, where it always understands the "mod", "gt", "ge" as identifiers instead of using the expression that has the "%", ">", ">=".

I'm new to ANTLR. My grammar is based on the Java grammar in the https://github.com/antlr/grammars-v4/tree/master/java/java and the JavaCC provided by: https://jakarta.ee/specifications/expression-language/4.0/jakarta-expression-language-spec-4.0.html#collected-syntax

I'm trying to upgrade a legacy Java EE application to Jakarta EE 8 on a Wildfly server. Most of the upgrade has gone smoothly since 8 doesn't swap the package names to jakarta yet. However, some of our code is using classes from Oracle's com.sun.faces package. These classes appear to be included in the Jakarta EE Faces API specification, but they are not included in our project when I use the following Maven dependency:

I see that Apache Tomcat 10 (alpha) is now available. The major feature there is support for Jakarta EE 9 where package names for APIs have changed from javax.* to jakarta.*. Jakarta EE 9 now has a milestone release available.

Can the current versions of Vaadin Flow (14 or 16) be made to work with the new Jakarta 9 and its name changes?

In a Jakarta EE 8 environment: Is it possible to define a ("portable JNDI") data source at EAR level [1] in application.xml and use this data source as JTA data source in the persistence.xml inside a library/JAR module?

Purpose: Creating a common JAR module that defines JPA entities together with corresponding "repositories", so that this JAR module can be used by multiple WAR modules (e. g. a RESTful API and a UI module) and package this modules as an EAR that is deployable to multiple application servers.

With the following attempt/method (for a full example I created a simple git repo [2]), the deployment of such an EAR fails (at least with Payara and WildFly).

Attempt/Method

Let's say there's an application consisting of 2 WAR modules and both WAR modules uses a shared JAR module, so that there is a application structure something like this:

Bean Validation specification defines:

Constraint annotations must define a payload element that specifies the payload with which the constraint declaration is associated. The type of the payload parameter is Payload[].

...

I would like to understand why some Jakarta EE specifications are empty.

For example for Jakarta Annotations specifications is composed by a Disclaimers and a quick description (3 lines), however there is Javadoc.

When JCP was in charge of J2EE speficiations it was more documented, still taking example on annotations specifications. When I read Jakarta EE 8 plateform specification I find more informations but this is still lower them JCP.

Then I finish to find specifications in the github account of the Eclipse EE4J with lot of details (remark this is not easy to find a particular specifications with the hudge number of repositories).

I would like to know if some specifications coming from jakarta ee web site are empty because these is exactly the sames of J2EE or Eclipse decide to prefer javadoc support and Why there is no link to github specification ?

I am having issues with decoding/using/verifying the passed JWT to my Java EE 8 with MicroProfile 2.0.1 backend running on Payara 5.183. The React frontend application passes the JWT token, which is obtained from Keycloak, to the backend as Authorization: Bearer eyXJS... The backend is configured to verify the JWT token as defined in the MicroProfile JWT Auth Spec 1.1 with the following microprofile-config.properties in src/main/resources/META-INF: