What does this PR do?

As dicussed on the mailing list a few months ago [1], building TomEE with Java 11 fails because of two classes, which depend on CORBA.

The places in the code-base with CORBA related access are:

org.apache.openejb.core.OrbFactory
org.apache.openejb.client.corba.Corbas

This PR aims to handle these two classes by generating them via ASM at compile-time during the Maven build (as suggested by @dblevins).

For reference, I have attached a version of the decompiled byte-code generated by ASM:

• OrbFactory.asm.decompiled.txt
• Corbas.asm.decompiled.txt

If this is merged, [2] will be obsolete (due to license issues as discussed in [1]].

References

• [1] https://www.mail-archive.com/[email protected]/msg14097.html
• [2] PR: https://github.com/apache/tomee/pull/664

What does this PR do?

• Adds unit tests to reproduce TOMEE-2968 (also affects 7.0.x and 7.1.x)
• Single opening curly braces are stripped away in property values as we treat them as suffix placeholders (even in the case, we did not have an opening curly brace). PR proposes a related fix.

References

• https://issues.apache.org/jira/browse/TOMEE-2968
• https://markmail.org/message/vxmm7t5sl33zr4wq

batchee and jcs added in Plume to reflect Plus flavor

removed xml api from from Plume to reflect Plus flavor remains some jar refs in jar scan exclusions (xerces, xml-apis)

Fixed the table in the pages according asciidoc syntax. Added new/old page (apache-tomee.adoc) by your relevance. One page (spring-ejb-and-jpa.adoc) were with broken links to old example project (spring-integration) that not belongs to tomee, so the old example project was bring to tomee and links were fixed.

Link to JIRA: https://issues.apache.org/jira/browse/TOMEE-55

JIRA: https://issues.apache.org/jira/browse/TOMEE-2917

Fix Summary: Change all WrappingMessage to implements Serializable and add unique serialVersionUID.

Notes: There is a business use case which need to persist WrappingTextMessage (or TextMessage) into database. Required WrappingTextMessage to become serializable. TextMessage implementation by both IBM Websphere and Weblogic are serializable. https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.javadoc.doc/WMQJMSClasses/com/ibm/jms/JMSMessage.html https://docs.oracle.com/middleware/12213/wls/WLAPI/weblogic/jms/common/TextMessageImpl.html

This was little to big but next time will make JIRA ticket for each module before start coding

Modules worked in :

openejb-multicast, openejb-axis, openejb-common-cli, openejb-ejbd, openejb-server, openejb-webservices, tomee-common,

Usage of dimond operator, remove unused import and Java Doc

…basic.password URL parameter

A double-decode bug caused URLDecode to be applied twice to parameters passed in via URL including basic.username and basic.password. The parameters were automatically decoded by the call to URI.getQuery() then again as each parameter was parsed and added to the returned Map in MulticastConnectionFactory.URIs.parseQuery(). parseQuery() splits the query string on the ampersand character then explictly URLDecode's each value. Since URI.getQuery() had already decoded the basic.password parameter, the splitting process in parseQuery truncated the password at the first ampersand character.

Instead, URI.getRawQuery() should be called to get the still URLEncoded query string. The splitting and subsequent decoding in parseQuery() then correctly extracts the full password from the query string.

PR contains failing unit test & fix.

Tomcat does not include JSTL nor the javax.security.enterprise.* packages. The documentation should reflect that, and should have these specs into WebProfile.

This is a live document until TomEE 8.0.0 is released. Till that point of time, any updates (either additions/removal) of Java versions support can be done to this document

This PR modifies the dependencies for plume and plus, adding the following dependencies:

• Jakarta MVC API
• Krazo CXF

this allows an application to avoid depending on the implementation choices (CXF) now an app can depend on the API instead.

** please build on CI before merging **

This PR modifies the dependencies for plume and plus, adding the following dependencies:

• Jakarta MVC API
• Krazo CXF

this allows an application to avoid depending on the implementation choices (CXF) now an app can depend on the API instead.

Tomcat 10.0 (EE 9) has reach EOL

EDIT: reworked this PR for TomEE v10 instead.

this updates tomcat to 10.1.4

old comment:

needs either

• TomEE 9.x become EOL itself in favor of TomEE 10.x OR
• Update TomEE with tomcat 10.1.2 (EE 10) AND TomEE 9.x goes Jakarta EE 10 compliant OR
• Update TomEE with tomcat 10.1.2 (EE 10) AND TomEE 9.x stays Jakarta EE 9 compliant (believed better option)

Quote from Tomcat website

Apache Tomcat 10.1.x Apache Tomcat 10.1.x is the current focus of development. It implements the Servlet 6.0, JSP 3.1, EL 5.0, WebSocket 2.1 and Authentication 3.0 specifications (the versions required by Jakarta EE 10 platform).

Apache Tomcat 10.0.x Apache Tomcat 10.0.x implements the Servlet 5.0, JSP 3.0, EL 4.0, WebSocket 2.0 and Authentication 2.0 specifications (the versions required by Jakarta EE 9 platform).

Users of Tomcat 10.0 should be aware that Tomcat 10.0 has now reached end of life. Users of Tomcat 10.0.x should upgrade to Tomcat 10.1.x or later.