Re: GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

Currently, I'm working on installing WebLogic server 14 my in Eclipse for local deployment, however, I'm not sure if this is a better way for our local development as I don't have much experience with Weblogic server. The production WebLogic server on Linux is maintained by another group.  

Would Jetty or Tomcat server be a better choice in terms of easy configuration etc.? If so, we should install the latest version, right?

If your server side code does not need a complete Java EE 8 server then you could also use Jetty/Tomcat. Since WebLogic 14 supports Servlet API 4.0 your Jetty/Tomcat version should also support it. So for Jetty you would choose Jetty 10.x.

Jetty is relatively easy to configure, all you need to do is activating the modules/plugins you need. To deploy a *.war file to Jetty you would need the server, http and deploy module. You can basically do the quick setup in their documentation: https://www.eclipse.org/jetty/documentation/jetty-10/operations-guide/index.html#og-quick-setup

If you don't want to copy your war file into the jetty-base/webapps folder you could instead place a xml file into that folder which tells jetty where to find the *.war file, see: https://www.eclipse.org/jetty/documentation/jetty-10/operations-guide/index.html#og-deploy-jetty . Since Jetty can deploy exploded war folders that xml file could point directly to C:/Users/jiny/gitTestUpgrade/aries/war

-- 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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8a79f93b-2002-4633-8e9b-814800b2cae7n%40googlegroups.com.

commons-fields: lightweight and GWT compatible alternative to GraphQL

Over the last year I've put up a simple lib^H^H^H design pattern for working
with partially initialized object graphs. It is intended to be used both
client side *and* server side, it's GWT compatible and provides some
additional functionalities over GraphQL (in addition to tons of
functionalities from GraphQL missing, of course).

https://github.com/gkresic/commons-fields

For motivation and examples, see the Github wiki page.

Note: it isn't published and that was conscious decision: it is meant to be
used as *pattern*, customizing it for every particular project.

Another note: checkers getters (one that throw if a particular field isn't
initialized) works poorly with serialization libs. If you are using Jackson,
see FieldPropertyFilter in 'jackson' subproject and its usage in demo
subproject, but on the GWT side it's a bit more complicated, since neither
gwt-jackson nor domino-jackson support @JsonFilter.

I've created issue on this for gwt-jackson a long time ago, but nothing came
out of it:

https://github.com/nmorel/gwt-jackson/issues/164

So, for my own projects I'm maintaining (ugly) patched gwt-jackson available
here ('fields' branch):

https://github.com/gkresic/gwt-jackson/tree/fields

For example on how to build own CRUDFieldsService implementations, see
additional project:

https://github.com/gkresic/commons-fields-sql

Which uses yet another private lib (turtles all the way down...):

https://github.com/gkresic/commons-sql

If you prefer Hibernate/jOOQ or any other JDBC-alternative, it shouldn't be
hard to translate CRUDFieldsSqlService.java from commons-fields-sql (without
even looking at commons-sql) into some Hibernate/jOOQ alternative.

Comments welcome.

-gkresic.

--
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/b069add0-1648-86f4-05a0-f1b905a42e00%40steatoda.com.

Re: GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

Thanks a lot for your explanation. 

The thing that puzzled me was that the HTTP 503 error generated when the ear file was deployed to Weblogic 14 server. If the error and warning can be ignored, why did we encounter this HTTP 503 error? What is the best way to figure out what caused this server error?

Currently, I'm working on installing WebLogic server 14 my in Eclipse for local deployment, however, I'm not sure if this is a better way for our local development as I don't have much experience with Weblogic server. The production WebLogic server on Linux is maintained by another group. 

Would Jetty or Tomcat server be a better choice in terms of easy configuration etc.? If so, we should install the latest version, right?

Your help is much appreciated,

Jenny 

On Friday, June 25, 2021 at 5:01:19 AM UTC-5 Jens wrote:

The code server is ready at http://127.0.0.1:9876/

Code server started in 4.878 s ms

[ERROR] jreLeakPrevention.gcDaemonFail

java.lang.ClassNotFoundException: sun.misc.GC

This can be ignored. GWT's class JettyLauncher tries to fix a class loader memory leak within sun.misc.GC but this class does not exist in that package in Java 11. The exception is catched and logged as error, but code will continue.

java.lang.RuntimeException: Error scanning entry module-info.class from jar file:/C:/Users/jiny/gitTestUpgrade/aries/war/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)

at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)

at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)

at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM6

at org.objectweb.asm.ClassVisitor.visitModule(ClassVisitor.java:130)

at org.objectweb.asm.ClassReader.readModuleAttributes(ClassReader.java:724)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:544)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)

... 6 more

The embedded Jetty provided by GWT's DevMode class is too old to handle module-info.class files correctly during class file scanning. It basically requires newer ASM version.

The recommend approach for anything other than a small demo app is to not use the embedded Jetty provided by GWT DevMode. Instead use your own Jetty installation or a Jetty plugin for Gradle/Maven to deploy the server side part of your app. Or even better use the same application server that you are also using in production to minimize development/production differences. Once you do that you can also directly use GWT's CodeServer class without going through DevMode class. This will also remove the error log regarding sun.misc.GC.

There is also a discussion in https://groups.google.com/g/google-web-toolkit-contributors/c/iU9hckIab2o to gather feedback wether or not GWT should remove embedded Jetty support. It makes configuring a server more complex but you also don't run into a situation where everything seems to look right, but still it does not work, as in your case.

-- 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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/beefbaf2-c7f9-4399-acd6-392380d378a4n%40googlegroups.com.

Re: GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

The code server is ready at http://127.0.0.1:9876/

Code server started in 4.878 s ms

[ERROR] jreLeakPrevention.gcDaemonFail

java.lang.ClassNotFoundException: sun.misc.GC

This can be ignored. GWT's class JettyLauncher tries to fix a class loader memory leak within sun.misc.GC but this class does not exist in that package in Java 11. The exception is catched and logged as error, but code will continue.

java.lang.RuntimeException: Error scanning entry module-info.class from jar file:/C:/Users/jiny/gitTestUpgrade/aries/war/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)

at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)

at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)

at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM6

at org.objectweb.asm.ClassVisitor.visitModule(ClassVisitor.java:130)

at org.objectweb.asm.ClassReader.readModuleAttributes(ClassReader.java:724)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:544)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)

... 6 more

The embedded Jetty provided by GWT's DevMode class is too old to handle module-info.class files correctly during class file scanning. It basically requires newer ASM version.

The recommend approach for anything other than a small demo app is to not use the embedded Jetty provided by GWT DevMode. Instead use your own Jetty installation or a Jetty plugin for Gradle/Maven to deploy the server side part of your app. Or even better use the same application server that you are also using in production to minimize development/production differences. Once you do that you can also directly use GWT's CodeServer class without going through DevMode class. This will also remove the error log regarding sun.misc.GC.

There is also a discussion in https://groups.google.com/g/google-web-toolkit-contributors/c/iU9hckIab2o to gather feedback wether or not GWT should remove embedded Jetty support. It makes configuring a server more complex but you also don't run into a situation where everything seems to look right, but still it does not work, as in your case.

-- 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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/832317a3-a9aa-47eb-b8d6-07c55f358a01n%40googlegroups.com.

GWT 2.9, JDK 11 project upgrade issue: HTTP ERROR: 503: SERVICE_UNAVAILABLE

Thanks in advance for your time to help with this issue.

After much hard work, we finally resolved all of the errors related to the GWT compilation process for our application upgraded from GWT 2.5 to 2.9, from JDK 8 to JDK 11. 

However, when I run the application with "Run as -> GWT development mode with Jetty",

I got the following error and warning:

I searched online for the error highlighted below and the post said this error can be ignored. When we created ear file and deployed it to Weblogic server 14 and it gave 

HTTP ERROR: 503: SERVICE_UNAVAILABLE

It would be great if you can help shed some light on this issue.

Running CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir, C:\Users\jiny\gitTestUpgrade\aries\war, -logLevel, INFO, -style, OBFUSCATED, edu.vanderbilt.mc.aries.ARIES]

Super Dev Mode starting up

   workDir: C:\Users\jiny\AppData\Local\Temp\gwt-codeserver-15364372133406537389.tmp

   Loading Java files in edu.vanderbilt.mc.aries.ARIES.

   Ignored 9 units with compilation errors in first pass.

Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.

   Module setup completed in 4592 ms

The code server is ready at http://127.0.0.1:9876/

Code server started in 4.878 s ms

[ERROR] jreLeakPrevention.gcDaemonFail

java.lang.ClassNotFoundException: sun.misc.GC

at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)

at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)

at java.base/java.lang.Class.forName0(Native Method)

at java.base/java.lang.Class.forName(Class.java:315)

at com.google.gwt.dev.shell.jetty.JettyLauncher.jreLeakPrevention(JettyLauncher.java:899)

at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:722)

at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:636)

at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:898)

at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:705)

at com.google.gwt.dev.DevMode.main(DevMode.java:432)

Starting Jetty on port 8888

   [WARN] 

java.lang.NullPointerException

at java.base/java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)

at org.eclipse.jetty.annotations.ClassInheritanceHandler.addToInheritanceMap(ClassInheritanceHandler.java:72)

at org.eclipse.jetty.annotations.ClassInheritanceHandler.handle(ClassInheritanceHandler.java:58)

at org.eclipse.jetty.annotations.AnnotationParser$MyClassVisitor.visit(AnnotationParser.java:480)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:533)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)

at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)

at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)

at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

at java.base/java.lang.Thread.run(Thread.java:834)

   [WARN] Failed startup of context c.g.g.d.s.j.WebAppContextWithReload@491dfd8e{/,file:/C:/Users/jiny/gitTestUpgrade/aries/war/,STARTING}{C:\Users\jiny\gitTestUpgrade\aries\war}

java.lang.RuntimeException: Error scanning entry module-info.class from jar file:/C:/Users/jiny/gitTestUpgrade/aries/war/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:913)

at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)

at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)

at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.UnsupportedOperationException: This feature requires ASM6

at org.objectweb.asm.ClassVisitor.visitModule(ClassVisitor.java:130)

at org.objectweb.asm.ClassReader.readModuleAttributes(ClassReader.java:724)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:544)

at org.objectweb.asm.ClassReader.accept(ClassReader.java:400)

at org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:974)

at org.eclipse.jetty.annotations.AnnotationParser.parseJarEntry(AnnotationParser.java:956)

at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:909)

... 6 more

[ERROR] 503 - GET /ARIES.html (127.0.0.1) 298 bytes

   Request headers

      Host: 127.0.0.1:8888

      Connection: keep-alive

      sec-ch-ua: " Not;A Brand";v="99", "Microsoft Edge";v="91", "Chromium";v="91"

      sec-ch-ua-mobile: ?0

      Upgrade-Insecure-Requests: 1

      User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36 Edg/91.0.864.54

      Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9

      Sec-Fetch-Site: none

      Sec-Fetch-Mode: navigate

      Sec-Fetch-User: ?1

      Sec-Fetch-Dest: document

      Accept-Encoding: gzip, deflate, br

      Accept-Language: en-US,en;q=0.9

   Response headers

      Date: Fri, 25 Jun 2021 02:01:02 GMT

      Cache-Control: must-revalidate,no-cache,no-store

      Content-Type: text/html; charset=ISO-8859-1

      Content-Length: 298

[ERROR] 503 - GET /favicon.ico (127.0.0.1) 299 bytes

   Request headers

      Host: 127.0.0.1:8888

      Connection: keep-alive

      sec-ch-ua: " Not;A Brand";v="99", "Microsoft Edge";v="91", "Chromium";v="91"

      sec-ch-ua-mobile: ?0

      User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36 Edg/91.0.864.54

      Accept: image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8

      Sec-Fetch-Site: same-origin

      Sec-Fetch-Mode: no-cors

      Sec-Fetch-Dest: image

      Referer: http://127.0.0.1:8888/ARIES.html

      Accept-Encoding: gzip, deflate, br

      Accept-Language: en-US,en;q=0.9

   Response headers

      Date: Fri, 25 Jun 2021 02:01:02 GMT

      Cache-Control: must-revalidate,no-cache,no-store

      Content-Type: text/html; charset=ISO-8859-1

      Content-Length: 299

thanks,

Jenny

--
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/a8eb3155-7675-41b7-b2ed-6c528c252b52n%40googlegroups.com.

Re: GWT 2.9.0 TextField clear option in Chrome and IE

Actually my requirements are to add the clear button to the end on the textbox, I also tried adding textBox.getElement.setAttribute("type","search") but for some reason it is not working. Any help will be appreciated. 

On Tuesday, June 22, 2021 at 7:32:31 PM UTC+5:30 Jim Douglas wrote:

In our project CSS, we set display:none for the ::ms-clear pseudo element.

https://stackoverflow.com/questions/41900431/disable-ie-11-input-clear-x-button

On Tuesday, June 22, 2021 at 1:03:58 AM UTC-7 Hari wrote:

Hi All, 

Recently we have upgraded GWT from 2.1.0 to 2.9.0 with GXT 2.3.1a (Officially unsupported), Most major issues have been fixed, how ever we are having an issue with TextField<String> which is generating an HTML input element with type=text, this field in IE is showing with an cross icon to clear the text, but the same is not happening in chrome,

IE

___________________ 

|                              X |

-------------------------------

how to add clear icon with in the text input field in Chrome? Please let me know for more details required.  

Thanks

--
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/d2fa56e8-fedc-4194-af13-2613d86abb48n%40googlegroups.com.

Re: GWT 2.9.0 TextField clear option in Chrome and IE

In our project CSS, we set display:none for the ::ms-clear pseudo element.

https://stackoverflow.com/questions/41900431/disable-ie-11-input-clear-x-button

On Tuesday, June 22, 2021 at 1:03:58 AM UTC-7 Hari wrote:

Hi All, 

Recently we have upgraded GWT from 2.1.0 to 2.9.0 with GXT 2.3.1a (Officially unsupported), Most major issues have been fixed, how ever we are having an issue with TextField<String> which is generating an HTML input element with type=text, this field in IE is showing with an cross icon to clear the text, but the same is not happening in chrome,

IE

___________________ 

|                              X |

-------------------------------

how to add clear icon with in the text input field in Chrome? Please let me know for more details required.  

Thanks

--
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/410ca913-e3a2-476f-a343-b4a6d7574086n%40googlegroups.com.

GWT 2.9.0 TextField clear option in Chrome and IE

Hi All, 

Recently we have upgraded GWT from 2.1.0 to 2.9.0 with GXT 2.3.1a (Officially unsupported), Most major issues have been fixed, how ever we are having an issue with TextField<String> which is generating an HTML input element with type=text, this field in IE is showing with an cross icon to clear the text, but the same is not happening in chrome,

IE

___________________ 

|                              X |

-------------------------------

how to add clear icon with in the text input field in Chrome? Please let me know for more details required.  

Thanks

--
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/ad35fd5b-3187-43cf-be2f-b06f0c4fe6een%40googlegroups.com.

GWT on the Survey JVM Ecosystem Report 2021

Hi All,

great position of GWT on the survey JVM Ecosystem Report 2021: 

GWT ahead of Vaadin and all... Only Spring MVC and JSF in the front...

Go go GWT we'll go for number ONE! ☝️ 😎😜

https://twitter.com/lofidewanto/status/1405882423309701127?s=21

Have a nice weekend,
Lofi

--
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/9c59d7b0-7968-4c6f-9c99-066209bcd35fn%40googlegroups.com.

Re: Creating Java frontend project using domino-cli

Great video.  Probably would have been good to mention that you don't need to do that 1 minute compile at the start, that's only when you want to deploy.

On Friday, 18 June 2021 at 1:54:48 am UTC+10 aka...@gmail.com wrote:

Hi

I would like to share with you a recording I made to show how we can create a Java frontend project using domino-cli

https://youtu.be/TIe2d69S1T4

thanks

--
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/f5ae3656-2ffd-4c3e-94c7-090ed8632d7bn%40googlegroups.com.

Creating Java frontend project using domino-cli

Hi

I would like to share with you a recording I made to show how we can create a Java frontend project using domino-cli

https://youtu.be/TIe2d69S1T4

thanks

--
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/80fb5ab1-21b4-4836-9598-aa11c0ffc073n%40googlegroups.com.

The GWT Eclipse Plugin stopped working in Eclipse 2021-06

I just updated my Eclipse development environment from 2021-03 to 2021-06. The installed GWT Eclipse Plugin (which hasn't been updated since 2017) no longer shows up in the menu bar, and it logs a bunch of errors. Is anyone (Brandon?) still maintaining it?

http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html

  GWT Eclipse Plugin 3.0.0.201710131939 com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse Plugin

org.osgi.framework.BundleException: Could not resolve module: com.gwtplugins.gdt.eclipse.core [3649]

  Unresolved requirement: Require-Bundle: com.gwtplugins.gdt.eclipse.platform

    -> Bundle-SymbolicName: com.gwtplugins.gdt.eclipse.platform; bundle-version="3.0.0.201710131939"; singleton:="true"

       com.gwtplugins.gdt.eclipse.platform [3651]

         No resolution report for the bundle.  Bundle was not resolved because of a uses constraint violation.

  org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"] and jakarta.servlet-api [osgi.identity; type="osgi.bundle"; version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"] via two dependency chains.

Chain 1:

  com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]

    require: (osgi.wiring.bundle=javax.servlet)

     |

    provide: osgi.wiring.bundle: javax.servlet

  javax.servlet [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"]

Chain 2:

  com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]

    require: (osgi.wiring.bundle=org.eclipse.jetty.servlet)

     |

    provide: osgi.wiring.bundle; bundle-version:Version="10.0.5"; osgi.wiring.bundle="org.eclipse.jetty.servlet"

  org.eclipse.jetty.servlet [osgi.identity; type="osgi.bundle"; version:Version="10.0.5"; osgi.identity="org.eclipse.jetty.servlet"]

    import: (&(osgi.wiring.package=javax.servlet)(&(version>=4.0.0)(!(version>=5.0.0))))

     |

    export: osgi.wiring.package: javax.servlet

  jakarta.servlet-api [osgi.identity; type="osgi.bundle"; version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"]

at org.eclipse.osgi.container.Module.start(Module.java:463)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1849)

at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1842)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1747)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1669)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)

at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

--
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/da623814-ce28-4e1a-bee9-6e961f47f4b3n%40googlegroups.com.

Re: [ANN] Akasha: Typed Browser API

For INTL Number and Date format, there is an implementation here: https://github.com/pepstock-org/Charba/tree/master/src/org/pepstock/charba/client/intl

If you are not using that chart lib, it could be a starting point.

Il giorno martedì 15 giugno 2021 alle 00:54:56 UTC+2 peter.j...@gmail.com ha scritto:

On Tue, Jun 15, 2021 at 6:59 AM foal <sspir...@gmail.com> wrote:

Hi, do you have support for Intl API? 

Not as yet. It is a javascript specification rather than a browser interface specification which means there is no WebIDL to use to generate the API. This would mean I would need to write the WebIDL or manually construct the jsinterop types ... which looks easy enough ... but I have yet to get to it ;)

--

Cheers,

Peter Donald

--
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/83683660-af71-4b41-bf9b-e377131cdd66n%40googlegroups.com.

Re: [ANN] Akasha: Typed Browser API

On Tue, Jun 15, 2021 at 6:59 AM foal <sspiridonov@gmail.com> wrote:

Hi, do you have support for Intl API? 

Not as yet. It is a javascript specification rather than a browser interface specification which means there is no WebIDL to use to generate the API. This would mean I would need to write the WebIDL or manually construct the jsinterop types ... which looks easy enough ... but I have yet to get to it ;)

--

Cheers,

Peter Donald

--
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/CACiKNc7b4Bnc7hMb9W1zHnH5eOLqaQz-X_7yG%3DsHV0MnUrL8mw%40mail.gmail.com.

Re: [ANN] Akasha: Typed Browser API

Hi, do you have support for Intl API? 

S.

 

On Thursday, May 27, 2021 at 1:11:21 AM UTC+2 peter.j...@gmail.com wrote:

What is Akasha?

Akasha is a typed browser API layer that is always up to date with the latest web specifications. These API layers are intended to simplify writing web applications in languages other than pure-Javascript. Akasha currently provides:

• Closure-compiler externs so that the closure-compiler can perform type checking and advanced type-based optimizations.
• Jsinterop annotated java classes that can be used in GWT projects.
• Jsinterop annotated java classes that can be used in J2CL projects.

In the near future, it is expected that bindings for other languages and frameworks will be produced (particularly to support WASM based toolkits). Support will also be re-enabled to generate React4j element factories.

Getting Started

Getting started using the JsInterop annotated classes is relatively easy. The following sections give a basic overview of how to get started in a GWT or J2CL project.

GWT

First you add a dependency on the gwt library to your project. In a Maven-based project is as simple as adding the following dependency:

<dependency>    <groupId>org.realityforge.akasha</groupId>    <artifactId>akasha-gwt</artifactId>    <version>0.11</version>  </dependency>

In a GWT project it is necessary to add a reference to the Akasha library the GWT module in your .gwt.xml file. This is just a single inherit:

<module>    ...    <inherits name='akasha.Akasha'/>    ...  </module>

J2CL/Closure Compiler

First you add a dependency on the j2cl library to your project. In a Maven-based project is as simple as adding the following dependency:

<dependency>    <groupId>org.realityforge.akasha</groupId>    <artifactId>akasha-j2cl</artifactId>    <version>0.11</version>  </dependency>

The closure compiler is shipped with a set of externs that do not align 100% with the externs produced by the Akasha project. Thus it is necessary to pass the arguments -env CUSTOM when running the closure compiler. It is also necessary to add the closure externs shipped as part of the akasha-java artifact. These are included in the artifact under the names; akasha/Akasha.externs.js and akasha/akasha_patches.extern.js. The exact way that these build steps are specified will depend upon the underlying tool but a simple example using Bazel is available at https://github.com/react4j/react4j-todomvc/tree/raw_bazel_j2cl

Java Integration

The easiest way to access browser APIs is to access the static fields or call static methods on the classes that represent the globalThis object within the javascript environment. The "namespaces" within the browser are also exposed as java classes containing static methods and static fields.

For example the javascript:

window.addEventListener( "online", e => console.log( "The network is connected" ) )

Would be translated into Akasha java as:

WindowGlobal.addOnlineListener( e -> Console.log( "The network is connected" ) );

In this scenario, the WindowGlobal java class represents globalThis value in a browser window context and the Console class represents the console namespace. Some browser types can also be created using the new keyword and where this is possible in javascript it is possible in Akasha java. i.e. new WebSocket("wss://..." ) is valid in both javascript and Akasha java.

How does it work?

Akasha is kept with evolving browser standards by fetching WebIDL and processing the WebIDL to generate source code and other artifacts.

WebIDL is used by various specifications to communicate the interfaces that are expected to be implemented in web browsers. Many web browsers also use a WebIDL variant to generate code to implement the specification.

WebIDL published as part of the official specifications are not always perfect representations of the interfaces as implemented by the web browsers. Nor is there a central place that contains the complete WebIDL that a browser is expected to implement. The Akasha suite defines a pipeline for processing WebIDL schemas. The pipeline defines a series of stages. Each stage will either transform a schema, combine multiple schemas or perform an action for the schema. This capability allows the tool to process the WebIDL schemas fetched from the specifications and combine them into a consistent document.

The Akasha suite also includes tools to fetch data from other locations and combine the data with the WebIDL in processing stages. The most significant other data source is the documentation that is scraped from the MDN website and used to add basic documentation to the WebIDL elements. In the near future it is expected that the browser compatibility data will also be scraped so that browser compatibility data for WebIDL elements can be used in the processing pipeline to influence how artifacts are built. Other data from the web specifications could be combined to improve the outputs generated from the suite.

Akasha extends the WebIDL syntax to support additional data being added to the WebIDL. This includes syntax to explicitly declare events emitted by interfaces (i.e. there is a new member element that looks like event ProgressEvent load;). It also supports a Javadoc-like syntax for documenting the WebIDL elements.

The Akasha jsinterop action generates source code with a more java-esque feel than is present in elemental2. It also aims to offer affordances that make working with the browser API easier for java developers. A few differences from Elemental2 include:

• Javadocs are added for most fields, methods and types if the element is documented on MDN. This often includes references to the specification in which the element is defined.
• Constants in WebIDL are represented as constants in java. This typically results in smaller code size and may open up additional optimization opportunities.
• Fields, methods and parameters are annotated with @Nonnull or @Nullable if the type is a non-primitive, non-void type.
• Read-only attributes in WebIDL are implemented as methods rather than mutable fields or properties with setters.
• Dictionaries in WebIDL use a "builder" pattern to make construction of these types much easier.
• No parameterized types exist in the Akasha generated artifacts as WebIDL does not define such constructs. However there are a handful of hand-written jsinterop annotated java classes such as JsArray, JsMap, JsSet, JsWeakMap and JsWeakSet that make use of parameterized types to support normal java development practices.
• Event handlers and event listeners are typed according to the type of event expected to be delivered and have a void return type. This simplifies the use of lambdas and method references in java code.
• @JsOverlay methods are added for known events emitted by an interface. For example, it is possible to use code such as e.addBlurListener(this::processBlurEvent) rather than the more verbose e.addEventListener("blur", e -> processBlurEvent((FocusEvent) e)
• WebIDL enumerations are annotated with the @MagicConstant annotation when translated to java code. The Jetbrains/IntelliJ IDE suite will detect this annotation and allow auto-completion of enumeration values or report errors when incorrect values are supplied.
• Several other minor usability improvements, particularly with respect to union types.

One of the greatest advantages of Akasha is the ability to quickly generate API for new specifications. First you run a single command to register the spec url, extracting the WebIDL from the specification and extract the documentation from MDN. Then you run a second command to regenerate the java and library and closure externs.

How does this relate to WebTack?

WebTack was the former name of this project when the scope encompassed building a tool to fetch and process WebIDL files. That name still lives on with that part of the suite but the name is no longer used outside this project.

The project evolution

Akasha grew out of several experiments that helped shape the way the code was generated. Several web apps have been created to explore the feel of using the generated code and these may be interesting to investigate to get a feel of how the project evolved. This has included experiments with the Web Bluetooth API by creating a browser based Heart Rate Monitor, experiments with speech synthesis using the Web Speech API, experiments with WebRTC by creating a video chat application and several other experiments that are not open source.

The next major milestone was for integration of Akasha into a medium sized application with ~600K lines of GWT code that has been in development since 2011. This integration has successfully replaced our previous browser API layers and we are now focusing on fine tuning and optimizing the output.

Adopting Akasha has made it trivial to integrate with new Web APIs as they come out with minimal fuss compared to past approaches such as the handwritten DOM adapters, elemental or elemental2 libraries and we think Akasha is nearing a time where it is suitable for adoption in a broader context.

--

Cheers,

Peter Donald

--
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/c5744b82-1aa2-4cb0-904a-ccb9650bb293n%40googlegroups.com.

[ANN] Akasha: Typed Browser API 0.12 released

Akasha is a typed browser API layer that is always up to date with the latest web specifications.

Changes in this release:

* Add the `WebCodecs` spec with version `W3C Working Draft, 11 June 2021` to the set of specifications which the API is generated from.
* Update the `Geolocation API` spec to the `W3C Working Draft 10 June 2021` version. This improved typing and aligned with how browsers are implementing the underlying javascript objects.
* Update the `Gamepad` spec to the `W3C Working Draft 08 April 2021` version. This added event events for when gamepads are connected and disconnected. This version also supports XR mappings.
* Update the `Web Bluetooth` spec to the `Draft Community Group Report, 17 May 2021` version. This improved the typing of several attributes and exposed `manufacturerData` via the API.
* Update to the latest version of the `webgl` specifications. This primarily resulted in supporting `VideoFrame` as a `TexImageSource`.
* Upgrade to the latest version of the `Web Authentication: Level 2 Recommendation` or `webauthn` specification finalized on `8 April 2021`.
* Update several web specifications with various fixes, clarifications and API changes to more closely align with actual browser implementations. These specifications included: `whatwg_html`, `whatwg_dom`, `visual_viewport`, `screen_capture` and `cssom_view`.

To learn more about Akasha and get started:

    https://github.com/akasha/akasha

Thanks!

The Akasha Team

--
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/CACiKNc4X8jpU8-1613F7hRtktLTkSin730PG%3DqX-tjoAcz4YOw%40mail.gmail.com.

Re: Upgrade GWT from 2.7 to 2.9

I understand the advantages of java 8, but i'm working on an existing project in a company, and for now they don't want to update to java 8, they want to upgrade gwt .

So I have to convice them that there is no reason to upgrade from gwt 2.7 to 2.8, because our matter now is securities reasons in gwt not java !!

Le jeudi 10 juin 2021 à 04:20:34 UTC+1, Craig Mitchell a écrit :

Avoid it!?!  Why would you want to avoid it?  Pre java 8 sucks.  No Lambdas for a start.  Feel free to Google all the advantages of Java 8.

I say, reduce your tech debt, upgrade to the latest.  :-)

On Tuesday, 8 June 2021 at 9:03:59 pm UTC+10 HATIM SETTI wrote:

Hi,

thank you guys for your responses.

So there is no breaking changes from 2.7 to 2.9. the main reason that we want to upgrade is for securities reasons, so I suggest there is no need to upgrade to 2.9 ?!  not to mention that we will have to migrate to java 8 or latest version. so a lot of work is anticipated.

do you guys have other arguments that I can provide to avoid this whole migration ?

Thank you .

Le jeudi 3 juin 2021 à 19:19:58 UTC+1, David Nouls a écrit :

Hi,

Migration is nearly invisible but if you depend on 3rd party gwt libs then there is always risk that they are no longer supported.

I ran into some backward compatibility issue with generics support with GWT2.9. It compiled on 2.8 but fails with 2.9. I did not find the time to create a bug report and code sample to demonstrate. 

Groeten,

David

On 3 Jun 2021, 18:42 +0200, HATIM SETTI <h.s...@mundiapolis.ma>, wrote:

Hi team,

I'm working on an existing project with (gwt 2.7 , maven Java 6,spring..), and we want to upgrade to 2,8 or 2.9 atest version.

And I want to know the impact of that, will we need to change a lot of code, what the steps shoud I follow ?

Also what the gain of upgrading to the latest version ? there is any improvement in term of security ?

Thanks

--
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-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/232cba3f-f910-432f-bfba-382e8d9eab9dn%40googlegroups.com.

--
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/4abd3e26-fae4-401a-844c-28d5cd042585n%40googlegroups.com.

Re: Upgrade GWT from 2.7 to 2.9

Avoid it!?!  Why would you want to avoid it?  Pre java 8 sucks.  No Lambdas for a start.  Feel free to Google all the advantages of Java 8.

I say, reduce your tech debt, upgrade to the latest.  :-)

On Tuesday, 8 June 2021 at 9:03:59 pm UTC+10 HATIM SETTI wrote:

Hi,

thank you guys for your responses.

So there is no breaking changes from 2.7 to 2.9. the main reason that we want to upgrade is for securities reasons, so I suggest there is no need to upgrade to 2.9 ?!  not to mention that we will have to migrate to java 8 or latest version. so a lot of work is anticipated.

do you guys have other arguments that I can provide to avoid this whole migration ?

Thank you .

Le jeudi 3 juin 2021 à 19:19:58 UTC+1, David Nouls a écrit :

Hi,

Migration is nearly invisible but if you depend on 3rd party gwt libs then there is always risk that they are no longer supported.

I ran into some backward compatibility issue with generics support with GWT2.9. It compiled on 2.8 but fails with 2.9. I did not find the time to create a bug report and code sample to demonstrate. 

Groeten,

David

On 3 Jun 2021, 18:42 +0200, HATIM SETTI <h.s...@mundiapolis.ma>, wrote:

Hi team,

I'm working on an existing project with (gwt 2.7 , maven Java 6,spring..), and we want to upgrade to 2,8 or 2.9 atest version.

And I want to know the impact of that, will we need to change a lot of code, what the steps shoud I follow ?

Also what the gain of upgrading to the latest version ? there is any improvement in term of security ?

Thanks

--
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-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/232cba3f-f910-432f-bfba-382e8d9eab9dn%40googlegroups.com.

--
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/4c84c576-60e0-4673-a39b-bfaa96bf77efn%40googlegroups.com.

Re:

At this line in JdtCompiler, the warningThredshold field is part of a JDT class, so double check your dependencies, your probably have an incompatible JDT/ECJ dependency in your classpath.

On Monday, June 7, 2021 at 8:57:19 PM UTC+2 jiny...@gmail.com wrote:

Hello,

We have an application can not compile using GWT-2.9 with JDK 11 after upgraded from GWT 2.5 and JDK 8.

It would be great if you can help shed some light on this. Please see below for the error:

Compiling module edu.vanderbilt.mc.aries.ARIES
[ERROR] Unexpected internal compiler error
java.lang.NoSuchFieldError: warningThreshold
at com.google.gwt.dev.javac.JdtCompiler$1.<init>(JdtCompiler.java:634)
at com.google.gwt.dev.javac.JdtCompiler.getStandardCompilerOptions(JdtCompiler.java:632)
at com.google.gwt.dev.javac.JdtCompiler.getCompilerOptions(JdtCompiler.java:664)
at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:1015)
at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:322)
at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532)
at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464)
at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:210)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:190)
at com.google.gwt.dev.Precompile.precompile(Precompile.java:131)
at com.google.gwt.dev.Compiler.compile(Compiler.java:192)
at com.google.gwt.dev.Compiler.compile(Compiler.java:143)
at com.google.gwt.dev.Compiler.compile(Compiler.java:132)
at com.google.gwt.dev.Compiler$1.run(Compiler.java:110)
at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
at com.google.gwt.dev.Compiler.main(Compiler.java:113)

Your help is greatly appreiciated!

Jenny

--
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/454ccda4-88bb-4433-a1c5-68e3d8ade7d3n%40googlegroups.com.

Re: Upgrade GWT from 2.7 to 2.9

Hi,

thank you guys for your responses.

So there is no breaking changes from 2.7 to 2.9. the main reason that we want to upgrade is for securities reasons, so I suggest there is no need to upgrade to 2.9 ?!  not to mention that we will have to migrate to java 8 or latest version. so a lot of work is anticipated.

do you guys have other arguments that I can provide to avoid this whole migration ?

Thank you .

Le jeudi 3 juin 2021 à 19:19:58 UTC+1, David Nouls a écrit :

Hi,

Migration is nearly invisible but if you depend on 3rd party gwt libs then there is always risk that they are no longer supported.

I ran into some backward compatibility issue with generics support with GWT2.9. It compiled on 2.8 but fails with 2.9. I did not find the time to create a bug report and code sample to demonstrate. 

Groeten,

David

On 3 Jun 2021, 18:42 +0200, HATIM SETTI <h.s...@mundiapolis.ma>, wrote:

Hi team,

I'm working on an existing project with (gwt 2.7 , maven Java 6,spring..), and we want to upgrade to 2,8 or 2.9 atest version.

And I want to know the impact of that, will we need to change a lot of code, what the steps shoud I follow ?

Also what the gain of upgrading to the latest version ? there is any improvement in term of security ?

Thanks

--
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-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/232cba3f-f910-432f-bfba-382e8d9eab9dn%40googlegroups.com.

--
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/51f26ed3-7d25-4a8e-86d7-af8867b9b2fdn%40googlegroups.com.