Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Why is Jetty not listed as Jakarta compatible product?

All of those questions are personal preference.
Personally, I would use ee10 (or ee11 on Jetty 12.1.x), not ee9.
As the ee9 codebase is pretty much ee8 with only namespace changes, and has none of the features from ee10 that you need to work with modern browsers (eg: Same-Site on Cookies to use one example of many).  The ee10 codebase is also actively maintained and improved.

We are actively working with the ee10 (and now ee11) Servlet TCK.
There's some TCK challenges (a process at the Jakarta EE foundation) we have to see through before we get our formal certification.

As for Jakarta WebSocket vs Jetty WebSocket, I personally choose Jetty WebSocket every time, as it is far more capable and configurable (esp with SSL/TLS) than Jakarta WebSocket, and I'm a project lead of the Jakarta WebSocket spec working group.

- Joakim

On Fri, Oct 18, 2024 at 7:31 AM Alexander Farber via jetty-users <jetty-users@xxxxxxxxxxx> wrote:
Ah, thank you Joakim.

Does this mean, I should target EE9 and not EE10, when I am trying to migrate my pet project servlet from Jetty 10 to Jetty 12?

And should I try to use Jakarta API for Websockets or keep using the Jetty Websockets?

Best regards
Alex
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users

Back to the top