camel
camel copied to clipboard
apache
Migration to Jakarta EE 8
This pull request contains changes described in CAMEL-17136: dependencies are updated to their Jakarta EE 8 analogues then possible. Current known limitations and notices:
- Jetty 9 -> Jetty 10 migration: Websocket. Jetty 10 is compatible with Jakarta EE 8, but many Apache Camel components use Jetty 9 specific websocket realization. This components are now unchanged left. This components are camel-ahc-ws, camel-atmosphere-websocket, camel-websocket.
- Jetty 9 -> Jetty 10 migration: Continuation. Jetty specific mechanism Continuation for asynchronous request processing is obsolete and was removed in Jetty 10. Component camel-jetty-common contains CamelContinuationServlet, which actively uses Continuation. Within current changes Continuation is replacing with AsyncContext, but existent junit-tests not give a confidence in full correctness of this change.
:no_entry_sign: There are too many components to be tested in this PR, components were removed or the code needs a rebase: (33 likely to be tested)
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (31 likely to be tested)
Thanks for the PR. We need to align also camel-karaf repository to use the same deps
Appropriated changes are made
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (31 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (31 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (31 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (30 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (30 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (30 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (30 likely to be tested)
@bvfalcon Is this still valid?
Yes, completely. I actualize periodically with last changes from branch "main" and hope, PR will be reviewed and merged sometime ;)
@bvfalcon Is this still valid?
Yes, completely. I actualize periodically with last changes from branch "main" and hope, PR will be reviewed and merged sometime ;)
Thank you for clarifying ... I have some work ahead that may overlap with this, so I am trying to understand at what point we are :)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (30 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (31 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (29 likely to be tested)
There are too many components to be tested in this PR, components were removed or the code needs a rebase: (38 likely to be tested)
:leftwards_arrow_with_hook: There are either too many changes to be tested in this PR or the code needs be rebased: (38 components likely to be affected)
:leftwards_arrow_with_hook: There are either too many changes to be tested in this PR or the code needs be rebased: (38 components likely to be affected)
Yes, I think so. There is also a PR on Karaf side probably, we should close there too.
