[
https://issues.apache.org/jira/browse/CAMEL-27030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Mariani updated CAMEL-27030:
-------------------------------------
Description:
Camel main currently uses io.undertow:undertow-core:2.4.4.Final with
io.undertow:undertow-servlet:2.3.27.Final. The servlet implementation remains
on the Servlet 6.0 line.
Undertow EE now provides a Final Jakarta Servlet 6.1 implementation under
io.undertow.ee:undertow-servlet:2.0.3.Final. The separate
undertow-io/spring-boot-undertow integration for Spring Boot 4 already uses
this implementation. An application combining that integration with
camel-undertow can consequently contain both servlet artifacts. Their group IDs
differ, so Maven does not mediate them as alternative versions, while their
io.undertow.servlet Java packages overlap.
Undertow EE 2.0.3.Final declares Undertow core 2.4.4.Final, matching Camel
main's existing core version.
Proposed work:
* Migrate camel-undertow and Camel's other direct Undertow servlet
dependencies/test fixtures to the Final Undertow EE implementation.
* Manage the EE version independently from Undertow core and validate it
against Camel's selected core version.
* Add regression coverage for a Servlet 6.1 deployment coexisting with Camel
Undertow HTTP consumers and document the dependency-coordinate change in the
upgrade guide.
* Verify affected component tests and resolved dependency trees contain one
servlet implementation.
This revisits the migration in CAMEL-23057 /
https://github.com/apache/camel/pull/21580, reverted by
https://github.com/apache/camel/commit/5893417f084462ee0cadf3e71a75a8b9b1ac111d
when Undertow EE had no Final release. Undertow EE 2.0.3.Final is now
published, so that earlier reason should be reassessed.
References:
https://github.com/undertow-io/undertow-ee
https://github.com/undertow-io/spring-boot-undertow
AI-assisted issue prepared by Codex on behalf of Federico Mariani (Croway).
was:
Camel main currently uses io.undertow:undertow-core:2.4.4.Final with
io.undertow:undertow-servlet:2.3.27.Final. The servlet implementation remains
on the Servlet 6.0 line.
Undertow EE now provides a Final Jakarta Servlet 6.1 implementation under
io.undertow.ee:undertow-servlet:2.0.2.Final. The separate
undertow-io/spring-boot-undertow integration for Spring Boot 4 already uses
this implementation. An application combining that integration with
camel-undertow can consequently contain both servlet artifacts. Their group IDs
differ, so Maven does not mediate them as alternative versions, while their
io.undertow.servlet Java packages overlap.
Proposed work:
* Migrate camel-undertow and Camel's other direct Undertow servlet
dependencies/test fixtures to the Final Undertow EE implementation.
* Manage the EE version independently from Undertow core and validate it
against Camel's selected core version.
* Add regression coverage for a Servlet 6.1 deployment coexisting with Camel
Undertow HTTP consumers and document the dependency-coordinate change in the
upgrade guide.
* Verify affected component tests and resolved dependency trees contain one
servlet implementation.
This revisits the migration in CAMEL-23057 /
https://github.com/apache/camel/pull/21580, reverted by
https://github.com/apache/camel/commit/5893417f084462ee0cadf3e71a75a8b9b1ac111d
when Undertow EE had no Final release. Undertow EE 2.0.2.Final is now
published, so that earlier reason should be reassessed.
References:
https://github.com/undertow-io/undertow-ee
https://github.com/undertow-io/spring-boot-undertow
AI-assisted issue prepared by Codex on behalf of Federico Mariani (Croway).
> Migrate Undertow servlet dependencies to Undertow EE
> ----------------------------------------------------
>
> Key: CAMEL-27030
> URL: https://issues.apache.org/jira/browse/CAMEL-27030
> Project: Camel
> Issue Type: Improvement
> Components: camel-undertow
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Major
> Fix For: 4.24.0
>
>
> Camel main currently uses io.undertow:undertow-core:2.4.4.Final with
> io.undertow:undertow-servlet:2.3.27.Final. The servlet implementation remains
> on the Servlet 6.0 line.
> Undertow EE now provides a Final Jakarta Servlet 6.1 implementation under
> io.undertow.ee:undertow-servlet:2.0.3.Final. The separate
> undertow-io/spring-boot-undertow integration for Spring Boot 4 already uses
> this implementation. An application combining that integration with
> camel-undertow can consequently contain both servlet artifacts. Their group
> IDs differ, so Maven does not mediate them as alternative versions, while
> their io.undertow.servlet Java packages overlap.
> Undertow EE 2.0.3.Final declares Undertow core 2.4.4.Final, matching Camel
> main's existing core version.
> Proposed work:
> * Migrate camel-undertow and Camel's other direct Undertow servlet
> dependencies/test fixtures to the Final Undertow EE implementation.
> * Manage the EE version independently from Undertow core and validate it
> against Camel's selected core version.
> * Add regression coverage for a Servlet 6.1 deployment coexisting with Camel
> Undertow HTTP consumers and document the dependency-coordinate change in the
> upgrade guide.
> * Verify affected component tests and resolved dependency trees contain one
> servlet implementation.
> This revisits the migration in CAMEL-23057 /
> https://github.com/apache/camel/pull/21580, reverted by
> https://github.com/apache/camel/commit/5893417f084462ee0cadf3e71a75a8b9b1ac111d
> when Undertow EE had no Final release. Undertow EE 2.0.3.Final is now
> published, so that earlier reason should be reassessed.
> References:
> https://github.com/undertow-io/undertow-ee
> https://github.com/undertow-io/spring-boot-undertow
> AI-assisted issue prepared by Codex on behalf of Federico Mariani (Croway).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)