Tuesday, July 19, 2022

Re: [WARN] 404 - GET //10.14.0.224:8888/sampleapp/sampleapp.nocache.js

I thought you had to put a "-bindAddress 0.0.0.0" to get access to your actual IP address.

Have you tried accessing it from http://127.0.0.1:8888/ ?

On Wednesday, 20 July 2022 at 12:32:02 am UTC+10 frank.h...@googlemail.com wrote:
Inside your module descriptor, is the rename-to attribute of the module tag also "sampleapp"?

abhiy...@gmail.com schrieb am Montag, 18. Juli 2022 um 19:18:00 UTC+2:
Hello Everyone,

I am getting below error when trying to start application through GWT plugin in eclipse. I am using GWT 2.9.0. I have renamed my module to sampleapp and in the html file I have used the below script in html file
 <script type="text/javascript" language="javascript" src="sampleapp/sampleapp.nocache.js"></script>

07:18 20:56:17 |  INFO | [main] | org.eclipse.jetty.server.handler.ContextHandler:doStart(824) | Started c.g.g.d.s.j.WebAppContextWithReload@238d3e2d{}
07:18 20:56:18 |  INFO | [main] | org.eclipse.jetty.server.AbstractConnector:doStart(330) | Started ServerConnector@6e4484d6{HTTP/1.1,[http/1.1]}{0.0.0.0:8888}
07:18 20:56:18 |  INFO | [main] | org.eclipse.jetty.server.Server:doStart(399) | Started @32366ms
[WARN] 404 - GET //10.14.0.224:8888/ sampleapp/sampleapp.nocache.js (10.14.0.224)
   Request headers
      Host: 10.14.0.224:8888
      Connection: keep-alive
      User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36
      Accept: */*
      Referer: http://10.14.0.224:8888/sampleapp.html
      Accept-Encoding: gzip, deflate
      Accept-Language: en-US,en;q=0.9
   Response headers
      Cache-Control: must-revalidate,no-cache,no-store
      Content-Type: text/html;charset=iso-8859-1

--
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/cf04a5d4-d0bf-4c33-913c-6a2f3f302b78n%40googlegroups.com.

Re: [WARN] 404 - GET //10.14.0.224:8888/sampleapp/sampleapp.nocache.js

Inside your module descriptor, is the rename-to attribute of the module tag also "sampleapp"?

abhiy...@gmail.com schrieb am Montag, 18. Juli 2022 um 19:18:00 UTC+2:
Hello Everyone,

I am getting below error when trying to start application through GWT plugin in eclipse. I am using GWT 2.9.0. I have renamed my module to sampleapp and in the html file I have used the below script in html file
 <script type="text/javascript" language="javascript" src="sampleapp/sampleapp.nocache.js"></script>

07:18 20:56:17 |  INFO | [main] | org.eclipse.jetty.server.handler.ContextHandler:doStart(824) | Started c.g.g.d.s.j.WebAppContextWithReload@238d3e2d{}
07:18 20:56:18 |  INFO | [main] | org.eclipse.jetty.server.AbstractConnector:doStart(330) | Started ServerConnector@6e4484d6{HTTP/1.1,[http/1.1]}{0.0.0.0:8888}
07:18 20:56:18 |  INFO | [main] | org.eclipse.jetty.server.Server:doStart(399) | Started @32366ms
[WARN] 404 - GET //10.14.0.224:8888/ sampleapp/sampleapp.nocache.js (10.14.0.224)
   Request headers
      Host: 10.14.0.224:8888
      Connection: keep-alive
      User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36
      Accept: */*
      Referer: http://10.14.0.224:8888/sampleapp.html
      Accept-Encoding: gzip, deflate
      Accept-Language: en-US,en;q=0.9
   Response headers
      Cache-Control: must-revalidate,no-cache,no-store
      Content-Type: text/html;charset=iso-8859-1

--
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/5af94871-9887-4280-9429-717c3ac7f5a6n%40googlegroups.com.

Monday, July 18, 2022

Re: Compatibility of GWT 2.10.0 with GXT 2.3.1.a

I work with an application using GWT 2.10.0 and GXT 2.3.1a. We have fixed some things on GXT 2.3.1a. With some fixes, you can run perfectly the GXT 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0 included).

--
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/CALVte5yNoDPQVr8FNud29EMMUM8EEyqHJyawqjjrc1j3xWHY2w%40mail.gmail.com.

Re: Compatibility of GWT 2.10.0 with GXT 2.3.1.a

In an ideal world, you'd reach out to those libs' maintainers and ask them if their lib is compatible with GWT 2.10.
But those are all libs that haven't had a new release in a decade:
* GXT 2.3.1.a was released in 2014
* GWTx 1.5.3 was released 2009 (GWT 2.0.0 wasn't even released at the time!)
* log4j-gwt 1.0 was released in 2012

You're quite fortunate that GWT has a rather extraordinary backward compatibility track and such a combination might still work with 2.10.0, but nobody in their own mind should even try that unless they're desperate.
If you're going to spend time on something, spend it on removing those outdated, unmaintained libs (you had between 8 and 13 years to do it already, but it's never too late). Stay on an older GWT version for as long as you can, but remove those libs (if you share code with the JVM that uses log4j –still using log4j 1.x? hope you migrated to reload4j–, then rewrite/copy the few bits that need to be emulated; for GXT and GWTx, replace with your own code or possibly another –maintained– lib).
If the project isn't worth it, then it's probably not worth either spending time updating to GWT 2.10 and make sure everything still works.

So first, let me ask: why do you want to update to GWT 2.10?

On Monday, July 18, 2022 at 6:56:23 AM UTC+2 priyako...@gmail.com wrote:
Hello Team,

we use following jars in our application - 
GXT .jar -        2.3.1.a
GWTx.jar -       1.5.3
Log4j-gwt.jar - 1.0

Wanted to know that will recent update of GWT 2.10.0 compatible with above dependencies.

--
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/3dceeda3-39b2-4b28-a972-20e686149d44n%40googlegroups.com.

Re: Compatibility of GWT 2.10.0 with GXT 2.3.1.a

GWT packages have still the same name. AFAIK, there are no changes on package names.
In case you start using GWT modules, you will have to use the packages starting with 'org.gwtproject'. 

Starting with GWT 2.10.0 you can 'com.google.gwt' or 'org.gwtproject' as groupId inside the Maven dependency. Starting with one of the next release of GWT, only the 'org.gwtproject' groupId can be used.  

leon.p...@gmail.com schrieb am Montag, 18. Juli 2022 um 15:33:09 UTC+2:
From what I gathered, packages have been renamed from **.google.** to **gwtproject** or smth.
So without a gxt update to cover for the new packages, I doubt you can upgrade your project.

There is one simple way to check, just update the GWT version in your dependency manager (maven or whatever you use) and you'll find out soon enough.
 
Op maandag 18 juli 2022 om 06:56:23 UTC+2 schreef priyako...@gmail.com:
Hello Team,

we use following jars in our application - 
GXT .jar -        2.3.1.a
GWTx.jar -       1.5.3
Log4j-gwt.jar - 1.0

Wanted to know that will recent update of GWT 2.10.0 compatible with above dependencies.

--
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/7c2e3720-6129-441f-906d-d3e2f3f5d21dn%40googlegroups.com.

Thursday, July 14, 2022

Re: GWT 2.10.0 release

Hello All,
Good to see that new version of GWT coming with new features!!!
Is the new 2.10.0 GWT version compatible with Sencha GXT 2.3.1.a ? 
Will appreciate an early reply! 

On Sat, Jul 2, 2022 at 1:40 AM Mihail Krastev <mkrastev.bg@gmail.com> wrote:
Really good job, thanks to everyone involved!

On Thursday, June 23, 2022 at 7:16:50 PM UTC+3 nilo...@gmail.com wrote:
I'm very happy to announce the release of GWT 2.10.0. This is the first release using our new groupId, org.gwtproject, and the final release using com.google.gwt. If you resolve dependencies from Maven Central, please be certain that your project is using com.google.gwt:gwt (or org.gwtproject:gwt) as a BOM, so that you are certain to have consistent versions of gwt-user and gwt-dev, even across groupIds.

For this release, either groupId will work, but future releases will only be made on the org.gwtproject groupId.


--


Highlights
  • Updated to HtmlUnit 2.55.0 and Jetty 9.4.44. With this newer HtmlUnit build comes support for Promise in unit tests, and the browser strings that can be specified when running tests are "FF", "Chrome", "IE" (for IE11), "Edge", and "Safari".

  • Tested support for running on Java 17, dropped remaining support for running on Java 7.

  • Maven groupId is formally changed to org.gwtproject, projects should take care to make sure they are using either the old com.google.gwt:gwt BOM or the new org.gwtproject:gwt BOM to sure that Maven or Gradle correctly handle this change. This will be the last published version using the com.google.gwt groupId.

  • Dropped support for IE 8, 9, and 10.

Bug fixes
  • Correct Long.hashCode semantics
  • Support CLASSPATH environment variable when creating child processes, fixing a bug where Windows could fail with a long list of arguments.
  • Use Function.name instead of displayName to support visible method names in Chrome 93+.
  • Allow stack traces to be available in Chrome when loading scripts from a remote origin.
JRE Emulation
  • Added OutputStreamWriter emulation.
  • Support StringReader mark() and reset() methods.
  • Added StrictMath emulation.
  • Added BufferedWriter emulation.
  • Added incomplete PrintStream emulation.
  • Add Charset.defaultCharset() emulation.
  • Improve BigInteger emulated performance.
  • System.nanoTime() emulation with performance.now().
  • Added Optional.isEmpty emulation.
  • JRE Emulation improvements/simplifications to facilitate J2CL's WASM support. Note that these do not always offer specific improvements to GWT itself, but helps to keep the codebases consistent.
Miscellaneous
  • Add support to compile GWT itself in Java 9+.
  • Improve compiled code size for applications that never use streams, by avoiding referencing streams from Throwable.

For more detail, see the commit log.

--
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/af5e74c8-4f62-46d2-a29a-f28203555e32n%40googlegroups.com.


--
Life is Beautiful..........
Keep Smiling!!!!!!!!
Priya......

--
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/CANu4zMz%3D%3DnaWtdQ88JLF%3DsNEddPpLu91KsOkqLiGD9hV9TWqBA%40mail.gmail.com.

Wednesday, July 13, 2022

Re: net.ltgt.gwt.maven and testing in multi-module project structure?



On Wednesday, July 13, 2022 at 3:06:37 AM UTC+2 ime...@gmail.com wrote:
Thank you, the setting the <include> did it.

FYI, using a GWTTestSuite can improve performance (that's why it's the default in the plugin, because it favors best practices): https://www.gwtproject.org/doc/latest/DevGuideTesting.html#DevGuideJUnitSuites
 
My next question about testing is, what are the expectations for the test module? Are we still required to provide a separate JUnit.gwt.xml?

You've never been (or at least not for many many years) as GWT will synthesize a module that inherits both com.google.gwt.junit.JUnit and the module your GWTTestCase's getModuleName() returns.
The gwt-maven-plugin itself has no specific expectations either, so https://www.gwtproject.org/doc/latest/DevGuideTesting.html should apply as-is (I haven't re-read it though, but that's the goal of the plugin, to be a "thin" wrapper that only wires things that are specific to Maven, e.g. src/main/java, computing the classpath from dependencies, etc.)

--
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/0a37ffc8-a2e6-4412-9cc0-4011b0fedde4n%40googlegroups.com.