Re: Seeking Advice on Legacy Application Migration Strategy

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.

--

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6c9f0417-4999-433e-8c97-0dfadf5ee1c1n%40googlegroups.com.

Re: Seeking Advice on Legacy Application Migration Strategy

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+unsubscribe@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+unsubscribe@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

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+unsubscribe@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

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+unsubscribe@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

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+unsubscribe@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

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+unsubscribe@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.

Learn more about our updated Terms of Service

vaughnjjoan@gmail.com We're updating our Terms of Service on May 22, 2024, so we wanted to let you know ahead of time. These changes won't affect the way you use our services, but they should help make it easier for you to understand what to expect from Google — and what we expect from you — as you use our services. You can see the new terms here. We also summarized the changes at the bottom of this email. What do I need to do? If you're under the age required to manage your own Google Account: We sent this email to your parent or guardian so that they can help you understand our updates better. Please discuss this email with your parent or guardian to decide if you need to do anything different with your account. If you're a parent or guardian, and you allow your child to use the services: Please review the updates to our terms with your child and help them decide whether they need to make any changes to their account. Please remember that these terms apply to you and you're responsible for your child's activity on the services. If you're the administrator of a Google Workspace corporate or educational account and you've enabled your users to access Google Additional Services: Our new Terms of Service won't affect the Google Workspace agreement between Google and your organization. These new terms will only apply to those users to whom you've given access to Google Additional Services. You can always manage whether your users have access to Google Additional Services, and which ones, in your Admin console. If you're a Google Workspace reseller whose customers have enabled their users to access Google Additional Services: Our new Terms of Service won't affect your Google Workspace agreement with your customers. These new terms will only apply to your customers' users who've been given access to Google Additional Services. Your customers can always manage whether their users have access to Google Additional Services, and which ones, in their Admin console. If you're any other user of the services: Please read this email to understand our updated terms and your options for further action. If you agree to the new terms, no further action is needed. What's changing? You can review the new Google Terms of Service here. At a glance, here's what this update covers: Generative AI terms. We're moving our existing Generative AI Additional Terms to our main Terms of Service and adding other AI-related clarifications. For example – we won't claim ownership over original content generated by our AI-powered services. More clarity on abusive activity. We're providing more examples and details about abuse and interference with our services that isn't allowed. More details on limitations of liability. For users outside the US, we're adding clarifications to our limitations of liability and indemnity sections to avoid any misunderstandings in light of local laws or customs. More clarity on disputes. We're clarifying that if you violate our terms, our remedies aren't limited to suspension or termination of your access to the services, but may include other remedies under applicable law. If problems or disputes arise between us about these terms, you'll have the opportunity to describe the issues and address them. Updates to reflect how our services work. We're adding language about how our services work, and updating certain Google service brand names that have changed over time. For users based in the European Economic Area (EEA) only: In addition to the changes described above, we're adding more explanatory text to help you understand the legal concept of "guarantees" under EU and local law. For more details, please see this summary of key changes to the EEA versions of our Terms. If you don't agree to the new terms, you should remove your content and stop using the services. You can also end your relationship with us at any time, without penalty, by closing your Google Account. Thank you for using Google services! © 2024 Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland. You have received this email to update you about important changes to Google's Terms of Service.