Sunday, May 28, 2023

Re: Article Planning Spring Boot and GWT Boot with Domino + Nalu

I actually created this article…


It's time that Java developers don't need to hide their capabilities behind JavaScript 😅

Lofi 

Am 27.05.2023 um 20:32 schrieb Alex Karg <alexkarg7@gmail.com>:

Hi Lofi, +1, this article would certainly be a great read. Did you actually manage to create it yet? Thanks, Alex

On Sunday, December 18, 2022 at 1:04:48 PM UTC+1 lofid...@gmail.com wrote:
Hi All,

I'm looking forward for Xmas holidays... Preparing an article for GWT / J2CL:

Spring Boot and GWT Boot with DominoKit - Introduction - I would take the "StockWatcher" example and build a Domino UI and Nalu web app.

Any other wishes? ☺️

Another question, I see some questions about moving from old GWT to a newer version. Mostly they still use Eclipse based development and maybe Ant?

Is it worth it to create a "recipe" in OpenRewrite to be able to move all the old GWT webapps automatically to the newer structure with TBroyer Maven? It's a pity that people stuck in the older structure.

Thanks,
Lofi

Debugging in Chrome is already very good, and we are actually independent of the IDE with the Maven plugin...

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/pr_jDlWpmDs/unsubscribe.
To unsubscribe from this group and all its topics, 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/c3f8cac0-ee38-4ab7-8109-d6cf69f5c9a4n%40googlegroups.com.

Saturday, May 27, 2023

Re: Article Planning Spring Boot and GWT Boot with Domino + Nalu

Hi Lofi, +1, this article would certainly be a great read. Did you actually manage to create it yet? Thanks, Alex

On Sunday, December 18, 2022 at 1:04:48 PM UTC+1 lofid...@gmail.com wrote:
Hi All,

I'm looking forward for Xmas holidays... Preparing an article for GWT / J2CL:

Spring Boot and GWT Boot with DominoKit - Introduction - I would take the "StockWatcher" example and build a Domino UI and Nalu web app.

Any other wishes? ☺️

Another question, I see some questions about moving from old GWT to a newer version. Mostly they still use Eclipse based development and maybe Ant?

Is it worth it to create a "recipe" in OpenRewrite to be able to move all the old GWT webapps automatically to the newer structure with TBroyer Maven? It's a pity that people stuck in the older structure.

Thanks,
Lofi

Debugging in Chrome is already very good, and we are actually independent of the IDE with the Maven plugin...

--
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/c3f8cac0-ee38-4ab7-8109-d6cf69f5c9a4n%40googlegroups.com.

Wednesday, May 17, 2023

Re: Entry point

The entrypoint is supposed to function as the start of the application - how do you "enter" into it. You likely don't encounter the same entrypoint more than once as the app is being used, and any/all entrypoints will run right at page load. Technically each of what you describe is probably possible, but it seems very likely that you wouldn't want to use an entrypoint to manage a dialog that is opened by clicking a button.

Typically, the entrypoint is used like a java public static void main method - just one, only do enough in it to start the application.

On Sunday, May 14, 2023 at 11:44:47 PM UTC-5 ronjos...@gmail.com wrote:
Thank you Colin for responding , 

Can we use the entry point for some specific page or widget in the application?
e.g. There is a dialog in the application on which if clicked on edit button , we see another dialog on which there is a button to add files. 
Can we use the entry point to drag and drop files over the area of that add file button ?

Regards
Ronit

On Monday, 15 May 2023 at 04:40:28 UTC+5:30 Colin Alworth wrote:
While it is technically possible to have more than one EntryPoint declared in your .gwt.xml files(s), order might be hard to control precisely. I believe the order is deterministic, but not strictly defined by the compiler (likely the order in which entry-point> tags are encountered when parsing .gwt.xml files, but since they are permitted to have cyclical dependencies, this is not always obvious).

With that said, this can be a good way to compile multiple independent applications into a single output JS (so that they avoid sending the same  classes to the browser multiple times. I've seen this done with a conditional at the top of each entrypoint, to that way one or more entrypoint can run at page load automatically, and each enhance the part of the page that matters specifically to them. Ideally in this case, order of execution will not matter, so the above concern won't apply.

On Sunday, May 14, 2023 at 5:57:20 PM UTC-5 ronjos...@gmail.com wrote:
Hello Team,

I am new to GWT and working on an existing system.

My application has already got an entry point. Can I have one more implementation of the Entrypoint ?

Thanks in advance 
Ronit

--
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/f17f59a2-1090-4c8d-bf9c-663fe72dfe87n%40googlegroups.com.

Tuesday, May 16, 2023

Re: GWT for a Java to WASM compiler

I think the advantages come from transpiling languages other than JS to WASM (in their examples, Kotlin and Dart).  Eg: An integer in Java, will still be in integer in WASM, while when you ask GWT for an integer, it has to do a bunch of magic, as JS doesn't have integers.

On Sunday, 14 May 2023 at 9:50:58 pm UTC+10 lofid...@gmail.com wrote:
Thanks for the info. A very good explanation in that video.

But still don't understand why would this solution with WASM GC 2x faster than the "pure transpiling" solution? The latter is completely in JS and uses the GC from JS as it is.

Does this means using JS with WASM will be 2x faster than the pure JS??? 🤣

Thanks 
Lofi

Craig Mitchell schrieb am Freitag, 12. Mai 2023 um 12:27:43 UTC+2:
At Google I/O 2023, they showed that WASM (Web Assembly) is finally getting garbage collection (as well as shared memory).


They showed that JetBrains was experimenting with Kotlin compiling to WASM.

There wasn't any mention of anyone doing Java compilation to WASM.

I wonder how hard it would be to modify GWT to compile to WASM.  Possible?  Thoughts?

--
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/edaac5a4-7bdd-42d0-a6af-0909da7d0573n%40googlegroups.com.

Sunday, May 14, 2023

Re: Entry point

Thank you Colin for responding , 

Can we use the entry point for some specific page or widget in the application?
e.g. There is a dialog in the application on which if clicked on edit button , we see another dialog on which there is a button to add files. 
Can we use the entry point to drag and drop files over the area of that add file button ?

Regards
Ronit

On Monday, 15 May 2023 at 04:40:28 UTC+5:30 Colin Alworth wrote:
While it is technically possible to have more than one EntryPoint declared in your .gwt.xml files(s), order might be hard to control precisely. I believe the order is deterministic, but not strictly defined by the compiler (likely the order in which entry-point> tags are encountered when parsing .gwt.xml files, but since they are permitted to have cyclical dependencies, this is not always obvious).

With that said, this can be a good way to compile multiple independent applications into a single output JS (so that they avoid sending the same  classes to the browser multiple times. I've seen this done with a conditional at the top of each entrypoint, to that way one or more entrypoint can run at page load automatically, and each enhance the part of the page that matters specifically to them. Ideally in this case, order of execution will not matter, so the above concern won't apply.

On Sunday, May 14, 2023 at 5:57:20 PM UTC-5 ronjos...@gmail.com wrote:
Hello Team,

I am new to GWT and working on an existing system.

My application has already got an entry point. Can I have one more implementation of the Entrypoint ?

Thanks in advance 
Ronit

--
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/6302e782-6cc6-4db2-ab16-b69e9531c709n%40googlegroups.com.

Re: Entry point

While it is technically possible to have more than one EntryPoint declared in your .gwt.xml files(s), order might be hard to control precisely. I believe the order is deterministic, but not strictly defined by the compiler (likely the order in which entry-point> tags are encountered when parsing .gwt.xml files, but since they are permitted to have cyclical dependencies, this is not always obvious).

With that said, this can be a good way to compile multiple independent applications into a single output JS (so that they avoid sending the same  classes to the browser multiple times. I've seen this done with a conditional at the top of each entrypoint, to that way one or more entrypoint can run at page load automatically, and each enhance the part of the page that matters specifically to them. Ideally in this case, order of execution will not matter, so the above concern won't apply.

On Sunday, May 14, 2023 at 5:57:20 PM UTC-5 ronjos...@gmail.com wrote:
Hello Team,

I am new to GWT and working on an existing system.

My application has already got an entry point. Can I have one more implementation of the Entrypoint ?

Thanks in advance 
Ronit

--
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/3399c7a4-4221-4f91-a921-a88ede7dd5a3n%40googlegroups.com.

Entry point

Hello Team,

I am new to GWT and working on an existing system.

My application has already got an entry point. Can I have one more implementation of the Entrypoint ?

Thanks in advance 
Ronit

--
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/e16dde65-00bd-49f0-b128-3a252fa2107cn%40googlegroups.com.

Friday, May 12, 2023

Re: GWT for a Java to WASM compiler

Awesome!  Looks like J2CL is on it!  🎉

From memory, TeaVM has had WASM in an undocumented  and experimental status for a few years now.  I won't be holding my breath for that one.  🙂

On Saturday, 13 May 2023 at 2:30:51 am UTC+10 Thomas Broyer wrote:
Also, TeaVM does Java → WebAssembly (WASM or WASI)
No idea if it already leverages WASM-GC or it's in their roadmap

On Friday, May 12, 2023 at 12:59:17 PM UTC+2 gordan...@steatoda.com wrote:
On 12. 05. 2023. 12:27, Craig Mitchell wrote:
>
> There wasn't any mention of anyone doing Java compilation to WASM.
>
> I wonder how hard it would be to modify GWT to compile to WASM.  Possible?  Thoughts?

There is a Wasm compilation target in J2CL, but I haven't ever tried it myself:

https://github.com/google/j2cl
https://github.com/google/j2cl/issues/88
https://github.com/google/j2cl/issues/93 -> according to this one, they are working on their WASM support currently ("Now")

-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/40619553-9a04-4e15-a903-57264bd1824dn%40googlegroups.com.

Thursday, May 4, 2023

Re: Commitment regarding Jakarta

Thanks Colin, I'll take a closer look at those links.

Have a nice day!

On Wednesday, May 3, 2023 at 9:25:03 a.m. UTC-4 Colin Alworth wrote:
Several volunteer community members are indeed committed to this.

There was another recent discussion on this mailing list (just four topics down) that you can see at https://groups.google.com/g/google-web-toolkit/c/vBSKMgdZz1w - I directed the user to the discussion on our issue tracker at https://github.com/gwtproject/gwt/issues/9727 - you might also be interested in the side discussion happening in a pull request at https://github.com/niloc132/gwt/pull/3 on specfics of how to achieve this painlessly.

Also as discussed in 9727, there is an early prototype deployed at https://repo.vertispan.com/gwt-snapshot/ with version 2.11.0-jakarta-SNAPSHOT that you are free to test.

If you or your company are interested in contributing, those are good places to offer your time or to otherwise assist the developers who are working on this. As an open source project with no real funding behind it, this will proceed at the pace of the community members who are able to engage and contribute.

On Wednesday, May 3, 2023 at 8:17:49 AM UTC-5 aikic...@gmail.com wrote:
Hello,

I would like to know if there is any kind of commitment from the GWT project to move to Jakarta in a nearby future. We have over 50 apps, some larger than others, built with GWT, so this is very important to us. Moving away from GWT would be a huge amount of work.

Thanks in advance,

Christian

--
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/3db83b5f-f788-4f9a-a3cf-e8dbd4b24573n%40googlegroups.com.

Monday, May 1, 2023

Re: GWT 2.10.0 and TLD/JAR Scanner Error

That seemed the be the issue. Gwt-dev was already set to a provided scope in Maven but there was an oversight in its dependencies. Htlmunit and apache-jsf wee being included on the classpath due to overriding the version and not setting the scope. Made sure everything under gwt-dev isn't on the classpath and it seems to be deploying normally with a few minor errors related to server configuration that can be fixed. Thank you very much!
On Sunday, April 30, 2023 at 2:21:50 PM UTC-4 Colin Alworth wrote:
I think a little more detail could help us to identify the problem, but to start with, gwt-dev should never be on your server classpath - and neither should its dependencies. If you have gwt-dev.jar or GWT's preferred apache-jsp.jar on your server classpath, you should remove that (either build your client separately from your server code, or exclude those dependencies from being provided at runtime by maven). Given that you are using WebLogic rather than Tomcat already, I'm guessing that this is the source of your problem.
On Friday, April 28, 2023 at 3:45:27 PM UTC-5 Aynesh Patel wrote:
Hello,

I have a GWT 2.10.0 project compiled in Java 11, built with Maven 3.8.4 through the GWT-maven-plugin, and deployed to a WebLogic 14c server. Recently I have seen errors related to the Tomcat JAR scanner and the embedded server utilized in development mode. The application was working but after the upgrade to version 2.10.0, errors fill the server out log in WebLogic that the Tomcat StandardJarScanner failed to scan JAR files from the classloader hierarchy along with a silent failure of the application itself. After ensuring GWT was starting in Production Mode, I added the following elements to the configuration section of the plugin to ensure the server would not start up:

<noServer>true</noServer>
<compilerArgs>
    <arg>-noincremental</arg>
</compilerArgs>

After recompiling with these changes the application was able to function normally once again but the errors regarding the JAR scanner being unable to scan from the classloader hierarchy remained. The JARs it attempted to scan were ones that are not part of the application nor in any of the dependency trees of the dependencies of the gwt-maven-plugin.

I want to disable that JAR scanning and the errors it produces when the application is started. I attempted to do so by adding a context.xml to the webapp/META-INF to the scanning with configuration to limit the scanner but it did not seem to have an effect. Here are logs for the errors happening in the out file for the WL server the application is deployed to:

Failed to scan <JarFile> from classloader hierarchy
Java.io.IOException: java.lang.reflect.InvocationTargetException
at org.apache.tomcat.util.compat.Jre9Compat.jarFileNewInstance(Jre9Compat.java:209)
at org.apache.tomcat.util.scan.JarFileUrlJar.<init>(JarFileUrlJar.java:65)
at org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49)
at org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:387)
at org.apache.tomcat.util.scan.StandardJarScanner.processURLs(StandardJarScanner.java:322)
at org.apache.tomcat.util.scan.StandardJarScanner.doScanClassPath(StandardJarScanner.java:284)
at org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:235)
at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104)
at org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1428)
...


Additionally, in the server log file there is this outputted on startup:
<warning: No org.apache.tomcat.JarScanner set in ServletContext. Falling back to default JarScanner implementation.>

This link (https://stackoverflow.com/questions/66689374/spring-boot-with-jetty-disable-o-a-tomcat-util-scan-standardjarscanner) mentioned that the org.apache.tomcat.util.scan.StandardJarScanner can originate from apache-jsp JARs which gwt-dev 2.10.0 has a dependency. I confirmed this in my IDE and maven repository but I have been unable to prevent the scanning of the classpath hierarchy for TLDs. Is there a way to disable this scanning of TLDs and JAR files from the classloader hierarchy?

Help is very much appreciated!

Thank you,
Aynesh Patel

--
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/d8bb75ff-3317-4824-94f6-394620a75ffbn%40googlegroups.com.