Thursday, February 18, 2021

Re: GWT 2.9 compatiblity with GXT 2.3.1a

I tried changing GWT to 2.9 and GXT 2.3.1a-gwt22.jar, most of the errors were because of the method name changes like you mentioned ContentPanel.setHeading being changed to html specific setters and getters, but one issue which i am not able to figure out is below error, 

[Error]  Error in 'com/extjs/gxt/ui/client/widget/' 
[Error]  Line 816: Type mismatch: cannot convert from Node to Element

and this error is cascading to all the classes using ListView widget. Any idea on this specific issue?
On Friday, February 19, 2021 at 1:25:50 AM UTC+5:30 Ricardo Serathiuk wrote:
We have successfully updated a big ERP application. First of all, we have changed the GWT version to a new version. After that, we have fixed all the errors. I don't remember all the steps, because It was years ago. Some methods were removed on GXT 2.3.1.a, for example the ContentPanel.setHeading. In our case, the migration was easy because We never use the GXT components directly. At the project beginning, We have extended all the GXT components, and We have been using the extended components in our code. We have recreated the removed methods in our classes and overload them with the replacement method. We have made the changes in XImages to extend ClientBundle, as described in my last message too. The app has been working for years with these changes.

I believe the major big step is to try to change the GWT version to evaluate the impact.

On Thu, Feb 18, 2021 at 3:32 PM Hari <> wrote:
Hi we are trying to upgrade as well with GXT 2.3.1a  and GWT 2.9.0, could you please let me know if you were successful in your upgrade and any pitfalls which we need to be avoid.

On Thursday, June 11, 2020 at 7:52:57 PM UTC+5:30 Ricardo Serathiuk wrote:
When we have migrated to GWT 2.6, We changed the GXT com.extjs.gxt.ui.client.image.XImages class to extend ClientBundle and changed its methods to return an ImageResource. After that, we changed the components to utilize ImageResource instead of AbstractImagePrototype. We made some other minor fixes which I don't remember now. We have been using newer versions since its launch without problems with these modifications. We have tested the version GWT 2.9.0 with this update and worked fine for us.

Priya said about version GWT 2.8.2, because of that I believe her company has made some updates on GXT by yourselves. And about the migration from 2.8.2 to 2.9.0, in my company, we haven't had problems with that. :)

Em quinta-feira, 11 de junho de 2020 10:36:21 UTC-3, Colin Alworth escreveu:
There are multiple problems with using GXT 2.x with a recent version of GWT (anything since GWT 2.6 or so, released in 2014). Sencha hasn't offered support for GXT 2 since version 4 was released (and doesn't appear to provide support for GXT 4 any longer either), but the last time I ran into this, I was able to successfully change a few .java files in the jar and recompile to continue using GXT 2.

But as Michael said, while GWT 2.6, 2.7, 2.8, 2.9 have added features and browser support, these will not necessarily help old GXT builds to have bug fixes also, though it may still improve your compiled output size and runtime performance.

On Thursday, June 11, 2020 at 7:13:31 AM UTC-5, Priya Kolekar wrote:
Hi All,

Currently our application has below versions -
1. GWT - 2.8.2
2. GXT - 2.3.1a

We are planning to upgrade GWT from 2.8.2 to 2.9.0. But have query regarding its compatibility towards GXT 2.3.1a.
I have gone through GXT Compatiblity version matrix page, but found nowhere officially mentioned that its supported.
So can you please confirm that GWT 2.9 is officially supported with GXT 2.3.1a?

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

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
To view this discussion on the web visit

No comments:

Post a Comment