There is the jakarta migration utility. Supposed to convert wars from
javax.* to jakarta.* for deployment. Tomcat also has a special deployment
option for such.
Another approach to consider, depending on your needs, is spring boot run,
maybe inside a docker container.
On Wed, Sep 21, 2022 at 11:
Thanks. We had problems due to jakarta.servlet with Glassfish 6.0 when we
attempted to migrate.
So was looking for a good replacement preferably open source. Was thinking
Payara, but if it goes jakarta route, we will have the same issue in the
future. Any suggestions?
On Wednesday, September
If you use GWT-RPC or RequestFactory you need to choose a servlet container
that still uses javax.servlet instead of jakarta.servlet because both these
GWT features have a servlet component using javax.servlet.
Other than that, you can choose whatever you want.
-- J.
Valavanur Man schrieb am D
Hi!
GWT has no dependencies to any app server. Just use your preferred one (and
look into your own code if you experience issues ;-))
Bon courage
Ralph
Valavanur Man schrieb am Di. 20. Sept. 2022 um 17:59:
> Hi,
>
> We are running GWT 2.8 with Glassfish4. We had issues trying to run the
> GWT (
Hi,
We are running GWT 2.8 with Glassfish4. We had issues trying to run the
GWT (2.8) App in Glassfish 6.
Currently we are looking into upgrading to GWT 2.10. Would like you know
what appservers are supported to run GWT 2.10 (even GWT 2.8 and beyond). Is
there a recommended set of servers?
A
