Hello All,
Anyone can please help us...??
On Wednesday, March 25, 2026 at 12:13:19 PM UTC+5:30 Arpan Ameta wrote:
Hi Craig,
Thanks for pointing that out.
Yes, in the screenshot I shared, there is indeed an error related to MonitorServiceInterfaceProxyGenerator. However, this is a custom generator used across multiple modules in our project, and those modules are compiling and working fine even after the upgrade.
That’s why I’m a bit unsure if this generator is the root cause here, or if it’s just a side effect of something failing earlier in the compilation chain.
Also, the failure still surfaces specifically at:
AwbCustomer.AwbCustomerUiBinderwhich makes it look like a UiBinder deferred binding issue at first glance.
That said, I agree with your point — if the generator fails, it could potentially break the binding process. I’ll try isolating this further by:
- Checking if this module has any differences in how the generator is used
- Verifying if any recent changes or stricter rules in GWT 2.12.0 / JDK 17 are affecting it
- Temporarily disabling or bypassing the generator (if possible) to see if the error persists
I’ll update once I have more findings.
Thanks again for your help!
On Wednesday, March 25, 2026 at 4:33:36 AM UTC+5:30 Craig Mitchell wrote:
Is your screenshot saying there is an error with the MonitorServiceInterfaceProxyGenerator? I've no clue what that is, but that error could be causing the error with the AwbCustomer.
On Tuesday, 24 March 2026 at 10:56:33 pm UTC+11 Arpan Ameta wrote:
Hi Craig,
Thanks for your response.
Yes, the error occurs during compilation (GWT Code Server / compile), but interestingly I do not see the “Unable to find resource” error for the AwbCustomer.ui.xml file.
The .ui.xml file is present in the correct package and follows the same naming convention as other working modules. That’s why this is a bit confusing — if it were a missing or misplaced file, I would expect that specific error to show up.
In this case, the compilation fails directly with the deferred binding error:
Failed to resolve 'AwbCustomer.AwbCustomerUiBinder' via deferred bindingAlso worth noting:
- Other UiBinder classes in different modules are compiling fine
- This issue started only after upgrading to GWT 2.12.0 and JDK 17
- The structure and setup of this module is consistent with others that are working
Because of this, I’m wondering if this could be related to stricter checks in the newer GWT version or something subtle being missed in this particular class/module.
Please let me know if there’s anything specific you’d recommend checking beyond the usual .ui.xml placement — happy to dig deeper.
Thanks again for your help!
On Tuesday, March 24, 2026 at 2:53:06 PM UTC+5:30 Craig Mitchell wrote:
I assume you get this error when running, and the GWT Code Server fails to compile that class.
If you've misspelt or misplaced the ui.xml file, you should also get an error like:
[ERROR] Unable to find resource: blah/blah/.../AwbCustomer.ui.xml
Do you see that error?On Tuesday, 24 March 2026 at 5:58:33 pm UTC+11 Arpan Ameta wrote:
Hi Team,
I’m currently facing an issue after upgrading our project to GWT 2.12.0 and JDK 17, and I’d really appreciate any guidance or suggestions from the community.
While most of our modules are compiling and working fine post-upgrade, one specific module is failing during GWT compilation with the following error:
[ERROR] Failed to resolve 'com.shipco.air.modules.awb.client.airimport.view.awbpopup.AwbCustomer.AwbCustomerUiBinder' via deferred bindingFrom the logs, it appears to be a UiBinder-related issue during deferred binding. The same pattern and structure are used in other modules, and they are working without any problems.
A few points to highlight:
- This issue started only after upgrading to GWT 2.12.0 and JDK 17
- Other UiBinder-based components in different modules are compiling successfully
- The .ui.xml file exists and is correctly placed
- Module inheritance and source paths appear to be properly configured
- There is also a custom generator involved (MonitorServiceInterfaceProxyGenerator), though it's used elsewhere without issues
At this point, I’m unsure whether this is:
- A compatibility issue with GWT 2.12.0 or JDK 17
- A stricter validation introduced in newer versions
- Or something specific being missed in this module
If anyone has encountered a similar issue or has suggestions on what to check next, your help would be greatly appreciated.
Thanks in advance for your support!
On Friday, March 20, 2026 at 6:18:18 PM UTC+5:30 Thomas Broyer wrote:
On Friday, March 20, 2026 at 1:19:56 PM UTC+1 arpanam...@gmail.com wrote:>
> * Maven build with net.ltgt.gwt.maven:gwt-maven-plugin
> ----
>
> Any insights or best practices for structuring GWT modules across Maven projects would be really helpful.
See https://tbroyer.github.io/gwt-maven-plugin/ and https://tbroyer.github.io/gwt-maven-plugin/usage.htmlFor a client-only library, use `<packaging>gwt-lib</packaging>`, and then depend on it using <type>gwt-lib</type> for better running/debugging support: https://tbroyer.github.io/gwt-maven-plugin/codeserver.html
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 visit https://groups.google.com/d/msgid/google-web-toolkit/a0b1224e-3817-42ac-8597-0ba2f8ce2f18n%40googlegroups.com.
