The short answer is yes, you need to do this for each such bug you find, and if you have a commercial license, you need to do it yourself - the only way to distribute fixes for things like this is under GPLv2, which may not be something you want in your project as a dependency.
If this is a gwt compiler error, editing bytecode is not sufficient, as GWT consumes the source each time it builds. You probably should also update the bytecode if you update the source files. Only the file in question needs to be edited in this way (HtmlEditor, ListField are the ones I know of).
Do not replace with a .toString() call, in case the model holds an explicit null value, casting to object will use StringBuilder.append(Object), which will be null safe, or pick some other null safe approach.
Sencha's release policy at the time was that they supported the last major release - this means that until GXT 4 was released, GXT 2 was supported, and got updates, but once 4.0.0 was available, GXT 2 was no longer supported. To my knowledge, GXT isn't receiving any updates at all any more. Combined with the license issues, it is hard to do more than discuss the possible fixes and how they could be applied.
On Thursday, October 14, 2021 at 11:08:14 PM UTC-5 RT wrote:
Yes, I agree changing the line in the GXT 2.3.1a ListField.java file from:sb.append(m.get(prop));To this:sb.append(m.get(prop).toString());Would seemingly fix the issue. However I would then need to compile this to a .class file to replace the one in the gxt-2.3.1a-gwt22,jar that I reference in my project and therein lies the problem. Must I track down all the dependencies for GXT and GWT so that I can do a full recompile from source just for this one line change? Or can I use a java byte code editor to simply insert the .toString() at the right place in the .class file for ListField? I'm not sure how to do that, so I'll have to read up on byte code editors as that seems easier than a full recompile - if I knew where and how to inject the .toString()However if the OP already had GXT 2.3.1a working with GWT 2.8.2 then I'm guessing they already had to do this operation, and may be able to provide some insight. Unless they were using Java 7 and this is only a Java 8 issue perhaps.On Wednesday, October 13, 2021 at 5:48:47 PM UTC-5 nilo...@gmail.com wrote:The updated JDT probably caused this (so that gwt 2.8.2 can support Java 8 language features) - at a guess you'll need to cast the result of m.get(prop) on that line to Object so that StringBuilder.append correctly uses the Object overload.On Wednesday, October 13, 2021 at 3:41:52 PM UTC-5 RT wrote:Hi, I am attempting to update to GWT 2.8.2 from 2.7.0 using GXT 2.3.1a however I get the following error:Errors in 'jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java'Line 322: The method append(boolean) is ambiguous for the type StringBufferHow were you able to get 2.8.2 working with 2.3.1a? I'm running Java 8 with compiler compliance set to 1.7On Thursday, June 11, 2020 at 7:13:31 AM UTC-5 priyako...@gmail.com wrote:Hi All,Currently our application has below versions -1. GWT - 2.8.22. GXT - 2.3.1aWe 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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/82fcc7c6-9397-470c-b76e-0c29dbf7ccdan%40googlegroups.com.