Re: Seeking Advice on Legacy Application Migration Strategy

You might run into issues with such an old version of GXT when using a new GWT version - take a look at https://groups.google.com/g/google-web-toolkit/c/If897MPqvw0/m/bSWnmuz9BwAJ for a summary of how to update GXT 2.3.1a-gwt22. With GWT updated to 2.9.0 or beyond, you will be able to run on

Re: [ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9

e the old project I want to migrate uses the old version of > mojo gwt-maven plugin and that's where the module is. Could that also be > part of my issue? I specified the path like that because the with Tbroyer > version, the gwt xml module file is not in the same place. > > > Mnamo

Re: [ERROR] Unable to find 'com/google/common/collect/Collect.gwt.xml' : GWT 2.9

This looks like the same question as https://stackoverflow.com/questions/78202341/how-to-set-up-gwt-super-dev-mode-with-the-new-gwt-maven-plugin-with-a-web-applic, except with some updates - it sounds like you resolved the servlet classpath issue, can you flesh out this example a little more

Re: Problem with GWT?

There really isn't enough information here to guess what is happen - what else could have changed, like server version or configuration, any errors in your browser dev tools console? On Tuesday, March 26, 2024 at 2:57:37 PM UTC-5 germ...@gmail.com wrote: > When I access the web page, it

Re: InvocationTargetException with null cause?

I'm guessing this server has been running for a while, and possibly seen/caught other NPEs before this point? Hotspot has an optimization where it stops producing stack traces for null pointer exceptions (as well as a few other exceptions) after it is thrown a few times (usually "many", but

Re: Is moving away from RPC a good idea?

Point 1 is a potentially a serious concern for basically any tooling that decouples through interprocess communication, including grpc+protobuf (with ostensibly "perfect backwards/forwards compatibility") - in tooling that doesn't explicitly force compatibility as GWT-RPC does, you have to

Re: GWT Eclipse Plugin 4 Problem

There is a pending patch for this at https://github.com/gwt-plugins/gwt-eclipse-plugin/pull/475. You should be able to pull and build this to get working again on the very latest Eclipse versions - and if you do, leave a comment, a code review, etc, and we can get this merged more expediently.

Re: "Unload event listeners are deprecated" browser error

It looks like the purpose of registering the unload handler for any Window event is to avoid IE6-10 era memory leaks. From the notes on the MDN page, removing those other handlers will break the page when the bfcache is in use, but our use of the unload handler will opt GWT pages out. The

[gwt-contrib] Re: Infinite loop at compile time

Thanks for reporting - perhaps better for the bug tracker, and indeed we do this (or something like it) filed already, see https://github.com/gwtproject/gwt/issues/9840. Your email title says that this is a compile time infinite loop, but then the body suggests that it was a runtime error. If

Re: Running GWT 2.4.0 using JDK 17

ant build logs and GWT error related build > logs. I am not sure if this gonna work but just wanted to give a try and if > it works it will be helpful. Thank you very much! > > > Regards, > Anjana > > On Tuesday, January 16, 2024 at 6:17:08 PM UTC+5:30 Colin Alworth wrote

Re: Running GWT 2.4.0 using JDK 17

gt; > GWT.2.4.0 source code downloaded from - > https://github.com/gwtproject/gwt/releases/tag/2.4.0 > <https://github.com/gwtproject/gwt/releases/tag/2.4.0> > tools - https://github.com/gwtproject/tools/ > <https://github.com/gwtproject/tools/> > > Thanks in adv

Re: Announcing GWT 2.10.1 and 2.11 releases

to use it. Note that this is not compatible with running your jakarta-servlet app inside dev mode, but you will need to run your own server separately from dev mode. -- Colin Alworth co...@colinalworth.com On Sat, Jan 13, 2024, at 7:54 PM, Craig Mitchell wrote: > Awesome! Thank you

Re: Is moving away from RPC a good idea?

With 2.11 released, GWT-RPC (and RequestFactory) work on jakarta.servlet. There are no specific improvements that I'm aware of that require updating beyond the Servlet API 5.0, which is what gwt-servlet-jakarta uses. I _believe_ that RestyGWT relies on Generators, so might make an eventual

Announcing GWT 2.10.1 and 2.11 releases

I'm excited to announce the release of 2.10.1 and 2.11.0! This is our second release under the new groupId, be sure when you update to change away from "com.google.gwt", as it will not get more updates. If you use GWT-RPC and JPA/JDO annotations in your project, we strongly suggest updating at

Re: Can we uplift GWT2.4.0 to GWT 2.10 directly

Check out the recent thread https://groups.google.com/g/google-web-toolkit/c/3z8KB_5u7ig - most of the discussion applies here too. That is, without knowing what libraries you use, what application code you've written, what error messages you get from attempting either running the app directly

Re: Strategies for dealing with large number of languages?

Apologies, dumb typo right in the first line: It is _no longer_ singly threaded by the time permutations are being built. I hope the rest is more accurate, please feel free to call me out on other dumb mistakes :). On Wednesday, January 3, 2024 at 9:29:20 PM UTC-6 Colin Alworth wrote: > Fi

Re: Strategies for dealing with large number of languages?

First, there's no magic - the compiler is pretty memory/cpu intensive, but by the time permutations are being built, it is singly threaded. Unless you've got a ton of cache and bandwidth to ram, "not scaling linearly" makes a lot of sense no matter what your application is - you're probably

Re: Running GWT 2.4.0 using JDK 17

more volunteers (contact me off-list). On Wednesday, January 3, 2024 at 2:36:34 PM UTC-6 Jim Douglas wrote: > Apologies for the off-topic question, but is there an estimated timeframe > for GWT 2.11? > > On Wednesday, January 3, 2024 at 8:55:25 AM UTC-8 Colin Alworth wrote: > >&

Re: Running GWT 2.4.0 using JDK 17

(I wrote a longer reply, but Google Groups ate it and never posted it, so apologies for brevity here): Without more information, it is hard to give a specific answer - are you just hoping to update the Java version and make no changes to the application? It might be that nothing at all needs

Re: Seeking Guidance: GWT Version with Resolved XSS Vulnerabilities - Which One to Use?

I think what Frank is saying is that those linked issues all related to the GWTTestCase tooling, which is only used for unit tests, and no reasonably-configured application will be serving GWTTestCase contents to users (and will usually only be available locally for 10s of seconds, on a

Re: Migrating from 2.5.0 to 2.7.0

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

Re: Migration from 2.7.0 to 2.9.0

Can you share the complete build log? At a guess, there is some classpath mismatch, mixing parts of GWT 2.7 with 2.9 - the Core module is always included as an inherits for every module, even if that module is empty, so this suggests an earlier error that prevented that module from working, or

Re: How to debug the java code on the eclipse ide with the tbroyer gwt maven plugin ?

That's great news! Related, I had understood that this didn't work at all, but I discovered via https://bugs.chromium.org/p/chromium/issues/detail?id=327092 that there is an "experimental" feature in chrome that lets locals be displayed. [image: screenshot867.png] However even with this

Re: How to debug the java code on the eclipse ide with the tbroyer gwt maven plugin ?

The gwt-eclipse-plugin is maintained, but browsers removed the API that was previously used to let a Java debugger connect to a running GWT application. This API was used by a browser plugin that was shipped as part of GWT. Technically GWT still supports this, but I believe only IE11 (and

Re: [gwt-contrib] Re: Preparing for GWT 2.11 release

we now use are not compatible there. On Thursday, November 23, 2023 at 7:36:55 AM UTC-6 Juan Pablo Gardella wrote: > Hello, is gwt-2.11 artifacts available somewhere for testing against the > applications I am currently working on? > > On Tue, Nov 14, 2023, 11:37 PM Colin Alworth wrote: > >&

Re: Code fails to compile with GWT 2.10.0

Reviewing https://github.com/GwtMaterialDesign/gwt-material/releases, I see that 2.4.0 was the first version that was built against GWT 2.9 itself, and latest HEAD still appears to use GWT 2.9.0 according to the pom file. On the other hand, at

[gwt-contrib] Re: Preparing for GWT 2.11 release

with Java 11 and Chrome/Edge/Firefox. > Will the jars for testing be available in some Maven repo? > > Cheers, > Zbynek > > On Wednesday, November 15, 2023 at 3:37:38 AM UTC+1 Colin Alworth wrote: > >> It has taken longer than we had hoped, but I think we're just about read

[gwt-contrib] Re: Preparing for GWT 2.11 release

e help, I'm feeling to help. > Specially the jakarta stuff is important for us. > Do you find the time to have a look to the open PR? > > BR > Rocco > > Colin Alworth schrieb am Mittwoch, 17. Mai 2023 um 16:44:58 UTC+2: > >> There have been a few suggestions of making a r

Re: GWT New Project doesn't start because of Jetty problems.

Sorry, hit send too early - when using CodeServer, you should be sure to start your own tomcat - for whatever reason, that error message at localhost:8080 indicates that tomcat isn't running or isnt reachable at that port. On Monday, October 30, 2023 at 11:49:43 AM UTC-5 Colin Alworth wrote

Re: GWT New Project doesn't start because of Jetty problems.

ge: log.png] > > [image: log2.png] > > On Sunday, October 29, 2023 at 3:37:49 PM UTC-4 Colin Alworth wrote: > >> There are a few options I would suggest: >> * Upgrade to GWT 2.10 (especially since this is a new project). This is >> probably the simplest and best

Re: GWT New Project doesn't start because of Jetty problems.

There are a few options I would suggest: * Upgrade to GWT 2.10 (especially since this is a new project). This is probably the simplest and best option. The new version of Jetty used there will not have this issue with scanning module files. * Stop using DevMode as an application server - run

Re: GWT Designer

If memory serves, the GWT Designer tool was never part of GWT itself, but was a component that could be installed in Eclipse, allowing for WYSIWYG UI design (in part by running something like dev mode while you were editing?). Changes that the author of the project made were reflected in

Re: GWT: Deserialize objects sent/received via websocket

ed. Hence, it is not easy for me to identify which GWT library class >> is in use. >> >> Is there any way how to get this information, (i.e. I could provide the >> URL of the endpoint I am talking to). >> >> Best, >> André >> >> Colin Al

Re: GWT: Deserialize objects sent/received via websocket

While GWT offers websocket support, the only support is "now you can send messages on a websocket" - no serialization is offered, beyond what the browser itself provides (allowing sending a utf8 string, arraybuffers, blobs, typedarrays, or arrayviews). How are you verifying messages

Re: com.ait.toolkit.core.Core not found in Gwt-tour

I'm broadly aware that gwt-tour exists (though it hasnt had an update in 8 years), but I don't see any com.ait packages or references in it. On the other hand, I think com.ait.toolkit.core refers to https://github.com/dikalo/ahome-core/, which is a different thing entirely. It appears that

Re: [GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

Tiberiu, the fact that it works in Eclipse strongly suggests to me that the ant classpath is different from the eclipse project classpath. That different configuration will lead to different results. This error is typically indicative of some other error happening (typically classpath related)

Re: Partial super source? Possible?

I don't use String.format() a lot, even in the normal JVM, but based on the Javadoc it looks like we could add the format method, and delegate to a java.util.Formatter, but then leave that unimplemented by default. Then, downstream applications could more easily add that, without having to

Re: GWT compilation issue with jdk 17

There is community work underway to update GWT-RPC itself to use jakarta.servlet packages, and the same idea could be applied to gwtplatform. Unfortunately, the gwtplatform.com domain is still owned, so any fork could not take over the groupid, but

Re: DataPicker in GWT

It appears that this is specified as part of the DefaultCalendarView type, in the nested DateCell class's update(Date) method. I don't see an obvious way to override that, nor to replace the DatePicker.StandardCss type (package protected). Instead, you might implement CalendarView in your own

Re: GWT war file deployment issue on Tomcat 9

It looks as though the war file that was deployed was built after Super Dev Mode had been started, but before the production build had been performed, so the generated JS only works with a local development server. Try a clean build, without starting dev mode? If this still doesn't work, can

Re: GWT compilation error with JDK 11

e GWT >> Plugin installed in Eclipse. >> >> Version: 2020-06 (4.16.0) >> GWT Plugin version: 3.0 >> >> Your help is greatly appreciated! >> >> thanks, >> Jenny >> On Friday, June 16, 2023 at 12:33:18 PM UTC-5 Colin Alworth wrote: >>

Re: Devmode compilation

3) > > It works with -draftCompile. What we are potentially losing having code > compiled with -draftCompile? Is it safe to have it on production? > > On Friday, June 16, 2023 at 7:36:50 PM UTC+2 Colin Alworth wrote: > >> Super Dev Mode skips many optimizations, both to decrease c

Re: Devmode compilation

Super Dev Mode skips many optimizations, both to decrease compile times and also to make incremental compilations possible - it isn't possible to make SDM behave the exact same as a production compile. One way you can get close is to specify -draftCompile (how you specify it may vary based on

Re: GWT compilation error with JDK 11

GWT 2.9 should support running on Java 11, both running on JDK 11 and compiling Java 11 sources. Without other information, it sounds like there is a problem with your copy of gwt-dev.jar - the jar might be corrupt, or somehow not on your classpath? Can you verify that the jar is present and

[gwt-contrib] Preparing for GWT 2.11 release

There have been a few suggestions of making a release in the near future, and it seemed like it might be a good idea to summarize pending development, ask for help to land these, and see if anything else needs to be addressed before shipping. - There is a pending branch (not yet a PR for

Re: Entry point

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 poss

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

Re: Commitment regarding Jakarta

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

Re: HTTP Method Override

I think Thomas is on the right track - the tester ran the query with the method override headers indicating “PUT” instead of “POST”, and saw that the response came back “200 OK”, and assumed that the attack had worked. Instead what happened is that gwt-rpc couldn’t understand the request, and

Re: GWT 2.10.0 and TLD/JAR Scanner Error

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

Re: Building artifact without clutter

(Might be a better post for https://groups.google.com/g/google-web-toolkit-contributors) The maven artifacts require one more step to deploy, either to your maven local cache, or to an artifact server you can deploy to. Use the maven/push-gwtproject.sh script (see

Re: Privacy Violation with SSN

I haven't seen this come up before in a scan like this, thanks for sharing! This is due to the compiler, but rather than obfuscation, this is due to the compiler solving for a constant value rather than doing the math at runtime. This same constant appears in the GWT showcase as well, at

Re: page navigation

It is difficult to be sure what you are asking, but to navigate automatically to a new URL, you might just want Window.Location..assign(newUrl) or Window.Location.replace(newUrl), depending on exactly what behavior you want to have in your user's browser history. Alternatively if you are using

Re: Jakarta EE 9 support in GWT

The work on this topic is being discussed on that ticket and related pull requests. In short, if there is community support to implement and test this, it will be present in a future release. Please try the test builds already discussed there, and consider joining the discussion to help

Re: Question about setting GWT RPC timeout

se ignore them. > Thank you again > > Best regards > Dmitri > > > On Thu, Apr 6, 2023 at 9:49 PM Colin Alworth wrote: > >> I believe you're experiencing different timeouts in different cases. That >> is, the problem you're facing of a short timeout before you use yo

Re: Question about setting GWT RPC timeout

I believe you're experiencing different timeouts in different cases. That is, the problem you're facing of a short timeout before you use your RPC_TIMEOUT_MS is a server-side timeout (or potentially a proxy?), but after you set a client-side timeout, the client is observing that the server is

[gwt-contrib] Re: Compiling gwt on Mac ?

That patch is delayed since it turns out there are some tests that rely on specific behavior from the JVM - a few JPMS violations in legacy dev mode, and apparently Annotation.toString() changed slightly breaking a few other tests. I think it is just about ready, but each round of testing takes

Re: Eclpse GWT 3.0 plugin not available

Error scanning file GWT29_JDK11.class at org.eclipse.jetty.annotations.AnnotationParser.parseDir(AnnotationParser.java:708) This error should be fixed with GWT 2.10.0, or by disabling the annotation-based servlet configurations. A very similar issue is discussed at

[gwt-contrib] Re: New home for GWT Eclipse Plugin

ger with password > sharing between trustworthy community members. I appreciate the commitment > of Vertispan but there should be a backup plan in case something unexpected > happens. > > -- J. > > Colin Alworth schrieb am Samstag, 28. Januar 2023 um 03:45:13 UTC+1: > >>

[gwt-contrib] New home for GWT Eclipse Plugin

The GWT Eclipse Plugin has become unmaintained, and over the last several months several community members have stepped up to update it to run on recent Eclipse versions, and support the new GWT groupId. As part of that process, we've created a new marketplace entry, and while it is still

[gwt-contrib] Re: GWT 2 Roadmap as it applies to future deprecations

I'd welcome a separate discussion about a backward compatibility contract, but clearly we have to contrast the "technically Java 8 is supported" with "realistically, any project that uses standard up-to-date tools can't use Java 8 by the end of 2023". We support _end users_ to the extreme, as

Re: Security Vulnerabilities with GWT

Thanks for working on this, Rafat. I've deployed a build of this to https://repo.vertispan.com/gwt-snapshot/ with version 2.11.0-fix-9778-SNAPSHOT. This uses the new groupIds, org.gwtproject:gwt-servlet:2.11.0-fix-9778-SNAPSHOT. For example, see

Re: Security Vulnerabilities with GWT

This is discussed at https://github.com/gwtproject/gwt/issues/9778 and https://github.com/gwtproject/gwt/issues/9752: this is a false positive, but still needs to be corrected. The simplest fix is probably to just stop packaging up the "I am running an old version" marker file, since the Is

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

l finally force people to move on faster. They tend to complain that > we are using old technology (GWT) but at the same time they stick with Java > 8. > On 4 Aug 2022, 06:05 +0300, Colin Alworth , wrote: > > > > If there’s one thing that GWT has tried to be consistent about, it is > r

Re: GWT 2.10.0: gradle gwtSuperDev - java.lang.IllegalArgumentException: No selectors

, which should at least force jetty-io and htmlunit to be updated to the expected versions. On Tuesday, August 9, 2022 at 1:58:04 PM UTC-5 Colin Alworth wrote: > Your stack trace lines up except for the top frame - jetty-io > 9.4.4.v20210927 has a blank line for SelectorManager.j

Re: GWT 2.10.0: gradle gwtSuperDev - java.lang.IllegalArgumentException: No selectors

Your stack trace lines up except for the top frame - jetty-io 9.4.4.v20210927 has a blank line for SelectorManager.java:81, and the source for the file at that version doesn't contain the string "No selectors". On the other hand, jetty-io 9.2.14.v20151116 has this as a constructor (and line 81

[gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

If there’s one thing that GWT has tried to be consistent about, it is retaining support for technologies past their “best by” dates. This is a sore point from time to time, as it makes the tooling feel dated even right after a release, but it has some specific advantages with regards to

Re: http://localhost:8080/....../gemsInquiry/gemsInquiry.nocaches.js 404 (Not Found)

Can you share how you are starting GWT to debug this, and what the logs show? You should not need (or want) both gwt-maven-plugins in your pom.xml. On Thursday, July 28, 2022 at 8:02:44 AM UTC-5 parthib...@gmail.com wrote: > Hi Everyone, > I am using *Java 17* and *GWT 2.10.0* when trying

Re: Old system in GWT 1.4.61

There is no explicit "Chrome" support in GWT - Chrome started its life as another browser based around the WebKit engine. This is referred to in GWT as "safari", though WebKit started its life as part of the Konqueror browser, which pre-dates Safari's use of it (though arguably Safari

GWT 2.10.0 release

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

[gwt-contrib] Re: Testing for GWT 2.10.0 release

The last step of the release process is under way, Google's 2.10.0 release is underway, we're just waiting for the release to be performed and synchronized to Maven Central. When that has finished we can formally announce the release. I've created an issue for next steps to finish our

[gwt-contrib] Testing for GWT 2.10.0 release

Hello all, All of the preliminary testing that I'm aware of for the upcoming release is complete, leaving us with a decent level of confidence in the changes. We have a document that outlines the release plan (with a link to the standard release steps and the testing process) that has

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

2022 à 21:34:23 UTC+2, juan_pablo_gardella a écrit : >> >>> Tried with Maven 3.8.5 and still fails with same issue. Reported at >>> https://github.com/tbroyer/gwt-maven-plugin/issues/152 >>> >>> On Sun, Apr 24, 2022 at 3:59 PM Colin Alworth wrote: >

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

I've pushed a new build with version 2.10.0-new-groupid-3 that has several @SuppressWarnings("deprecation")s added, and hopefully will solve the WARN logging issue. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

ethod > create(ObservableMutableDocument) in the type > DefaultDocumentEventRouter is not applicable for the arguments > (ObservableMutableDocument) > [ERROR] Line 963: The method > createGadgetStatesDoc(DocumentEventRouter, > ObservablePrimitiveSupplement.Listener) in the

[gwt-contrib] Re: License for gwt-site content

rit and did require a CLA? > > --J. > > Colin Alworth schrieb am Donnerstag, 21. April 2022 um 17:34:49 UTC+2: > >> See the question raised at >> https://github.com/gwtproject/gwt-site/issues/328. >> >> While gwtproject explicitly licenses all "software a

[gwt-contrib] Preliminary testing for GWT 2.10 release

TL;DR: If you have the capability to do so, now would be an excellent time to help us test GWT in anticipation of a release, especially around the groupId change we're going to make. -- We think that we're one merge away from being ready for a GWT 2.10 release, so I'm starting the release

[gwt-contrib] License for gwt-site content

See the question raised at https://github.com/gwtproject/gwt-site/issues/328. While gwtproject explicitly licenses all "software and sample code" as under the Apache License 2.0, it appears that we don't have a license specified for the contents of the gwtproject website

Re: URGENT: GWT build crash with out of memory

Split points are amazingly expensive to compute (in both CPU and memory) - I would definitely remove all split points currently under 10KB, and strongly consider removing all under 100KB, at least for an application of that size. Odds are excellent that your 4043KB file is your "leftovers"

[gwt-contrib] gwtproject.org migration, https support

We've successfully migrated the gwtproject.org website to a new domain name server and new hosting, at Google's request. There are a few small differences from the old hosting: - HTTPS is now supported and enabled, though not yet mandatory, to allow a period of migration, and making

Re: [gwt-contrib] Re: Goodbye IE 8–9 

the same. >> >> -- J. >> >> ManfredTremmel schrieb am Montag, 4. Oktober 2021 um 11:07:11 UTC+2: >> >>> Am Donnerstag, 30. September 2021, 18:49:56 CEST schrieb Colin Alworth: >>> >>> > So, is there any objection at this time to dropping what r

Re: GWT 2.9 compatiblity with GXT 2.3.1a

The short answer is yes, you need to do this for each such bug you find, and if you have a commercial license, you need to do it yourself - the only way to distribute fixes for things like this is under GPLv2, which may not be something you want in your project as a dependency. If this is a

Re: [gwt-contrib] Re: GWT 2.10 release?

I'm looking for reviewers and help for the above issues so I can finalize them and begin testing. There are a few dependency chains here - I have IE8/9/10 removal just about complete, but before that can merge we need the apichecker updated, and after that merges, we can remove the poorly

Re: GWT 2.9 compatiblity with GXT 2.3.1a

The updated JDT probably caused this (so that gwt 2.8.2 can support Java 8 language features) - at a guess you'll need to cast the result of m.get(prop) on that line to Object so that StringBuilder.append correctly uses the Object overload. On Wednesday, October 13, 2021 at 3:41:52 PM UTC-5 RT

Re: [gwt-contrib] Re: Goodbye IE 8–9 

Note that it appears I'm mistaken, Runtime.java polyfilled Date.now() (though code in JsDate and others still believed that this method might not exist), so GWT 2.8.2 and 2.9.0 likely function properly in IE8. On Thursday, September 30, 2021 at 11:49:56 AM UTC-5 Colin Alworth wrote: > I

[gwt-contrib] GWT 2.10 release?

We've got a few changes that have been brewing or waiting to be made available, and it sounds like it is about time to collectively push to make these things happen. Given the nature of some of these, I am suggesting that they not be folded into a bugfix release, but instead that the next

Re: [gwt-contrib] Re: Goodbye IE 8–9 

I've just filed https://github.com/gwtproject/gwt/issues/9739, where a workaround exists in java.util.Date that nearly doubles the time it takes to parse date strings and build date objects. This workaround exists for IE8 and IE9, as all more recent browsers implement the same behavior as we

[gwt-contrib] Re: Documentation of compiler optimisations?

GWT itself hasn't changed substantially in many years - improvements have mostly been language features, adding support for incremental compilation, the jsinterop system, etc, so for the most part the optimizations haven't changed. That said, the best way is almost certainly to take a look at

Re: [gwt-contrib] Thurs July 16 2020 GWT community call

9saW5AdmVydGlzcGFuLmNvbQ=colin%40vertispan.com -- Colin Alworth co...@colinalworth.com On Tue, Jul 21, 2020, at 8:24 AM, Michael Conrad wrote: > How did it go? > > > On 7/15/20 5:02 PM, Colin Alworth wrote: >> We have a shorter itinerary this week - I'll record a short

[gwt-contrib] Thurs July 16 2020 GWT community call

We have a shorter itinerary this week - I'll record a short piece on j2cl-maven-plugin and how to start a project with it, try using pieces from the ecosystem. Dmitrii, Ahmad and I will continue our brainstorming about efficiently producing both optimized output and minimizing the work the

Re: Problem decoding complex AutoBean

I'm not seeing any issue with that code and sample JSON. Here's a quick entrypoint that I made: @Override public void onModuleLoad() { IWebchatThemeConfigurationBean bean = deserializeFromJson("{\n" + "\"themeId\": 1,\n" + "\"name\":

Re: GWT Server and debug

Yes, remove -nosuperDevMode. On Tuesday, July 7, 2020 at 5:02:19 AM UTC-5, Jasper Suijker wrote: > > Hi, > > We are running with 2.8.2 and want to migrate to 2.9.0 later on. > this is my current gwt server start with arguments: > Main class: > com.google.gwt.dev.DevMode > arguments: >

[gwt-contrib] Re: Thurs July 2 2020 GWT community call

Meeting link is at https://meet.google.com/jbs-wier-ywp - we will start recording in about an hour, and will only publish the three talks listed below. On Wednesday, July 1, 2020 at 12:58:15 PM UTC-5, Colin Alworth wrote: > > We're going to try recording tomorrow, just for the sp

[gwt-contrib] Thurs July 2 2020 GWT community call

We're going to try recording tomorrow, just for the specific 'sessions' that are planned, so the video should be available afterward, I'll link in a follow up post when they are ready. Three planned topics to record: * Ahmad Bawaneh presenting domino-history, a simple routing tool to

Re: [gwt-contrib] Re: Required JDK version to build GWT?

d, landed. * Update Javadoc to support >8 only, update build to skip any doc tasks when on Java 8 On Wed, Jul 1, 2020, at 11:34 AM, Thomas Broyer wrote: > > > On Wednesday, July 1, 2020 at 3:32:34 AM UTC+2, Colin Alworth wrote: >> Thanks Goktug for clarifying - I am personall

Re: [gwt-contrib] Re: Required JDK version to build GWT?

> In the long run, as JDK9+ tests grow, supersourcing might become >>> unsustainable, but the impact on the CI server et al. is non-negligible. We >>> could still possibly, at least temporarily, build only with JDK8, and only >>> run the JDK9+ tests once in a whil

Re: GWT SingleUploader gets stuck

It looks like this isn't part of GWT itself, but an external library. Here's a stackoverflow post i found from a few years ago that seems to address your issue: https://stackoverflow.com/questions/31424639/gwt-error-when-uploading-file-with-singleuploader It looks like the project might live

Re: [gwt-contrib] Required JDK version to build GWT?

impossible, just perhaps messy - and unwinding the "java8" flag (which really seems to mean "newer than java7") is less fun than I'd like. -- Colin Alworth co...@colinalworth.com On Mon, Jun 29, 2020, at 9:21 PM, 'Goktug Gokdogan' via GWT Contributors wrote: > wrt running tests: &g

[gwt-contrib] Required JDK version to build GWT?

As of somewhere in the time leading up to the GWT 2.9.0 release, it is no longer possible to build GWT with Java7, and similarly the decision was made to no longer officially support running on Java7 (jsinterop-annotations use of "TYPE_USE", newer jetty version too I believe). There is still

Re: Security Vulnerabilities with GWT

The gwt-servlet issue is only on c++ versions of protobuf, so we believe there is no exploit here at all. The other issues are all specific to gwt-dev, and neither gwt-dev.jar nor gwt-user.jar should ever be deployed as part of a running server application, so none of those should be

  1   2   3   4   5   >