Migrating from 2.5.0 to 2.7.0

[flosanlop17]

I am currently migrating an application that uses GWT version 2.5.0, I am trying to migrate it, I have already updated some libraries that conflicted with this new version and I have solved some problems.

Currently the compilation is successful, and I manage to deploy to my local Oracle Weblogic Server, but when I analyze the HTTP requests with BurpSuite, I see that apparently they are loading cache files that point to version 2.5.0, someone could explain me why this happens and how I could solve it...

I share the cache files in my local seem to be updated, and indeed the compilation is generated on version 2.7.0 as seen in the following images

But when the first requests are made to enter the application it is observed that it loads a cache file that points to version 2.5.0, as shown in the image below.



Thank you very much for your help

[Colin Alworth]

Its a bit hard to read the screenshots, but it looks like the file your browser/burp network log shows isn't one that even exists in your project? If those bytes were indeed sent over the wire and the old ...15.cache.html file was not present anywhere in your workspace or generated production code (date is 27 Dec, but last-modified is 21 Dec...), I would guess that either you have a proxy helping and incorrectly caching beyond what it should, or the server deployment somehow didn't replace all of the old files.

Also check what the contents of your .nocache.js file, as that is probably either stale or incorrectly cached by the browser/proxy/both. Note that this file should have changed dramatically - your old ...15.cache.html file ends in ".html", but all of the new files are .cache.js instead, so you've switched linkers as well during your upgrade.

Finally please note that GWT 2.7.0 is a little over 9 years old, so it might make sense to keep updating, and see if you can get to GWT 2.10 (and the 2.11 release process is starting soon).

[flosanlop17]

The deployment on the server did not run successfully, although it looked like it did, apparently it had not replaced the files.

I recompiled the project, generated a new deployment and restarted my Weblogic Oracle server and it worked perfectly, thank you very much for your help.