(tomcat) branch main updated: Update CXF

[remm]

This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/main by this push:
 new 7d19b0f92c Update CXF
7d19b0f92c is described below

commit 7d19b0f92c2e582528ac1f922721f8e1c02d381e
Author: remm 
AuthorDate: Wed Mar 27 23:12:25 2024 +0100

Update CXF

Still EE 10 compatibility issues.
---
 modules/cxf/pom.xml  | 4 ++--
 modules/cxf/src/main/java/tomcat/cxf/JsonBean.java   | 6 +++---
 modules/cxf/src/main/resources/META-INF/beans.xml| 6 +++---
 modules/cxf/src/main/resources/META-INF/web-fragment.xml | 8 
 4 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/modules/cxf/pom.xml b/modules/cxf/pom.xml
index 2f3690c4ef..9aa15ecce1 100644
--- a/modules/cxf/pom.xml
+++ b/modules/cxf/pom.xml
@@ -29,7 +29,7 @@
 Apache CXF for Apache Tomcat CDI
 Apache CXF packaged for Apache Tomcat CDI
 
-4.0.3
+4.0.4
 jar
 
 
@@ -97,7 +97,7 @@
 org.apache.maven.plugins
 maven-compiler-plugin
 
-21
+17
 
 
 
diff --git a/modules/cxf/src/main/java/tomcat/cxf/JsonBean.java 
b/modules/cxf/src/main/java/tomcat/cxf/JsonBean.java
index 88ce138543..019d48cf75 100644
--- a/modules/cxf/src/main/java/tomcat/cxf/JsonBean.java
+++ b/modules/cxf/src/main/java/tomcat/cxf/JsonBean.java
@@ -16,9 +16,9 @@
  */
 package tomcat.cxf;
 
-import javax.enterprise.context.Dependent;
-import javax.ws.rs.Produces;
-import javax.ws.rs.ext.Provider;
+import jakarta.enterprise.context.Dependent;
+import jakarta.ws.rs.Produces;
+import jakarta.ws.rs.ext.Provider;
 
 import org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider;
 
diff --git a/modules/cxf/src/main/resources/META-INF/beans.xml 
b/modules/cxf/src/main/resources/META-INF/beans.xml
index d48340296f..e21852ff29 100644
--- a/modules/cxf/src/main/resources/META-INF/beans.xml
+++ b/modules/cxf/src/main/resources/META-INF/beans.xml
@@ -15,11 +15,11 @@
 See the License for the specific language governing permissions and
 limitations under the License.
 -->
-http://xmlns.jcp.org/xml/ns/javaee;
+https://jakarta.ee/xml/ns/jakartaee;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-   xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee 
http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd;
+   xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee 
https://jakarta.ee/xml/ns/jakartaee/beans_4_0.xsd;
bean-discovery-mode="annotated"
-   version="2.0">
+   version="4.0">



diff --git a/modules/cxf/src/main/resources/META-INF/web-fragment.xml 
b/modules/cxf/src/main/resources/META-INF/web-fragment.xml
index 75ec8dbca6..e55f6921bd 100644
--- a/modules/cxf/src/main/resources/META-INF/web-fragment.xml
+++ b/modules/cxf/src/main/resources/META-INF/web-fragment.xml
@@ -15,11 +15,11 @@
 See the License for the specific language governing permissions and
 limitations under the License.
 -->
-http://xmlns.jcp.org/xml/ns/javaee;
+https://jakarta.ee/xml/ns/jakartaee;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-  xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
-  http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd;
-  version="4.0">
+  xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee
+  https://jakarta.ee/xml/ns/jakartaee/web-app_6_0.xsd;
+  version="6.0">
 tomcat-cxf
 
 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Romain Manni-Bucau]

FYI here is the diff between servlet 5 and 6 API jars:

New API: - jakarta.servlet.ServletConnection Deleted API: -
jakarta.servlet.SingleThreadModel - jakarta.servlet.http.HttpSessionContext
- jakarta.servlet.http.HttpUtils Changed API:
jakarta.servlet.ServletContext Deleted methods: - public abstract
jakarta.servlet.Servlet
jakarta.servlet.ServletContext.getServlet(java.lang.String) throws
jakarta.servlet.ServletException - public abstract java.util.Enumeration
jakarta.servlet.ServletContext.getServletNames() - public abstract
java.util.Enumeration jakarta.servlet.ServletContext.getServlets() - public
abstract void
jakarta.servlet.ServletContext.log(java.lang.Exception,java.lang.String)
jakarta.servlet.ServletRequest Added methods: - public abstract
jakarta.servlet.ServletConnection
jakarta.servlet.ServletRequest.getServletConnection() - public abstract
java.lang.String jakarta.servlet.ServletRequest.getProtocolRequestId() -
public abstract java.lang.String
jakarta.servlet.ServletRequest.getRequestId() Deleted methods: - public
abstract java.lang.String
jakarta.servlet.ServletRequest.getRealPath(java.lang.String)
jakarta.servlet.ServletRequestWrapper Added methods: - public
jakarta.servlet.ServletConnection
jakarta.servlet.ServletRequestWrapper.getServletConnection() - public
java.lang.String
jakarta.servlet.ServletRequestWrapper.getProtocolRequestId() - public
java.lang.String jakarta.servlet.ServletRequestWrapper.getRequestId()
Deleted methods: - public java.lang.String
jakarta.servlet.ServletRequestWrapper.getRealPath(java.lang.String)
jakarta.servlet.SessionCookieConfig Added methods: - public abstract
java.lang.String
jakarta.servlet.SessionCookieConfig.getAttribute(java.lang.String) - public
abstract java.util.Map jakarta.servlet.SessionCookieConfig.getAttributes()
- public abstract void
jakarta.servlet.SessionCookieConfig.setAttribute(java.lang.String,java.lang.String)
jakarta.servlet.UnavailableException Deleted methods: - public
jakarta.servlet.Servlet jakarta.servlet.UnavailableException.getServlet()
jakarta.servlet.descriptor.JspPropertyGroupDescriptor Added methods: -
public abstract java.lang.String
jakarta.servlet.descriptor.JspPropertyGroupDescriptor.getErrorOnELNotFound()
jakarta.servlet.http.Cookie Added methods: - public boolean
jakarta.servlet.http.Cookie.equals(java.lang.Object) - public int
jakarta.servlet.http.Cookie.hashCode() - public java.lang.String
jakarta.servlet.http.Cookie.getAttribute(java.lang.String) - public
java.lang.String jakarta.servlet.http.Cookie.toString() - public
java.util.Map jakarta.servlet.http.Cookie.getAttributes() - public void
jakarta.servlet.http.Cookie.setAttribute(java.lang.String,java.lang.String)
jakarta.servlet.http.HttpServlet Added fields: - public static final
java.lang.String jakarta.servlet.http.HttpServlet.LEGACY_DO_HEAD Added
methods: - public void
jakarta.servlet.http.HttpServlet.init(jakarta.servlet.ServletConfig) throws
jakarta.servlet.ServletException jakarta.servlet.http.HttpServletRequest
Deleted methods: - public abstract boolean
jakarta.servlet.http.HttpServletRequest.isRequestedSessionIdFromUrl()
jakarta.servlet.http.HttpServletRequestWrapper Deleted methods: - public
boolean
jakarta.servlet.http.HttpServletRequestWrapper.isRequestedSessionIdFromUrl()
jakarta.servlet.http.HttpServletResponse Deleted methods: - public abstract
java.lang.String
jakarta.servlet.http.HttpServletResponse.encodeRedirectUrl(java.lang.String)
- public abstract java.lang.String
jakarta.servlet.http.HttpServletResponse.encodeUrl(java.lang.String) -
public abstract void
jakarta.servlet.http.HttpServletResponse.setStatus(int,java.lang.String)
jakarta.servlet.http.HttpServletResponseWrapper Deleted methods: - public
java.lang.String
jakarta.servlet.http.HttpServletResponseWrapper.encodeRedirectUrl(java.lang.String)
- public java.lang.String
jakarta.servlet.http.HttpServletResponseWrapper.encodeUrl(java.lang.String)
- public void
jakarta.servlet.http.HttpServletResponseWrapper.setStatus(int,java.lang.String)
jakarta.servlet.http.HttpSession Deleted methods: - public abstract
jakarta.servlet.http.HttpSessionContext
jakarta.servlet.http.HttpSession.getSessionContext() - public abstract
java.lang.Object
jakarta.servlet.http.HttpSession.getValue(java.lang.String) - public
abstract java.lang.String[]
jakarta.servlet.http.HttpSession.getValueNames() - public abstract void
jakarta.servlet.http.HttpSession.putValue(java.lang.String,java.lang.Object)
- public abstract void
jakarta.servlet.http.HttpSession.removeValue(java.lang.String)

It does not look crazy to get back (without @Override) deleted methods in
Tomcat - most of them are just either "return null" or a delegation to
another method so cost for tomcat is almost 0 for that side.
What I'm not yet sure - didn't have time to check yet - is if the new API
are used directly from jakarta package (if so it would fail running with
servlet 5 api else it will run smoothly and could be a win-win?).

Romain Manni-Bucau

(tomcat-tck) branch main updated: Servlet TCK 6.1.0 has been staged

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git


The following commit(s) were added to refs/heads/main by this push:
 new 4e0f906  Servlet TCK 6.1.0 has been staged
4e0f906 is described below

commit 4e0f9067ae6d2ffac2559c8206361654dc1b02d5
Author: Mark Thomas 
AuthorDate: Wed Mar 27 16:32:33 2024 +

Servlet TCK 6.1.0 has been staged
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index 312a61f..50631e4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -36,7 +36,7 @@
 
 6.0.0
 6.0.0
-6.1.0-SNAPSHOT
+6.1.0
 4.0.0
 2.2.0
 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Romain Manni-Bucau]

Ok, let see if we can maybe have an exceptional certification status with
servlet 6 as an exception but I doubt (but would make everyone happy) :(

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 27 mars 2024 à 14:15, Rémy Maucherat  a écrit :

> On Wed, Mar 27, 2024 at 11:13 AM Romain Manni-Bucau
>  wrote:
> >
> > Le mer. 27 mars 2024 à 10:58, Rémy Maucherat  a écrit :
> >
> > > On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
> > >  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Checkout out TomEE's notifications I realized Tomcat is in a weirdish
> > > > situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1
> > > which
> > > > is Servlet 6.
> > > > It means Tomcat is no more a Servlet 5 friendly option.
> > > >
> > > > I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat
> > > 10.0
> > > > should be maintained and released again - pretty sure we can find
> help if
> > > > desired for that not that far.
> > > > Another option is to restore the deleted methods between servlet 5-6
> in
> > > the
> > > > code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
> > > > Servlet 6 - to pass signature TCK.
> > > >
> > > > Wdyt?
> > >
> > > Nothing. The Tomcat developers (= the committers) determined that the
> > > EE 9 release was useless since the only change is the javax -> jakarta
> > > package renaming. A big task for sure, but that seemed to us this was
> > > more a developer oriented armaggeddon and not something that benefits
> > > our users.
> > >
> > > For reasons that elude my understanding, some other projects like
> > > TomEE thought this was still useful and decided to release full
> > > support for EE 9 rather than go to EE 10 like we did. Our plan about
> > > EE was public. So I guess this is still our problem obviously, but I
> > > don't feel like doing anything about it.
> > >
> >
> > From what I saw on other AsfEE projects, users requested it, nothing more
> > and then you have CVE game.
> >
> >
> > >
> > > BTW, about the last item. Recently, I tried to run CXF on the new EE
> > > 10 APIs (since OWB moved to that). It doesn't work as it uses
> > > deprecated APIs, while IMO it should have moved away from them long
> > > ago. And it's an ASF project, not some hack project somewhere.
> > >
> >
> > This is fixed AFAIK on master (maybe last release, didnt check) so should
> > be fine soon.
>
> I checked and there is a new CXF release from early March.
>
> However, I still get the CDI 4 deprecation removal issue:
> Caused by: java.lang.NoSuchMethodError: 'void
> jakarta.enterprise.inject.spi.BeanManager.fireEvent(java.lang.Object,
> java.lang.annotation.Annotation[])'
> at
> org.apache.cxf.cdi.JAXRSCdiResourceExtension.onStartup(JAXRSCdiResourceExtension.java:167)
>
> This is deprecated in CDI 3 (and removed in 4):
>
> https://jakarta.ee/specifications/cdi/3.0/apidocs/jakarta/enterprise/inject/spi/beanmanager#fireEvent-java.lang.Object-java.lang.annotation.Annotation...-
>
> I did not report it since this is EE 10 work, which they don't claim
> to support. However, it doesn't hurt to remove use of these deprecated
> methods and I believe this would make CXF work with OWB 4 (although
> not officially supported). I use this example to show how much this EE
> 9 is simply a piece of garbage, you get breakage, it's useless, but
> then you get breakage again with EE 10.
>
> > > Basically unless there's a cut somewhere, nothing will ever change :D
> > > As a result, I don't think an API restoration in Tomcat 10.1 is a good
> > > idea ...
> > >
> >
> > Ok, so last option is TomEE community taking the lead on 10.0 branch, is
> > that an option if all the PR work is done?
>
> I doubt it would make any difference:
> a) Tomcat 10.0 was frozen at 10.1.1 level exactly 18 months ago.
> b) I suppose this is about CVEs.
> c) So the process would be to fix them and then release only the Maven
> artifacts. We cannot make a real release and advertise it with so many
> bugfixes missing.
> This would produce the same result with the same effort compared to
> their custom "forked" branch (I don't consider it a fork since this is
> simply a continuation from where the Tomcat branch stopped). I would
> be reluctant to vote +1 to these releases unfortunately due to the
> known issues.
>
> Backporting everything from Tomcat 10.1 is a huge effort ...
>
> Rémy
>
> > >
> > > Rémy
> > >
> > > > Best,
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Old Blog
> > > >  | Github <
> > > https://github.com/rmannibucau> |
> > > > LinkedIn 

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Rémy Maucherat]

On Wed, Mar 27, 2024 at 11:13 AM Romain Manni-Bucau
 wrote:
>
> Le mer. 27 mars 2024 à 10:58, Rémy Maucherat  a écrit :
>
> > On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
> >  wrote:
> > >
> > > Hi all,
> > >
> > > Checkout out TomEE's notifications I realized Tomcat is in a weirdish
> > > situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1
> > which
> > > is Servlet 6.
> > > It means Tomcat is no more a Servlet 5 friendly option.
> > >
> > > I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat
> > 10.0
> > > should be maintained and released again - pretty sure we can find help if
> > > desired for that not that far.
> > > Another option is to restore the deleted methods between servlet 5-6 in
> > the
> > > code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
> > > Servlet 6 - to pass signature TCK.
> > >
> > > Wdyt?
> >
> > Nothing. The Tomcat developers (= the committers) determined that the
> > EE 9 release was useless since the only change is the javax -> jakarta
> > package renaming. A big task for sure, but that seemed to us this was
> > more a developer oriented armaggeddon and not something that benefits
> > our users.
> >
> > For reasons that elude my understanding, some other projects like
> > TomEE thought this was still useful and decided to release full
> > support for EE 9 rather than go to EE 10 like we did. Our plan about
> > EE was public. So I guess this is still our problem obviously, but I
> > don't feel like doing anything about it.
> >
>
> From what I saw on other AsfEE projects, users requested it, nothing more
> and then you have CVE game.
>
>
> >
> > BTW, about the last item. Recently, I tried to run CXF on the new EE
> > 10 APIs (since OWB moved to that). It doesn't work as it uses
> > deprecated APIs, while IMO it should have moved away from them long
> > ago. And it's an ASF project, not some hack project somewhere.
> >
>
> This is fixed AFAIK on master (maybe last release, didnt check) so should
> be fine soon.

I checked and there is a new CXF release from early March.

However, I still get the CDI 4 deprecation removal issue:
Caused by: java.lang.NoSuchMethodError: 'void
jakarta.enterprise.inject.spi.BeanManager.fireEvent(java.lang.Object,
java.lang.annotation.Annotation[])'
at 
org.apache.cxf.cdi.JAXRSCdiResourceExtension.onStartup(JAXRSCdiResourceExtension.java:167)

This is deprecated in CDI 3 (and removed in 4):
https://jakarta.ee/specifications/cdi/3.0/apidocs/jakarta/enterprise/inject/spi/beanmanager#fireEvent-java.lang.Object-java.lang.annotation.Annotation...-

I did not report it since this is EE 10 work, which they don't claim
to support. However, it doesn't hurt to remove use of these deprecated
methods and I believe this would make CXF work with OWB 4 (although
not officially supported). I use this example to show how much this EE
9 is simply a piece of garbage, you get breakage, it's useless, but
then you get breakage again with EE 10.

> > Basically unless there's a cut somewhere, nothing will ever change :D
> > As a result, I don't think an API restoration in Tomcat 10.1 is a good
> > idea ...
> >
>
> Ok, so last option is TomEE community taking the lead on 10.0 branch, is
> that an option if all the PR work is done?

I doubt it would make any difference:
a) Tomcat 10.0 was frozen at 10.1.1 level exactly 18 months ago.
b) I suppose this is about CVEs.
c) So the process would be to fix them and then release only the Maven
artifacts. We cannot make a real release and advertise it with so many
bugfixes missing.
This would produce the same result with the same effort compared to
their custom "forked" branch (I don't consider it a fork since this is
simply a continuation from where the Tomcat branch stopped). I would
be reluctant to vote +1 to these releases unfortunately due to the
known issues.

Backporting everything from Tomcat 10.1 is a huge effort ...

Rémy

> >
> > Rémy
> >
> > > Best,
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn  | Book
> > > <
> > https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: dev-h...@tomcat.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

(tomcat) branch main updated: Fix Java release target

[remm]

This is an automated email from the ASF dual-hosted git repository.

remm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/main by this push:
 new 6fe3dbf547 Fix Java release target
6fe3dbf547 is described below

commit 6fe3dbf547e2e07388f688b4266f7020017294e3
Author: remm 
AuthorDate: Wed Mar 27 14:08:15 2024 +0100

Fix Java release target

EE 10 switched back to Java 17.
---
 modules/owb/pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/owb/pom.xml b/modules/owb/pom.xml
index a372517918..912abeed69 100644
--- a/modules/owb/pom.xml
+++ b/modules/owb/pom.xml
@@ -37,7 +37,7 @@
 2.1.0
 4.0.1
 2.1.1
-11.0.0-M17
+11.0.0-M18
 
 
 
@@ -98,7 +98,7 @@
 org.apache.maven.plugins
 maven-compiler-plugin
 
-21
+17
 
 
 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

svn commit: r1916579 - /tomcat/site/trunk/docs/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt

[markt]

Author: markt
Date: Wed Mar 27 12:31:13 2024
New Revision: 1916579

URL: http://svn.apache.org/viewvc?rev=1916579=rev
Log:
TCK WebSocket 2.2.0 Tomcat 11.0.0-M19-SNAPSHOT

Added:
tomcat/site/trunk/docs/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt

Added: tomcat/site/trunk/docs/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt
URL: 
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt?rev=1916579=auto
==
--- tomcat/site/trunk/docs/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt 
(added)
+++ tomcat/site/trunk/docs/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt 
Wed Mar 27 12:31:13 2024
@@ -0,0 +1,47 @@
+TCK Certification Summary
+=
+
+License:
+  The terms of the EFTL are acceptable.
+
+Product Name, Version and download URL:
+  Apache Tomcat
+  11.0.0-M19-SNAPSHOT (build 20240326.151401-23)
+  
https://repository.apache.org/content/groups/snapshots/org/apache/tomcat/tomcat/11.0.0-M19-SNAPSHOT/tomcat-11.0.0-M19-20240326.151401-23.tar.gz
+
+Specification Name, Version and download URL:
+  Jakarta WebSocket
+  2.2.0
+  https://github.com/jakartaee/specifications/pull/713
+
+TCK Version, digital SHA-256 fingerprint and download URL
+  TCK
+  2.2.0
+  
https://www.eclipse.org/downloads/download.php?file=/ee4j/jakartaee-tck/jakartaee11/staged/eftl/jakarta-websocket-tck-2.2.0.zip
+  SHA512: 
3284c6f45193a5f5e34b8bb9c65e222b6a35dd66a9c141466c0e35f36a7fb88ed9f7b498eb2688aa3d5be852a356bfc5165b9c49b5a17331ce99658cf2ad4d31
+
+Implementation runtime Version(s) tested:
+  Apache Tomcat
+  11.0.0-M19-SNAPSHOT (build 20240326.151401-23)
+
+Public URL of TCK Results Summary:
+  https://tomcat.apache.org/tck/websocket-2.2.0-tomcat-11.0.0-M19-SNAPSHOT.txt
+
+Any Additional Specification Certification Requirements:
+  None
+
+Java runtime used to run the implementation:
+  Java 17 - Temurin 17.0.10
+  Java 21 - Temurin 21.0.2
+
+Summary of the information for the certification environment:
+  Ubuntu 22.04.4 LTS
+​  https://github.com/apache/tomcat-tck
+  hash 2c6877326a5b05c24a1b0cc40b801177dfdf8ac7
+
+A statement attesting that all TCK requirements have been met, including any 
compatibility rules:
+  Confirmed
+
+Test results:
+  Java 17: Tests run: 737, Failures: 0, Errors: 0, Skipped: 0
+  Java 21: Tests run: 737, Failures: 0, Errors: 0, Skipped: 0



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Romain Manni-Bucau]

Hi Chris,

Le mer. 27 mars 2024 à 13:13, Christopher Schultz <
ch...@christopherschultz.net> a écrit :

> Romain,
>
> On 3/27/24 06:13, Romain Manni-Bucau wrote:
> > Le mer. 27 mars 2024 à 10:58, Rémy Maucherat  a écrit :
> >
> >> On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
> >>  wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Checkout out TomEE's notifications I realized Tomcat is in a weirdish
> >>> situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1
> >> which
> >>> is Servlet 6.
> >>> It means Tomcat is no more a Servlet 5 friendly option.
> >>>
> >>> I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat
> >> 10.0
> >>> should be maintained and released again - pretty sure we can find help
> if
> >>> desired for that not that far.
> >>> Another option is to restore the deleted methods between servlet 5-6 in
> >> the
> >>> code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
> >>> Servlet 6 - to pass signature TCK.
> >>>
> >>> Wdyt?
> >>
> >> Nothing. The Tomcat developers (= the committers) determined that the
> >> EE 9 release was useless since the only change is the javax -> jakarta
> >> package renaming. A big task for sure, but that seemed to us this was
> >> more a developer oriented armaggeddon and not something that benefits
> >> our users.
> >>
> >> For reasons that elude my understanding, some other projects like
> >> TomEE thought this was still useful and decided to release full
> >> support for EE 9 rather than go to EE 10 like we did. Our plan about
> >> EE was public. So I guess this is still our problem obviously, but I
> >> don't feel like doing anything about it.
> >>
> >
> >  From what I saw on other AsfEE projects, users requested it, nothing
> more
> > and then you have CVE game.
> >
> >
> >>
> >> BTW, about the last item. Recently, I tried to run CXF on the new EE
> >> 10 APIs (since OWB moved to that). It doesn't work as it uses
> >> deprecated APIs, while IMO it should have moved away from them long
> >> ago. And it's an ASF project, not some hack project somewhere.
> >>
> >
> > This is fixed AFAIK on master (maybe last release, didnt check) so should
> > be fine soon.
> >
> >
> >> Basically unless there's a cut somewhere, nothing will ever change :D
> >> As a result, I don't think an API restoration in Tomcat 10.1 is a good
> >> idea ...
> >>
> >
> > Ok, so last option is TomEE community taking the lead on 10.0 branch, is
> > that an option if all the PR work is done?
>
> Is the problem that you have customers actually using these APIs?
>
> https://tomcat.apache.org/tomcat-10.0-doc/servletapi/deprecated-list.html
>
> Or is the problem that you can't pass a TCK unless you have support for
> these ancient methods?
>

A bit both, have to admit I lost a bit track of original user request and
if they adopted it or not but TCK point is important and justifies today a
complete tomcat fork which is quite not understandable for me from an ASF
standpoint.


>
> Most of that stuff was deprecated ages ago and just finally removed.
>
> Why is it super important for you to get certified for Servlet 5
> specifically? Why not just get Jakarta EE 10 certified and move on? Any
> applications that would actually fail on Tomcat 10.1 + Migration Tool
> really really _really_ need to be updated to work properly. People have
> had 15 years to stop using that stuff.
>

This is the plan, but for the same reason you don't want to release 10.0,
certification is not a one week fork, tomee 10m1 is planned but in the
meantime having tomee 9 (servlet 5) certified would be very welcomed.
That said should I read it as you are proposing yourself to help? (trying
;)).


>
> Honestly, I think it would be much more worth you while to fork Tomcat
> 10.1 and add-back the methods you need rather than trying to resurrect
> the 10.0 branch. There have been no commits on that branch for 2 years,
> and we've had something like ~24 releases of each other branch in the
> meantime. That includes performance improvements, security fixes,
> feature and stability improvements, etc.
>
> Would it be as simple as providing your own replacements for deprecated
> classes/methods to pass the TCK? That seems far less onerous than
> bringing back zombie Tomcat 10.0.
>

Asked this morning the same question but it is still being investigated if
possible but still means forking at some point so gain is not really huge
for the project - can be for end users, agree.


>
> -chris
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

(tomcat-tck) branch main updated: Simplify

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git


The following commit(s) were added to refs/heads/main by this push:
 new 2c68773  Simplify
2c68773 is described below

commit 2c6877326a5b05c24a1b0cc40b801177dfdf8ac7
Author: Mark Thomas 
AuthorDate: Wed Mar 27 12:13:38 2024 +

Simplify
---
 websocket-tck/pom.xml | 4 
 1 file changed, 4 deletions(-)

diff --git a/websocket-tck/pom.xml b/websocket-tck/pom.xml
index 0d1deb1..2c7de16 100644
--- a/websocket-tck/pom.xml
+++ b/websocket-tck/pom.xml
@@ -132,11 +132,7 @@
 
 
 
jakarta.tck:websocket-tck-spec-tests
-
 
 5
 false


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Christopher Schultz]

Romain,

On 3/27/24 06:13, Romain Manni-Bucau wrote:

Le mer. 27 mars 2024 à 10:58, Rémy Maucherat  a écrit :


On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
 wrote:


Hi all,

Checkout out TomEE's notifications I realized Tomcat is in a weirdish
situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1

which

is Servlet 6.
It means Tomcat is no more a Servlet 5 friendly option.

I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat

10.0

should be maintained and released again - pretty sure we can find help if
desired for that not that far.
Another option is to restore the deleted methods between servlet 5-6 in

the

code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
Servlet 6 - to pass signature TCK.

Wdyt?


Nothing. The Tomcat developers (= the committers) determined that the
EE 9 release was useless since the only change is the javax -> jakarta
package renaming. A big task for sure, but that seemed to us this was
more a developer oriented armaggeddon and not something that benefits
our users.

For reasons that elude my understanding, some other projects like
TomEE thought this was still useful and decided to release full
support for EE 9 rather than go to EE 10 like we did. Our plan about
EE was public. So I guess this is still our problem obviously, but I
don't feel like doing anything about it.



 From what I saw on other AsfEE projects, users requested it, nothing more
and then you have CVE game.




BTW, about the last item. Recently, I tried to run CXF on the new EE
10 APIs (since OWB moved to that). It doesn't work as it uses
deprecated APIs, while IMO it should have moved away from them long
ago. And it's an ASF project, not some hack project somewhere.



This is fixed AFAIK on master (maybe last release, didnt check) so should
be fine soon.



Basically unless there's a cut somewhere, nothing will ever change :D
As a result, I don't think an API restoration in Tomcat 10.1 is a good
idea ...



Ok, so last option is TomEE community taking the lead on 10.0 branch, is
that an option if all the PR work is done?


Is the problem that you have customers actually using these APIs?

https://tomcat.apache.org/tomcat-10.0-doc/servletapi/deprecated-list.html

Or is the problem that you can't pass a TCK unless you have support for 
these ancient methods?


Most of that stuff was deprecated ages ago and just finally removed.

Why is it super important for you to get certified for Servlet 5 
specifically? Why not just get Jakarta EE 10 certified and move on? Any 
applications that would actually fail on Tomcat 10.1 + Migration Tool 
really really _really_ need to be updated to work properly. People have 
had 15 years to stop using that stuff.


Honestly, I think it would be much more worth you while to fork Tomcat 
10.1 and add-back the methods you need rather than trying to resurrect 
the 10.0 branch. There have been no commits on that branch for 2 years, 
and we've had something like ~24 releases of each other branch in the 
meantime. That includes performance improvements, security fixes, 
feature and stability improvements, etc.


Would it be as simple as providing your own replacements for deprecated 
classes/methods to pass the TCK? That seems far less onerous than 
bringing back zombie Tomcat 10.0.


-chris

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

(tomcat-tck) branch main updated: List spec and platform dependencies explicitly

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git


The following commit(s) were added to refs/heads/main by this push:
 new 2a2ad02  List spec and platform dependencies explicitly
2a2ad02 is described below

commit 2a2ad02d7a712e4411b86938b9cb85d778eee050
Author: Mark Thomas 
AuthorDate: Wed Mar 27 12:12:17 2024 +

List spec and platform dependencies explicitly

This allows simpler testing with the published TCK bundle.
---
 websocket-tck/pom.xml | 22 --
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/websocket-tck/pom.xml b/websocket-tck/pom.xml
index 3288d10..0d1deb1 100644
--- a/websocket-tck/pom.xml
+++ b/websocket-tck/pom.xml
@@ -31,9 +31,8 @@
 
 
 jakarta.tck
-websocket-tck-dist
+websocket-tck-spec-tests
 ${tck.websocket.version}
-
 
   
 jakarta.websocket
@@ -45,6 +44,25 @@
   
 
 
+
 
 org.apache.tomcat.embed
 tomcat-embed-websocket


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Romain Manni-Bucau]

Le mer. 27 mars 2024 à 10:58, Rémy Maucherat  a écrit :

> On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
>  wrote:
> >
> > Hi all,
> >
> > Checkout out TomEE's notifications I realized Tomcat is in a weirdish
> > situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1
> which
> > is Servlet 6.
> > It means Tomcat is no more a Servlet 5 friendly option.
> >
> > I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat
> 10.0
> > should be maintained and released again - pretty sure we can find help if
> > desired for that not that far.
> > Another option is to restore the deleted methods between servlet 5-6 in
> the
> > code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
> > Servlet 6 - to pass signature TCK.
> >
> > Wdyt?
>
> Nothing. The Tomcat developers (= the committers) determined that the
> EE 9 release was useless since the only change is the javax -> jakarta
> package renaming. A big task for sure, but that seemed to us this was
> more a developer oriented armaggeddon and not something that benefits
> our users.
>
> For reasons that elude my understanding, some other projects like
> TomEE thought this was still useful and decided to release full
> support for EE 9 rather than go to EE 10 like we did. Our plan about
> EE was public. So I guess this is still our problem obviously, but I
> don't feel like doing anything about it.
>

>From what I saw on other AsfEE projects, users requested it, nothing more
and then you have CVE game.


>
> BTW, about the last item. Recently, I tried to run CXF on the new EE
> 10 APIs (since OWB moved to that). It doesn't work as it uses
> deprecated APIs, while IMO it should have moved away from them long
> ago. And it's an ASF project, not some hack project somewhere.
>

This is fixed AFAIK on master (maybe last release, didnt check) so should
be fine soon.


> Basically unless there's a cut somewhere, nothing will ever change :D
> As a result, I don't think an API restoration in Tomcat 10.1 is a good
> idea ...
>

Ok, so last option is TomEE community taking the lead on 10.0 branch, is
that an option if all the PR work is done?


>
> Rémy
>
> > Best,
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Rémy Maucherat]

On Wed, Mar 27, 2024 at 9:49 AM Romain Manni-Bucau
 wrote:
>
> Hi all,
>
> Checkout out TomEE's notifications I realized Tomcat is in a weirdish
> situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1 which
> is Servlet 6.
> It means Tomcat is no more a Servlet 5 friendly option.
>
> I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat 10.0
> should be maintained and released again - pretty sure we can find help if
> desired for that not that far.
> Another option is to restore the deleted methods between servlet 5-6 in the
> code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
> Servlet 6 - to pass signature TCK.
>
> Wdyt?

Nothing. The Tomcat developers (= the committers) determined that the
EE 9 release was useless since the only change is the javax -> jakarta
package renaming. A big task for sure, but that seemed to us this was
more a developer oriented armaggeddon and not something that benefits
our users.

For reasons that elude my understanding, some other projects like
TomEE thought this was still useful and decided to release full
support for EE 9 rather than go to EE 10 like we did. Our plan about
EE was public. So I guess this is still our problem obviously, but I
don't feel like doing anything about it.

BTW, about the last item. Recently, I tried to run CXF on the new EE
10 APIs (since OWB moved to that). It doesn't work as it uses
deprecated APIs, while IMO it should have moved away from them long
ago. And it's an ASF project, not some hack project somewhere.
Basically unless there's a cut somewhere, nothing will ever change :D
As a result, I don't think an API restoration in Tomcat 10.1 is a good
idea ...

Rémy

> Best,
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Romain Manni-Bucau]

Hi Mark,

I'm aware of these discussions but it let Tomcat in the state where Servlet
5.0 is not supported - but Servlet 4.0 is which is ultra weird but don't
get me wrong I'm for keeping it for a  moment.
Concretely it prevents downstream consumers to be certified so

> No interest in supporting 10.0.x

is likely wrong from a community standpoint and at least TomEE would be
interested in dropping its fork of Tomcat 10 for that reason.

Any way we get back a 10.0 or a 10.1 runnable with Servlet 5.0 API (guess
it would be better for everyone)?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 27 mars 2024 à 10:45, Mark Thomas  a écrit :

> On 27/03/2024 08:48, Romain Manni-Bucau wrote:
> > Hi all,
> >
> > Checkout out TomEE's notifications I realized Tomcat is in a weirdish
> > situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1
> which
> > is Servlet 6.
> > It means Tomcat is no more a Servlet 5 friendly option.
> >
> > I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat
> 10.0
> > should be maintained and released again - pretty sure we can find help if
> > desired for that not that far.
> > Another option is to restore the deleted methods between servlet 5-6 in
> the
> > code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
> > Servlet 6 - to pass signature TCK.
> >
> > Wdyt?
>
> -1 to stopping Tomcat 9.0.x support.
>
> No interest in supporting 10.0.x
>
> This has been discussed at length previously. Those discussions can be
> found in the archives.
>
> The short version is:
> - Tomcat 9.x (Java EE8) will be maintained for the foreseeable future at
>it is the last branch to support Java EE.
> - Jakarta EE 9 (Tomcat 10.0) was a transition release that we only ever
>intended to maintain for as long as it took for Jakarta EE 10 (Tomcat
>10.1) to reach stability
>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

(tomcat-tck) branch main updated (3d009ff -> a5f4764)

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git


from 3d009ff  Disable platform TCK tests by default
 new 7e3231c  Servlet TCK now requires an slf4j implementation to be 
configured
 new a5f4764  Add explicit dependency on tomcat-servlet-api for signature 
tests

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 pom.xml |  5 +
 servlet-tck/pom.xml | 10 ++
 2 files changed, 15 insertions(+)


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

(tomcat-tck) 01/02: Servlet TCK now requires an slf4j implementation to be configured

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git

commit 7e3231c773c70caade82f91d3f1cdd55705c5363
Author: Mark Thomas 
AuthorDate: Wed Mar 27 09:31:51 2024 +

Servlet TCK now requires an slf4j implementation to be configured
---
 pom.xml | 5 +
 servlet-tck/pom.xml | 4 
 2 files changed, 9 insertions(+)

diff --git a/pom.xml b/pom.xml
index 0613af1..312a61f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -79,6 +79,11 @@
 pom
 import
 
+
+org.slf4j
+slf4j-simple
+2.0.12
+
 
 
 
diff --git a/servlet-tck/pom.xml b/servlet-tck/pom.xml
index 2f4d2a7..f691a10 100644
--- a/servlet-tck/pom.xml
+++ b/servlet-tck/pom.xml
@@ -84,6 +84,10 @@
 junit
 4.13.2
 
+
+org.slf4j
+slf4j-simple
+
 
 
 


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

(tomcat-tck) 02/02: Add explicit dependency on tomcat-servlet-api for signature tests

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git

commit a5f4764887dcc7eb69fbced37d8f49cc11a2d9bf
Author: Mark Thomas 
AuthorDate: Wed Mar 27 09:50:01 2024 +

Add explicit dependency on tomcat-servlet-api for signature tests
---
 servlet-tck/pom.xml | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/servlet-tck/pom.xml b/servlet-tck/pom.xml
index f691a10..38032e2 100644
--- a/servlet-tck/pom.xml
+++ b/servlet-tck/pom.xml
@@ -53,6 +53,12 @@
 ${tomcat.version}
 test
 
+
+org.apache.tomcat
+tomcat-servlet-api
+${tomcat.version}
+test
+
 
 org.jboss.arquillian.container
 arquillian-tomcat-embedded-10


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Mark Thomas]

On 27/03/2024 08:48, Romain Manni-Bucau wrote:

Hi all,

Checkout out TomEE's notifications I realized Tomcat is in a weirdish
situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1 which
is Servlet 6.
It means Tomcat is no more a Servlet 5 friendly option.

I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat 10.0
should be maintained and released again - pretty sure we can find help if
desired for that not that far.
Another option is to restore the deleted methods between servlet 5-6 in the
code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
Servlet 6 - to pass signature TCK.

Wdyt?


-1 to stopping Tomcat 9.0.x support.

No interest in supporting 10.0.x

This has been discussed at length previously. Those discussions can be 
found in the archives.


The short version is:
- Tomcat 9.x (Java EE8) will be maintained for the foreseeable future at
  it is the last branch to support Java EE.
- Jakarta EE 9 (Tomcat 10.0) was a transition release that we only ever
  intended to maintain for as long as it took for Jakarta EE 10 (Tomcat
  10.1) to reach stability

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

(tomcat-tck) branch main updated: Disable platform TCK tests by default

[markt]

This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-tck.git


The following commit(s) were added to refs/heads/main by this push:
 new 3d009ff  Disable platform TCK tests by default
3d009ff is described below

commit 3d009ff6d047d734cb19a01502d39e61cf0b3e41
Author: Mark Thomas 
AuthorDate: Tue Mar 26 14:50:35 2024 +

Disable platform TCK tests by default
---
 websocket-tck/pom.xml | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/websocket-tck/pom.xml b/websocket-tck/pom.xml
index 9d28894..3288d10 100644
--- a/websocket-tck/pom.xml
+++ b/websocket-tck/pom.xml
@@ -114,9 +114,13 @@
 
 
 
jakarta.tck:websocket-tck-spec-tests
+
 
-20
+5
 false
 
 http


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Community Over Code NA 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

[ You are receiving this email as a subscriber to one or more ASF project
dev or user
  mailing lists and is not being sent to you directly. It is important that
we reach all of our
  users and contributors/committers so that they may get a chance to
benefit from this.
  We apologise in advance if this doesn't interest you but it is on topic
for the mailing
  lists of the Apache Software Foundation; and it is important please that
you do not
  mark this as spam in your email client. Thank You! ]

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code NA 2024 are now
open!

We will be supporting Community over Code NA, Denver Colorado in
October 7th to the 10th 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Monday 6th May, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Denver, Colorado , October 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Stop releasing Tomcat 9 or adding back Tomcat 10.0?

[Romain Manni-Bucau]

Hi all,

Checkout out TomEE's notifications I realized Tomcat is in a weirdish
situation where Tomcat 9 is Servlet 4 and "+1" version is Tomcat 10.1 which
is Servlet 6.
It means Tomcat is no more a Servlet 5 friendly option.

I wonder if it means Tomcat < 10.1 should be stopped too or if Tomcat 10.0
should be maintained and released again - pretty sure we can find help if
desired for that not that far.
Another option is to restore the deleted methods between servlet 5-6 in the
code base to be able to run Tomcat 10.1 with Servlet 5 API instead of
Servlet 6 - to pass signature TCK.

Wdyt?

Best,
Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book