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 [email protected] 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 < >> [email protected]> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/google-web-toolkit/a91eb3fa-af37-4c37-bc61-010bbd151763n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/google-web-toolkit/a91eb3fa-af37-4c37-bc61-010bbd151763n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> >> *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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/db1cfa0b-44ce-4bd3-a803-3e1e86b0e2f6n%40googlegroups.com.
