[gwt-contrib] Re: Seeking Advice on Legacy Application Migration Strategy

[Jens]

Then the very first thing to do is stop using the embedded Jetty of GWT 
DevMode as application server. The embedded Jetty in GWT DevMode does some 
ClassLoader hacks and it often causes issues for people using the embedded 
Jetty as application server. That is the reason why GWT 2.11 has deprecated 
the use of embedded Jetty except for demo purposes. If you search for 
"jetty-web.xml" or "jetty-env.xml" on Github GWT issues then you will 
already find some issues with the above stack trace.

So you should find a solution to run a dedicated servlet container (jetty, 
tomcat, etc) that fits your workflow. 

GWT has updated its Getting Started instructions 
(https://www.gwtproject.org/gettingstarted-v2.html) to use the recommended 
project layout and a dedicated servlet container via Maven plugin. The core 
essence is to split the legacy project layout into three projects (client, 
shared, server) with dedicated classpaths and use a build tool to build a 
*.war file (or an exploded war folder) and then deploy this file/folder to 
a dedicated servlet container of your choice. The dedicated servlet 
container can then be configured as you like, usually as closely to your 
production server as possible.

Personally I don't like launching a servlet container via a build tool so I 
use a jetty docker container and a shell script to deploy the webapp.

-- J.

Wejden Mrabti schrieb am Mittwoch, 1. Mai 2024 um 17:09:57 UTC+2:

>
> thank  you @jens for your answer 
>
> I started by  upgrading gwt Only  from version 2.8.2 To 2.10.0 and I kept 
> java 8 .
> I my jetty-env.xml file  i had  org.eclipse.jetty.webapp.WebAppContext as 
> a configurationClass, so It cause fd ollowing error when launching 
> java.lang.ClassNotFoundException: 
> org.eclipse.jetty.webapp.WebAppContext
> at java.lang.ClassLoader.findClass(ClassLoader.java:523)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:487)
> at 
> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.loadClass(JettyLauncher.java:458)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at org.eclipse.jetty.util.Loader.loadClass(Loader.java:64)
> at 
> org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.nodeClass(XmlConfiguration.java:477)
> at 
> org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417)
> at 
> org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:364)
> at 
> org.eclipse.jetty.plus.webapp.EnvConfiguration.lambda$configure$0(EnvConfiguration.java:120)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.runWithServerClassAccess(WebAppClassLoader.java:138)
> at 
> org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118)
> at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
> at 
> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:568)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> at org.eclipse.jetty.server.Server.start(Server.java:423)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
> at org.eclipse.jetty.server.Server.doStart(Server.java:387)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> at 
> com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:776)
> at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)
> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)
> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)
> at com.google.gwt.dev.DevMode.main(DevMode.java:432)
> Suppressed: java.lang.ClassNotFoundException: 
> org.eclipse.jetty.webapp.WebAppContext
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.findClass(WebAppClassLoader.java:629)
> at 
> 

Re: Seeking Advice on Legacy Application Migration Strategy

[Wejden Mrabti]

thank you @Colin 

I started by  upgrading gwt Only  from version 2.8.2 To 2.10.0 and I kept 
java 8 and  GXT 2.3.1a-gwt22
In  my jetty-env.xml file  i had  org.eclipse.jetty.webapp.WebAppContext as 
a configurationClass, so It cause fd ollowing error when launching 
java.lang.ClassNotFoundException: 
org.eclipse.jetty.webapp.WebAppContext
at java.lang.ClassLoader.findClass(ClassLoader.java:523)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:487)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.loadClass(JettyLauncher.java:458)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at org.eclipse.jetty.util.Loader.loadClass(Loader.java:64)
at 
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.nodeClass(XmlConfiguration.java:477)
at 
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417)
at 
org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:364)
at 
org.eclipse.jetty.plus.webapp.EnvConfiguration.lambda$configure$0(EnvConfiguration.java:120)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.runWithServerClassAccess(WebAppClassLoader.java:138)
at 
org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118)
at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910)
at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:568)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
at org.eclipse.jetty.server.Server.start(Server.java:423)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
at org.eclipse.jetty.server.Server.doStart(Server.java:387)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:776)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)
at com.google.gwt.dev.DevMode.main(DevMode.java:432)
Suppressed: java.lang.ClassNotFoundException: 
org.eclipse.jetty.webapp.WebAppContext
at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.findClass(WebAppClassLoader.java:629)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:511)
... 31 more

Le vendredi 26 avril 2024 à 15:28:09 UTC+2, Colin Alworth a écrit :

> You might run into issues with such an old version of GXT when using a new 
> GWT version - take a look at 
> https://groups.google.com/g/google-web-toolkit/c/If897MPqvw0/m/bSWnmuz9BwAJ 
> for a summary of how to update GXT 2.3.1a-gwt22. 
>
> With GWT updated to 2.9.0 or beyond, you will be able to run on Java 11 
> (see https://www.gwtproject.org/release-notes.html#Release_Notes_2_9_0). 
>
>
>
>
> On Friday, April 26, 2024 at 7:59:27 AM UTC-5 wejden...@gmail.com wrote:
>
>> Many thanks @frank Hossfeld, 
>> I am so excited to start it .. it is clear 
>> please feel free to share any references or links that can help me in 
>> that adventure .
>>
>> thank you
>> wm
>>
>> Le ven. 26 avr. 2024 à 11:50, 'Frank Hossfeld' via GWT Users <
>> google-we...@googlegroups.com> a écrit :
>>
>>> GWT 2.8.2 is pretty old - nearly seven years - and i am not sure, if the 
>>> GWT 2.8.2 will work with Java 11
>>>
>>> Migrating to the latest version of GWT will give you some benefits. IIRC 
>>> GWT 2.8.2 generates at least 5 JS-files where GWT 2.11.0 only generates 2. 
>>> This will speed up the build. Also, there is a security issue in older GWT 
>>> versions (in case you are using RPC). 
>>>
>>> To do so, separate your code in client-, shared- and server-modules (as 
>>> Craig already mentioned).  Take a look here: 
>>> https://github.com/tbroyer/gwt-maven-archetypes or here 
>>> 

[gwt-contrib] Re: Seeking Advice on Legacy Application Migration Strategy

[Wejden Mrabti]

thank  you @jens for your answer 

I started by  upgrading gwt Only  from version 2.8.2 To 2.10.0 and I kept 
java 8 .
I my jetty-env.xml file  i had  org.eclipse.jetty.webapp.WebAppContext as a 
configurationClass, so It cause fd ollowing error when launching 
java.lang.ClassNotFoundException: 
org.eclipse.jetty.webapp.WebAppContext
at java.lang.ClassLoader.findClass(ClassLoader.java:523)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:487)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.loadClass(JettyLauncher.java:458)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at org.eclipse.jetty.util.Loader.loadClass(Loader.java:64)
at 
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.nodeClass(XmlConfiguration.java:477)
at 
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:417)
at 
org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:364)
at 
org.eclipse.jetty.plus.webapp.EnvConfiguration.lambda$configure$0(EnvConfiguration.java:120)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.runWithServerClassAccess(WebAppClassLoader.java:138)
at 
org.eclipse.jetty.plus.webapp.EnvConfiguration.configure(EnvConfiguration.java:118)
at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:910)
at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:568)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
at org.eclipse.jetty.server.Server.start(Server.java:423)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
at org.eclipse.jetty.server.Server.doStart(Server.java:387)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:776)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)
at com.google.gwt.dev.DevMode.main(DevMode.java:432)
Suppressed: java.lang.ClassNotFoundException: 
org.eclipse.jetty.webapp.WebAppContext
at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.findClass(WebAppClassLoader.java:629)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:511)
... 31 more

Le mardi 30 avril 2024 à 10:37:22 UTC+2, Jens a écrit :

> I would first focus on upgrading Java, GWT and possibly GXT if it is 
> incompatible with newest GWT. The DataSource error will go away once you 
> upgrade GWT because newer GWT versions use a newer Jetty. Keep in mind that 
> in newest GWT the use of embedded Jetty as appliction server during 
> development has been deprecated. It is preferred to use a local jetty 
> installation, a docker container or launching jetty via a build tool plugin 
> (maven / gradle).
>
> Once you have upgraded to latest GWT you have the possibility to use GWT 
> 2.11-jakarta if you need to switch to Jakarta.
>
> GWT itself only supports Hibernate 4 validation. So if the application 
> uses Hibernate validation in GWT as well, then you likely need to use 
> https://gitlab.com/ManfredTremmel/gwt-bean-validators
>
> -- J.
>
> Wejden Mrabti schrieb am Donnerstag, 25. April 2024 um 15:59:45 UTC+2:
>
>> Hello GWT Community,
>>
>> I'm currently working on a large legacy application stack, using Java 8, 
>> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
>> frontend technology stack includes GWT version 2.8.2 and GXT version 
>> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>>
>> In my initial approach to modernize the application, I began by migrating 
>> Hibernate to version 6.2, assuming it would be the easiest step. However, I 
>> encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
>> 

[gwt-contrib] Re: Seeking Advice on Legacy Application Migration Strategy

[Jens]

I would first focus on upgrading Java, GWT and possibly GXT if it is 
incompatible with newest GWT. The DataSource error will go away once you 
upgrade GWT because newer GWT versions use a newer Jetty. Keep in mind that 
in newest GWT the use of embedded Jetty as appliction server during 
development has been deprecated. It is preferred to use a local jetty 
installation, a docker container or launching jetty via a build tool plugin 
(maven / gradle).

Once you have upgraded to latest GWT you have the possibility to use GWT 
2.11-jakarta if you need to switch to Jakarta.

GWT itself only supports Hibernate 4 validation. So if the application uses 
Hibernate validation in GWT as well, then you likely need to 
use https://gitlab.com/ManfredTremmel/gwt-bean-validators

-- J.

Wejden Mrabti schrieb am Donnerstag, 25. April 2024 um 15:59:45 UTC+2:

> Hello GWT Community,
>
> I'm currently working on a large legacy application stack, using Java 8, 
> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
> frontend technology stack includes GWT version 2.8.2 and GXT version 
> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>
> In my initial approach to modernize the application, I began by migrating 
> Hibernate to version 6.2, assuming it would be the easiest step. However, I 
> encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
> Persistence. When attempting to compile parts of my codebase, I received 
> the following error:
>
> java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has 
> been compiled by a more recent version of the Java Runtime (class file 
> version 55.0), this version of the Java Runtime only recognizes class file 
> versions up to 52.0
>
> This suggests that I need to execute my code with JDK 11. However, when 
> attempting to do so, I encountered the following issue:
>
> [ERROR] Found resouce but unrecognized URL format: 
> 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
> javax/sql/DataSource
>
> After reviewing your discussions in the GWT contributors group, I'm 
> questioning whether starting with the Hibernate migration is the right 
> approach. Should I instead prioritize migrating Java or perhaps GWT? I 
> would greatly appreciate your insights and advice based on your experiences.
>
> Thank you,
>
> WM
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/d52d9aa6-5cc0-4f5b-be14-907bf758d2ecn%40googlegroups.com.

Re: Seeking Advice on Legacy Application Migration Strategy

[Colin Alworth]

You might run into issues with such an old version of GXT when using a new 
GWT version - take a look at 
https://groups.google.com/g/google-web-toolkit/c/If897MPqvw0/m/bSWnmuz9BwAJ 
for a summary of how to update GXT 2.3.1a-gwt22. 

With GWT updated to 2.9.0 or beyond, you will be able to run on Java 11 
(see https://www.gwtproject.org/release-notes.html#Release_Notes_2_9_0). 




On Friday, April 26, 2024 at 7:59:27 AM UTC-5 wejden...@gmail.com wrote:

> Many thanks @frank Hossfeld, 
> I am so excited to start it .. it is clear 
> please feel free to share any references or links that can help me in that 
> adventure .
>
> thank you
> wm
>
> Le ven. 26 avr. 2024 à 11:50, 'Frank Hossfeld' via GWT Users <
> google-we...@googlegroups.com> a écrit :
>
>> GWT 2.8.2 is pretty old - nearly seven years - and i am not sure, if the 
>> GWT 2.8.2 will work with Java 11
>>
>> Migrating to the latest version of GWT will give you some benefits. IIRC 
>> GWT 2.8.2 generates at least 5 JS-files where GWT 2.11.0 only generates 2. 
>> This will speed up the build. Also, there is a security issue in older GWT 
>> versions (in case you are using RPC). 
>>
>> To do so, separate your code in client-, shared- and server-modules (as 
>> Craig already mentioned).  Take a look here: 
>> https://github.com/tbroyer/gwt-maven-archetypes or here 
>> https://github.com/NaluKit/gwt-maven-springboot-archetype. This should 
>> give you an idea, how your project look like after the separation. Once 
>> done, it should be possible to use different Java versions on the client 
>> and server side.
>>
>> Once you have separate your code, you can update the GWT version. My 
>> first step would be to update to GWT 2.10.0. I would do this, because to 
>> GWT 2.10.0 works with the old javax stuff on the server side and give you 
>> the opportunity to patch GXT without updating the server stuff.  (IIRC you 
>> need to patch two classes). After the patch you can move to GWT 2.11.0 and 
>> Java 11 and fix the other issues by updating versions, etc.
>>
>> Wejden Mrabti schrieb am Freitag, 26. April 2024 um 09:12:33 UTC+2:
>>
>>> thank you for your answer @craig Mitchell
>>> if i want to continue hibernate 6 , how to do launch gwt application on 
>>> java 11 ? 
>>> is it possible to continue working like this ? what do you think?
>>> Le vendredi 26 avril 2024 à 02:22:52 UTC+2, Craig Mitchell a écrit :
>>>
 It'd be hard to answer that question, as we don't have all the 
 details.  As this is a GWT forum, I'd say, migrate GWT to the latest 
 version first.  But that might actually be bad advice, just depends on 
 your 
 project.

 My gut feel is you'd be best to decouple the front end and back end 
 first.

 On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:

> Hello GWT Users Community,
>
> I'm currently working on a large legacy application stack, using Java 
> 8, Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
> frontend technology stack includes GWT version 2.8.2 and GXT version 
> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>
> In my initial approach to modernize the application, I began by 
> migrating Hibernate to version 6.2, assuming it would be the easiest 
> step. 
> However, I encountered an issue where Hibernate 6.2 requires 
> transitioning 
> to Jakarta Persistence. When attempting to compile parts of my codebase, 
> I 
> received the following error:
>
> java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient 
> has been compiled by a more recent version of the Java Runtime (class 
> file 
> version 55.0), this version of the Java Runtime only recognizes class 
> file 
> versions up to 52.0
>
> This suggests that I need to execute my code with JDK 11. However, 
> when attempting to do so, I encountered the following issue:
>
> [ERROR] Found resouce but unrecognized URL format: 
> 'jrt:/java.sql/javax/sql/DataSource.class' 
> java.lang.NoClassDefFoundError: 
> javax/sql/DataSource
>
> After reviewing your discussions in the GWT contributors group, I'm 
> questioning whether starting with the Hibernate migration is the right 
> approach. Should I instead prioritize migrating Java or perhaps GWT? I 
> would greatly appreciate your insights and advice based on your 
> experiences.
>
> Thank you,
>
> WM
>
 -- 
>> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/a91eb3fa-af37-4c37-bc61-010bbd151763n%40googlegroups.com
>>  
>> 

Re: Seeking Advice on Legacy Application Migration Strategy

[Wejden Mrabti]

Many thanks @frank Hossfeld,
I am so excited to start it .. it is clear
please feel free to share any references or links that can help me in that
adventure .

thank you
wm

Le ven. 26 avr. 2024 à 11:50, 'Frank Hossfeld' via GWT Users <
google-web-toolkit@googlegroups.com> a écrit :

> GWT 2.8.2 is pretty old - nearly seven years - and i am not sure, if the
> GWT 2.8.2 will work with Java 11
>
> Migrating to the latest version of GWT will give you some benefits. IIRC
> GWT 2.8.2 generates at least 5 JS-files where GWT 2.11.0 only generates 2.
> This will speed up the build. Also, there is a security issue in older GWT
> versions (in case you are using RPC).
>
> To do so, separate your code in client-, shared- and server-modules (as
> Craig already mentioned).  Take a look here:
> https://github.com/tbroyer/gwt-maven-archetypes or here
> https://github.com/NaluKit/gwt-maven-springboot-archetype. This should
> give you an idea, how your project look like after the separation. Once
> done, it should be possible to use different Java versions on the client
> and server side.
>
> Once you have separate your code, you can update the GWT version. My first
> step would be to update to GWT 2.10.0. I would do this, because to GWT
> 2.10.0 works with the old javax stuff on the server side and give you the
> opportunity to patch GXT without updating the server stuff.  (IIRC you need
> to patch two classes). After the patch you can move to GWT 2.11.0 and Java
> 11 and fix the other issues by updating versions, etc.
>
> Wejden Mrabti schrieb am Freitag, 26. April 2024 um 09:12:33 UTC+2:
>
>> thank you for your answer @craig Mitchell
>> if i want to continue hibernate 6 , how to do launch gwt application on
>> java 11 ?
>> is it possible to continue working like this ? what do you think?
>> Le vendredi 26 avril 2024 à 02:22:52 UTC+2, Craig Mitchell a écrit :
>>
>>> It'd be hard to answer that question, as we don't have all the details.
>>> As this is a GWT forum, I'd say, migrate GWT to the latest version first.
>>> But that might actually be bad advice, just depends on your project.
>>>
>>> My gut feel is you'd be best to decouple the front end and back end
>>> first.
>>>
>>> On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:
>>>
 Hello GWT Users Community,

 I'm currently working on a large legacy application stack, using Java
 8, Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our
 frontend technology stack includes GWT version 2.8.2 and GXT version
 2.3.1a-gwt22. Fontend and backend arent well de-coupled.

 In my initial approach to modernize the application, I began by
 migrating Hibernate to version 6.2, assuming it would be the easiest step.
 However, I encountered an issue where Hibernate 6.2 requires transitioning
 to Jakarta Persistence. When attempting to compile parts of my codebase, I
 received the following error:

 java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient
 has been compiled by a more recent version of the Java Runtime (class file
 version 55.0), this version of the Java Runtime only recognizes class file
 versions up to 52.0

 This suggests that I need to execute my code with JDK 11. However, when
 attempting to do so, I encountered the following issue:

 [ERROR] Found resouce but unrecognized URL format:
 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError:
 javax/sql/DataSource

 After reviewing your discussions in the GWT contributors group, I'm
 questioning whether starting with the Hibernate migration is the right
 approach. Should I instead prioritize migrating Java or perhaps GWT? I
 would greatly appreciate your insights and advice based on your 
 experiences.

 Thank you,

 WM

>>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/a91eb3fa-af37-4c37-bc61-010bbd151763n%40googlegroups.com
> 
> .
>


-- 

*Best Regards,*
*Wejden MRABTI*

Ingénieur étude et développement

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CADMk%2BV%2BKpb89x9QN2%3DqXoaK3MDrtMN%2BMss%2BJ7CQ1YrevYr8q1w%40mail.gmail.com.

Re: Seeking Advice on Legacy Application Migration Strategy

['Frank Hossfeld' via GWT Users]

GWT 2.8.2 is pretty old - nearly seven years - and i am not sure, if the 
GWT 2.8.2 will work with Java 11

Migrating to the latest version of GWT will give you some benefits. IIRC 
GWT 2.8.2 generates at least 5 JS-files where GWT 2.11.0 only generates 2. 
This will speed up the build. Also, there is a security issue in older GWT 
versions (in case you are using RPC). 

To do so, separate your code in client-, shared- and server-modules (as 
Craig already mentioned).  Take a look 
here: https://github.com/tbroyer/gwt-maven-archetypes or 
here https://github.com/NaluKit/gwt-maven-springboot-archetype. This should 
give you an idea, how your project look like after the separation. Once 
done, it should be possible to use different Java versions on the client 
and server side.

Once you have separate your code, you can update the GWT version. My first 
step would be to update to GWT 2.10.0. I would do this, because to GWT 
2.10.0 works with the old javax stuff on the server side and give you the 
opportunity to patch GXT without updating the server stuff.  (IIRC you need 
to patch two classes). After the patch you can move to GWT 2.11.0 and Java 
11 and fix the other issues by updating versions, etc.

Wejden Mrabti schrieb am Freitag, 26. April 2024 um 09:12:33 UTC+2:

> thank you for your answer @craig Mitchell
> if i want to continue hibernate 6 , how to do launch gwt application on 
> java 11 ? 
> is it possible to continue working like this ? what do you think?
> Le vendredi 26 avril 2024 à 02:22:52 UTC+2, Craig Mitchell a écrit :
>
>> It'd be hard to answer that question, as we don't have all the details.  
>> As this is a GWT forum, I'd say, migrate GWT to the latest version first.  
>> But that might actually be bad advice, just depends on your project.
>>
>> My gut feel is you'd be best to decouple the front end and back end first.
>>
>> On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:
>>
>>> Hello GWT Users Community,
>>>
>>> I'm currently working on a large legacy application stack, using Java 8, 
>>> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
>>> frontend technology stack includes GWT version 2.8.2 and GXT version 
>>> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>>>
>>> In my initial approach to modernize the application, I began by 
>>> migrating Hibernate to version 6.2, assuming it would be the easiest step. 
>>> However, I encountered an issue where Hibernate 6.2 requires transitioning 
>>> to Jakarta Persistence. When attempting to compile parts of my codebase, I 
>>> received the following error:
>>>
>>> java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient 
>>> has been compiled by a more recent version of the Java Runtime (class file 
>>> version 55.0), this version of the Java Runtime only recognizes class file 
>>> versions up to 52.0
>>>
>>> This suggests that I need to execute my code with JDK 11. However, when 
>>> attempting to do so, I encountered the following issue:
>>>
>>> [ERROR] Found resouce but unrecognized URL format: 
>>> 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
>>> javax/sql/DataSource
>>>
>>> After reviewing your discussions in the GWT contributors group, I'm 
>>> questioning whether starting with the Hibernate migration is the right 
>>> approach. Should I instead prioritize migrating Java or perhaps GWT? I 
>>> would greatly appreciate your insights and advice based on your experiences.
>>>
>>> Thank you,
>>>
>>> WM
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/a91eb3fa-af37-4c37-bc61-010bbd151763n%40googlegroups.com.

Re: Seeking Advice on Legacy Application Migration Strategy

[Wejden Mrabti]

thank you for your answer @craig Mitchell
if i want to continue hibernate 6 , how to do launch gwt application on 
java 11 ? 
is it possible to continue working like this ? what do you think?
Le vendredi 26 avril 2024 à 02:22:52 UTC+2, Craig Mitchell a écrit :

> It'd be hard to answer that question, as we don't have all the details.  
> As this is a GWT forum, I'd say, migrate GWT to the latest version first.  
> But that might actually be bad advice, just depends on your project.
>
> My gut feel is you'd be best to decouple the front end and back end first.
>
> On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:
>
>> Hello GWT Users Community,
>>
>> I'm currently working on a large legacy application stack, using Java 8, 
>> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
>> frontend technology stack includes GWT version 2.8.2 and GXT version 
>> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>>
>> In my initial approach to modernize the application, I began by migrating 
>> Hibernate to version 6.2, assuming it would be the easiest step. However, I 
>> encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
>> Persistence. When attempting to compile parts of my codebase, I received 
>> the following error:
>>
>> java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has 
>> been compiled by a more recent version of the Java Runtime (class file 
>> version 55.0), this version of the Java Runtime only recognizes class file 
>> versions up to 52.0
>>
>> This suggests that I need to execute my code with JDK 11. However, when 
>> attempting to do so, I encountered the following issue:
>>
>> [ERROR] Found resouce but unrecognized URL format: 
>> 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
>> javax/sql/DataSource
>>
>> After reviewing your discussions in the GWT contributors group, I'm 
>> questioning whether starting with the Hibernate migration is the right 
>> approach. Should I instead prioritize migrating Java or perhaps GWT? I 
>> would greatly appreciate your insights and advice based on your experiences.
>>
>> Thank you,
>>
>> WM
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5e426237-abc7-4ead-bb46-7963e9891d00n%40googlegroups.com.

Re: Seeking Advice on Legacy Application Migration Strategy

[Craig Mitchell]

It'd be hard to answer that question, as we don't have all the details.  As 
this is a GWT forum, I'd say, migrate GWT to the latest version first.  But 
that might actually be bad advice, just depends on your project.

My gut feel is you'd be best to decouple the front end and back end first.

On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:

> Hello GWT Users Community,
>
> I'm currently working on a large legacy application stack, using Java 8, 
> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
> frontend technology stack includes GWT version 2.8.2 and GXT version 
> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>
> In my initial approach to modernize the application, I began by migrating 
> Hibernate to version 6.2, assuming it would be the easiest step. However, I 
> encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
> Persistence. When attempting to compile parts of my codebase, I received 
> the following error:
>
> java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has 
> been compiled by a more recent version of the Java Runtime (class file 
> version 55.0), this version of the Java Runtime only recognizes class file 
> versions up to 52.0
>
> This suggests that I need to execute my code with JDK 11. However, when 
> attempting to do so, I encountered the following issue:
>
> [ERROR] Found resouce but unrecognized URL format: 
> 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
> javax/sql/DataSource
>
> After reviewing your discussions in the GWT contributors group, I'm 
> questioning whether starting with the Hibernate migration is the right 
> approach. Should I instead prioritize migrating Java or perhaps GWT? I 
> would greatly appreciate your insights and advice based on your experiences.
>
> Thank you,
>
> WM
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e72ddd8b-24f3-41dd-b4fa-52d2f860f07cn%40googlegroups.com.

Seeking Advice on Legacy Application Migration Strategy

[Wejden Mrabti]

Hello GWT Users Community,

I'm currently working on a large legacy application stack, using Java 8, 
Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
frontend technology stack includes GWT version 2.8.2 and GXT version 
2.3.1a-gwt22. Fontend and backend arent well de-coupled.

In my initial approach to modernize the application, I began by migrating 
Hibernate to version 6.2, assuming it would be the easiest step. However, I 
encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
Persistence. When attempting to compile parts of my codebase, I received 
the following error:

java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has 
been compiled by a more recent version of the Java Runtime (class file 
version 55.0), this version of the Java Runtime only recognizes class file 
versions up to 52.0

This suggests that I need to execute my code with JDK 11. However, when 
attempting to do so, I encountered the following issue:

[ERROR] Found resouce but unrecognized URL format: 
'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
javax/sql/DataSource

After reviewing your discussions in the GWT contributors group, I'm 
questioning whether starting with the Hibernate migration is the right 
approach. Should I instead prioritize migrating Java or perhaps GWT? I 
would greatly appreciate your insights and advice based on your experiences.

Thank you,

WM

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/dea97a11-0e1d-471a-8de6-9b92a79f0187n%40googlegroups.com.

[gwt-contrib] Seeking Advice on Legacy Application Migration Strategy

[Wejden Mrabti]

Hello GWT Community,

I'm currently working on a large legacy application stack, using Java 8, 
Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
frontend technology stack includes GWT version 2.8.2 and GXT version 
2.3.1a-gwt22. Fontend and backend arent well de-coupled.

In my initial approach to modernize the application, I began by migrating 
Hibernate to version 6.2, assuming it would be the easiest step. However, I 
encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
Persistence. When attempting to compile parts of my codebase, I received 
the following error:

java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has 
been compiled by a more recent version of the Java Runtime (class file 
version 55.0), this version of the Java Runtime only recognizes class file 
versions up to 52.0

This suggests that I need to execute my code with JDK 11. However, when 
attempting to do so, I encountered the following issue:

[ERROR] Found resouce but unrecognized URL format: 
'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
javax/sql/DataSource

After reviewing your discussions in the GWT contributors group, I'm 
questioning whether starting with the Hibernate migration is the right 
approach. Should I instead prioritize migrating Java or perhaps GWT? I 
would greatly appreciate your insights and advice based on your experiences.

Thank you,

WM

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1ab55db1-72aa-423d-9b06-c238993208fdn%40googlegroups.com.