There is community work underway to update GWT-RPC itself to use jakarta.servlet packages, and the same idea could be applied to gwtplatform. Unfortunately, the gwtplatform.com domain is still owned, so any fork could not take over the groupid, but would need to pick a new one, which might cause some irritation when upgrading. I do see that the domain is scheduled to expire next year, but that probably isn't long enough to wait. It might be possible to contact the former owners to get permission for this work to be published as well. If you take that route, I'd be interested in being involved.
I've used the eclipse transformer before, and personally found it to be more trouble that it is worth.
On Friday, July 21, 2023 at 8:03:56 AM UTC-5 NIKITAH wrote:
Thank you Thomas for your guidance .On Friday, July 21, 2023 at 6:25:36 PM UTC+5:30 Thomas Broyer wrote:On Friday, July 21, 2023 at 12:51:32 PM UTC+2 NIKITAH wrote:Yes , we are using jakartaee-api : 9.0.0 . So can you please suggest which version of gwtp-dispatch-rest-*.jar will be compatible with Jakarta 9.0 ?None!Repeating myself here:Legacy projects should stay on "legacy" Java EE (or Jakarta EE 8), or migrate away from legacy/abandoned libs and frameworks that lock them to Java EE.
- GWTP is long dead; at least one year before the Javax/Jakarta mess was even announced (except for one never-released commit in Sept. 2018)
Now paraphrasing myself, you have to either:
- stay on Jakarta EE 8 (or earlier Java EE)
- rewrite the whole thing to remove GWTP
- transform GWTP to Jakarta EE 9+ with the help of tools like Eclipse Transformer
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c27903b8-a23b-4d9b-bc75-465e53b1d1ean%40googlegroups.com.
No comments:
Post a Comment