IIRC you need to update a few classes of GXT to get it running with GWT 2.9.0+. And GWT 2.10.0 dropped the support for ie8, ie9 & ie10 which will also cause problems.
Jens schrieb am Mittwoch, 15. Februar 2023 um 13:21:38 UTC+1: > I am currently stuck with an error in a commercial GWT widget library that > our project uses (GXT v4.0.2). The code generated by that library contains > a bug: it contains a GWT.create(…)-call where the argument is an > interface and not a class. > > Actually GWT.create() usually takes an interface and during GWT > compilation that interface is either replaced by a class using GWT rebind > rules stored in any *.gwt.xml file or a GWT generator will be executed > (also defined in *.gwt.xml file) which generates a class that implements > that interface. Maybe you can find that rebind rule in any *.gwt.xml file > provided by GXT and then you might see why it fails to replace that > interface with a concrete class. You should be able to add your own custom > rebind rules then to fix the issue. > > But when I try to execute the application in development mode on a local > Tomcat then the compilation that is triggered in code server by the first > UI request yields this: > CodeServer has option -[no]failOnError. Have you tried that? > > But I could imagine that this kind of error will still be reported because > GWT wants to replace GWT.create() with new SomeClass() but does not know > how to do it. If -nofailOnError does not work you have to try fixing the > root cause of the issue as described above. > > -- J. > -- 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/8122fa52-e1b4-42e8-b7db-02660b657183n%40googlegroups.com.
