Re: GWT Deferred Binding Error – UiBinder Not Resolved from Dependent Module (phoenix-air)

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.html

For 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/09e05458-a9d5-4061-bfc1-bc688b7a1587n%40googlegroups.com.

GWT Deferred Binding Error – UiBinder Not Resolved from Dependent Module (phoenix-air)

Hi Team,

I'm facing an issue with GWT deferred binding while working with a modular Maven setup and would appreciate any guidance.

Error:

Failed to resolve AwbCustomerUiBinder via deferred binding

---

 Project Setup

We have a multi-module Maven project:

• phoenix-air → packaged as a JAR (contains GWT UI, UiBinder files)

• phoenix-main → WAR (main application)

• Parent project builds all modules

In application.gwt.xml, we are inheriting the air module:

<inherits name="com.shipco.phoenix.air.Air"/>

The dependency is also added in phoenix-main:

<dependency> <groupId>phoenix</groupId> <artifactId>phoenix-air</artifactId> <version>1.0</version> </dependency>

---

 Air Module Details

In phoenix-air:

• AwbCustomer.java uses UiBinder:

interface AwbCustomerUiBinder extends UiBinder<Widget, AwbCustomer> {} private static AwbCustomerUiBinder uiBinder = GWT.create(AwbCustomerUiBinder.class);

• Corresponding file exists:

AwbCustomer.ui.xml

• Both are in the same package:

modules/awb/client/airimport/view/awbpopup/

• air.gwt.xml includes:

<source path="modules/awb/client"/>

• POM includes .ui.xml and .gwt.xml in resources

 Additional Context

• Other modules with similar setup seem to work (possibly not using UiBinder or structured differently)

• Using GWT 2.12.x

• 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.

Thanks in advance!

Best regards,
Arpan Ameta

--
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/041e17ff-f23f-464f-af19-f3ebc28c800en%40googlegroups.com.

Re: GWT Datagrid

A cool 80,000 lines of CSS in your demo.   https://dominokit.com/domino-ui/demo/v2/css/domino-ui/domino-ui.css   😲

On Wednesday, 18 March 2026 at 8:58:39 am UTC+11 Vegegoku wrote:

In general starting from version 2.0.0 everything is controlled with css variables and all css classes are prefixed to avoid as much as possible any collision with other css.

You can simply get the domino-ui-theme-default.css, domino-ui-theme-dark, domino-ui-theme-light and start playing with the css variables

I am preparing some documentation for theming to add to the website but I just need some time to finish them and publish.

On Monday, March 16, 2026 at 6:05:29 PM UTC+3 cbruno...@gmail.com wrote:

Domino ui looks great, I didnt see the data grid before but it looks like it solves it for using DOM nodes nicely. Is there documentation on theming specific components so as to integrate with a project not using a material ui theme? Not being a fan of material was always my hesitation with domino-ui. 

On Monday, March 16, 2026 at 3:51:59 AM UTC-5 Vegegoku wrote:

Nice works.
In domino-ui we thought initially of using the canvas approach but we didnt go that way because we needed to have something that is easy to customize and extends and support more types of components out of the box. I went with the approach to first implement virtual scrolling on a list of data that allowed other component to hook in and listen to scrolling events and based on that it knows what needs to be rendered and what needs to be removed. and it can handle selection  and search without a big overhead on the performance.

Here is a live Data table

https://dominokit.com/domino-ui/demo/v2/datatable/live-grid

and this one is for Simple Lists 

https://dominokit.com/domino-ui/demo/v2/data/data-list

Or for drop down lists

https://dominokit.com/domino-ui/demo/v2/data/data-select

And the plan is to expand on this to support more use cases. they all uses the virtual scrolling with a long div and can handle huge number of records.

On Monday, March 16, 2026 at 11:35:23 AM UTC+3 Craig Mitchell wrote:

Browsers have gotten a lot smarter.  I tried to do this about 8 years ago in a similar way with a fake tall div to handle the scroll, but asking for a div around 10 million pixels high caused the browser to struggle, so I ended up creating my own scrollbar.  It was a bit janky.

Yours is working great, and the browser doesn't seem to care about the tall div.  Well done!

On Monday, 16 March 2026 at 6:01:41 pm UTC+11 RobW wrote:

Looking very useful - nice work

On Sunday, 15 March 2026 at 22:05:03 UTC cbruno...@gmail.com wrote:

I did consider using the DOM to render the cells. The main reason I went with canvas (aside from speed) was wanted the neat column reordering effect where the contents of the cells moves with the dragged column. Definitely this implementation is not a general datatable (e.g. its not useful for rendering UI elements in the cells, just data that can be drawn as strings). The main motivation is to display data from a data set. 

On Sunday, March 15, 2026 at 4:14:26 PM UTC-5 Jens wrote:

Back in the days of IE6 I did something similar for long lists but without using canvas. Basically the developer had to define the item/cell height (or multiple heights if multiple item types exist in the list) so the height of the container/list and absolute position of items in that list could be calculated. Then it made sure to use the minimal amount of elements needed to fill the visible area and during scrolling elements were added/removed accordingly. So only 30 elements or so were used at a time.

That way the list could handle a lot ot items in IE6 at the cost of predefined static item heights while still sticking to the mental model of widgets. Later GWT introduced cell widgets which use HTML strings to use with innerHTML. Because of the string based nature I never really liked the API and still using the list made for IE6.

Using canvas to render the table is interesting and definitely fast but it also means styling is limited compared to CSS + HTML without reinventing the wheel for canvas. Something simple as a checkbox or button in a row matching the design system will be difficult.

Have you tried the DOM based approach I outlined above and it was too slow for your use case? But it is nice that AI can help to explore such side projects you would never start otherwise because of time.

-- J.

cbruno...@gmail.com schrieb am Sonntag, 15. März 2026 um 03:28:25 UTC+1:

I finally got around to bringing something like NSTableView from Cocoa to the web in pure GWT. Still a work in progress, this is something I wanted to get around to for the last 10 years:

- Millions of rows,

- Slick column reordering

- Row headers

- Various selection modes

I was able to get it done while pair programming with Claude.

https://datatable.cocoawerks.com

 Claude does well with Java and GWT. It works best when it can look at your project structure and add features that are not conceptually difficult but are tedious, especially accounting for edge cases.  Its able to even understand and flawlessly add or refactor changes to UiBinder. 

I plan to release this on GitHub once its done..need to add a DataSource and the ability to have editors. But please let me know if anyone is interested in a component like this.

 

--
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/51adf730-1976-4283-9ca9-8dfc6bc0ee51n%40googlegroups.com.

Re: GWT Datagrid

In general starting from version 2.0.0 everything is controlled with css variables and all css classes are prefixed to avoid as much as possible any collision with other css.

You can simply get the domino-ui-theme-default.css, domino-ui-theme-dark, domino-ui-theme-light and start playing with the css variables

I am preparing some documentation for theming to add to the website but I just need some time to finish them and publish.

On Monday, March 16, 2026 at 6:05:29 PM UTC+3 cbruno...@gmail.com wrote:

Domino ui looks great, I didnt see the data grid before but it looks like it solves it for using DOM nodes nicely. Is there documentation on theming specific components so as to integrate with a project not using a material ui theme? Not being a fan of material was always my hesitation with domino-ui. 

On Monday, March 16, 2026 at 3:51:59 AM UTC-5 Vegegoku wrote:

Nice works.
In domino-ui we thought initially of using the canvas approach but we didnt go that way because we needed to have something that is easy to customize and extends and support more types of components out of the box. I went with the approach to first implement virtual scrolling on a list of data that allowed other component to hook in and listen to scrolling events and based on that it knows what needs to be rendered and what needs to be removed. and it can handle selection  and search without a big overhead on the performance.

Here is a live Data table

https://dominokit.com/domino-ui/demo/v2/datatable/live-grid

and this one is for Simple Lists 

https://dominokit.com/domino-ui/demo/v2/data/data-list

Or for drop down lists

https://dominokit.com/domino-ui/demo/v2/data/data-select

And the plan is to expand on this to support more use cases. they all uses the virtual scrolling with a long div and can handle huge number of records.

On Monday, March 16, 2026 at 11:35:23 AM UTC+3 Craig Mitchell wrote:

Browsers have gotten a lot smarter.  I tried to do this about 8 years ago in a similar way with a fake tall div to handle the scroll, but asking for a div around 10 million pixels high caused the browser to struggle, so I ended up creating my own scrollbar.  It was a bit janky.

Yours is working great, and the browser doesn't seem to care about the tall div.  Well done!

On Monday, 16 March 2026 at 6:01:41 pm UTC+11 RobW wrote:

Looking very useful - nice work

On Sunday, 15 March 2026 at 22:05:03 UTC cbruno...@gmail.com wrote:

I did consider using the DOM to render the cells. The main reason I went with canvas (aside from speed) was wanted the neat column reordering effect where the contents of the cells moves with the dragged column. Definitely this implementation is not a general datatable (e.g. its not useful for rendering UI elements in the cells, just data that can be drawn as strings). The main motivation is to display data from a data set. 

On Sunday, March 15, 2026 at 4:14:26 PM UTC-5 Jens wrote:

Back in the days of IE6 I did something similar for long lists but without using canvas. Basically the developer had to define the item/cell height (or multiple heights if multiple item types exist in the list) so the height of the container/list and absolute position of items in that list could be calculated. Then it made sure to use the minimal amount of elements needed to fill the visible area and during scrolling elements were added/removed accordingly. So only 30 elements or so were used at a time.

That way the list could handle a lot ot items in IE6 at the cost of predefined static item heights while still sticking to the mental model of widgets. Later GWT introduced cell widgets which use HTML strings to use with innerHTML. Because of the string based nature I never really liked the API and still using the list made for IE6.

Using canvas to render the table is interesting and definitely fast but it also means styling is limited compared to CSS + HTML without reinventing the wheel for canvas. Something simple as a checkbox or button in a row matching the design system will be difficult.

Have you tried the DOM based approach I outlined above and it was too slow for your use case? But it is nice that AI can help to explore such side projects you would never start otherwise because of time.

-- J.

cbruno...@gmail.com schrieb am Sonntag, 15. März 2026 um 03:28:25 UTC+1:

I finally got around to bringing something like NSTableView from Cocoa to the web in pure GWT. Still a work in progress, this is something I wanted to get around to for the last 10 years:

- Millions of rows,

- Slick column reordering

- Row headers

- Various selection modes

I was able to get it done while pair programming with Claude.

https://datatable.cocoawerks.com

 Claude does well with Java and GWT. It works best when it can look at your project structure and add features that are not conceptually difficult but are tedious, especially accounting for edge cases.  Its able to even understand and flawlessly add or refactor changes to UiBinder. 

I plan to release this on GitHub once its done..need to add a DataSource and the ability to have editors. But please let me know if anyone is interested in a component like this.

 

--
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/2f8f3db3-fa01-404e-9173-010694033319n%40googlegroups.com.

Re: GWT Datagrid

Domino ui looks great, I didnt see the data grid before but it looks like it solves it for using DOM nodes nicely. Is there documentation on theming specific components so as to integrate with a project not using a material ui theme? Not being a fan of material was always my hesitation with domino-ui. 

On Monday, March 16, 2026 at 3:51:59 AM UTC-5 Vegegoku wrote:

Nice works.
In domino-ui we thought initially of using the canvas approach but we didnt go that way because we needed to have something that is easy to customize and extends and support more types of components out of the box. I went with the approach to first implement virtual scrolling on a list of data that allowed other component to hook in and listen to scrolling events and based on that it knows what needs to be rendered and what needs to be removed. and it can handle selection  and search without a big overhead on the performance.

Here is a live Data table

https://dominokit.com/domino-ui/demo/v2/datatable/live-grid

and this one is for Simple Lists 

https://dominokit.com/domino-ui/demo/v2/data/data-list

Or for drop down lists

https://dominokit.com/domino-ui/demo/v2/data/data-select

And the plan is to expand on this to support more use cases. they all uses the virtual scrolling with a long div and can handle huge number of records.

On Monday, March 16, 2026 at 11:35:23 AM UTC+3 Craig Mitchell wrote:

Browsers have gotten a lot smarter.  I tried to do this about 8 years ago in a similar way with a fake tall div to handle the scroll, but asking for a div around 10 million pixels high caused the browser to struggle, so I ended up creating my own scrollbar.  It was a bit janky.

Yours is working great, and the browser doesn't seem to care about the tall div.  Well done!

On Monday, 16 March 2026 at 6:01:41 pm UTC+11 RobW wrote:

Looking very useful - nice work

On Sunday, 15 March 2026 at 22:05:03 UTC cbruno...@gmail.com wrote:

I did consider using the DOM to render the cells. The main reason I went with canvas (aside from speed) was wanted the neat column reordering effect where the contents of the cells moves with the dragged column. Definitely this implementation is not a general datatable (e.g. its not useful for rendering UI elements in the cells, just data that can be drawn as strings). The main motivation is to display data from a data set. 

On Sunday, March 15, 2026 at 4:14:26 PM UTC-5 Jens wrote:

Back in the days of IE6 I did something similar for long lists but without using canvas. Basically the developer had to define the item/cell height (or multiple heights if multiple item types exist in the list) so the height of the container/list and absolute position of items in that list could be calculated. Then it made sure to use the minimal amount of elements needed to fill the visible area and during scrolling elements were added/removed accordingly. So only 30 elements or so were used at a time.

That way the list could handle a lot ot items in IE6 at the cost of predefined static item heights while still sticking to the mental model of widgets. Later GWT introduced cell widgets which use HTML strings to use with innerHTML. Because of the string based nature I never really liked the API and still using the list made for IE6.

Using canvas to render the table is interesting and definitely fast but it also means styling is limited compared to CSS + HTML without reinventing the wheel for canvas. Something simple as a checkbox or button in a row matching the design system will be difficult.

Have you tried the DOM based approach I outlined above and it was too slow for your use case? But it is nice that AI can help to explore such side projects you would never start otherwise because of time.

-- J.

cbruno...@gmail.com schrieb am Sonntag, 15. März 2026 um 03:28:25 UTC+1:

I finally got around to bringing something like NSTableView from Cocoa to the web in pure GWT. Still a work in progress, this is something I wanted to get around to for the last 10 years:

- Millions of rows,

- Slick column reordering

- Row headers

- Various selection modes

I was able to get it done while pair programming with Claude.

https://datatable.cocoawerks.com

 Claude does well with Java and GWT. It works best when it can look at your project structure and add features that are not conceptually difficult but are tedious, especially accounting for edge cases.  Its able to even understand and flawlessly add or refactor changes to UiBinder. 

I plan to release this on GitHub once its done..need to add a DataSource and the ability to have editors. But please let me know if anyone is interested in a component like this.

 

--
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/87ec9370-0deb-421b-a25f-0ea1ef19facan%40googlegroups.com.

Re: GWT Datagrid

I ran into this max div height also and the trick was to use virtual scrolling - remap the the physical scroll position to a logical one once a max height was exceeded.  

On Monday, March 16, 2026 at 3:35:23 AM UTC-5 Craig Mitchell wrote:

Browsers have gotten a lot smarter.  I tried to do this about 8 years ago in a similar way with a fake tall div to handle the scroll, but asking for a div around 10 million pixels high caused the browser to struggle, so I ended up creating my own scrollbar.  It was a bit janky.

Yours is working great, and the browser doesn't seem to care about the tall div.  Well done!

On Monday, 16 March 2026 at 6:01:41 pm UTC+11 RobW wrote:

Looking very useful - nice work

On Sunday, 15 March 2026 at 22:05:03 UTC cbruno...@gmail.com wrote:

I did consider using the DOM to render the cells. The main reason I went with canvas (aside from speed) was wanted the neat column reordering effect where the contents of the cells moves with the dragged column. Definitely this implementation is not a general datatable (e.g. its not useful for rendering UI elements in the cells, just data that can be drawn as strings). The main motivation is to display data from a data set. 

On Sunday, March 15, 2026 at 4:14:26 PM UTC-5 Jens wrote:

Back in the days of IE6 I did something similar for long lists but without using canvas. Basically the developer had to define the item/cell height (or multiple heights if multiple item types exist in the list) so the height of the container/list and absolute position of items in that list could be calculated. Then it made sure to use the minimal amount of elements needed to fill the visible area and during scrolling elements were added/removed accordingly. So only 30 elements or so were used at a time.

That way the list could handle a lot ot items in IE6 at the cost of predefined static item heights while still sticking to the mental model of widgets. Later GWT introduced cell widgets which use HTML strings to use with innerHTML. Because of the string based nature I never really liked the API and still using the list made for IE6.

Using canvas to render the table is interesting and definitely fast but it also means styling is limited compared to CSS + HTML without reinventing the wheel for canvas. Something simple as a checkbox or button in a row matching the design system will be difficult.

Have you tried the DOM based approach I outlined above and it was too slow for your use case? But it is nice that AI can help to explore such side projects you would never start otherwise because of time.

-- J.

cbruno...@gmail.com schrieb am Sonntag, 15. März 2026 um 03:28:25 UTC+1:

I finally got around to bringing something like NSTableView from Cocoa to the web in pure GWT. Still a work in progress, this is something I wanted to get around to for the last 10 years:

- Millions of rows,

- Slick column reordering

- Row headers

- Various selection modes

I was able to get it done while pair programming with Claude.

https://datatable.cocoawerks.com

 Claude does well with Java and GWT. It works best when it can look at your project structure and add features that are not conceptually difficult but are tedious, especially accounting for edge cases.  Its able to even understand and flawlessly add or refactor changes to UiBinder. 

I plan to release this on GitHub once its done..need to add a DataSource and the ability to have editors. But please let me know if anyone is interested in a component like this.

 

--
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/c4e37c37-03e8-4d63-b61c-502cf4abd543n%40googlegroups.com.

Re: GWT Datagrid

Nice works.
In domino-ui we thought initially of using the canvas approach but we didnt go that way because we needed to have something that is easy to customize and extends and support more types of components out of the box. I went with the approach to first implement virtual scrolling on a list of data that allowed other component to hook in and listen to scrolling events and based on that it knows what needs to be rendered and what needs to be removed. and it can handle selection  and search without a big overhead on the performance.

Here is a live Data table

https://dominokit.com/domino-ui/demo/v2/datatable/live-grid

and this one is for Simple Lists 

https://dominokit.com/domino-ui/demo/v2/data/data-list

Or for drop down lists

https://dominokit.com/domino-ui/demo/v2/data/data-select

And the plan is to expand on this to support more use cases. they all uses the virtual scrolling with a long div and can handle huge number of records.

On Monday, March 16, 2026 at 11:35:23 AM UTC+3 Craig Mitchell wrote:

Browsers have gotten a lot smarter.  I tried to do this about 8 years ago in a similar way with a fake tall div to handle the scroll, but asking for a div around 10 million pixels high caused the browser to struggle, so I ended up creating my own scrollbar.  It was a bit janky.

Yours is working great, and the browser doesn't seem to care about the tall div.  Well done!

On Monday, 16 March 2026 at 6:01:41 pm UTC+11 RobW wrote:

Looking very useful - nice work

On Sunday, 15 March 2026 at 22:05:03 UTC cbruno...@gmail.com wrote:

I did consider using the DOM to render the cells. The main reason I went with canvas (aside from speed) was wanted the neat column reordering effect where the contents of the cells moves with the dragged column. Definitely this implementation is not a general datatable (e.g. its not useful for rendering UI elements in the cells, just data that can be drawn as strings). The main motivation is to display data from a data set. 

On Sunday, March 15, 2026 at 4:14:26 PM UTC-5 Jens wrote:

Back in the days of IE6 I did something similar for long lists but without using canvas. Basically the developer had to define the item/cell height (or multiple heights if multiple item types exist in the list) so the height of the container/list and absolute position of items in that list could be calculated. Then it made sure to use the minimal amount of elements needed to fill the visible area and during scrolling elements were added/removed accordingly. So only 30 elements or so were used at a time.

That way the list could handle a lot ot items in IE6 at the cost of predefined static item heights while still sticking to the mental model of widgets. Later GWT introduced cell widgets which use HTML strings to use with innerHTML. Because of the string based nature I never really liked the API and still using the list made for IE6.

Using canvas to render the table is interesting and definitely fast but it also means styling is limited compared to CSS + HTML without reinventing the wheel for canvas. Something simple as a checkbox or button in a row matching the design system will be difficult.

Have you tried the DOM based approach I outlined above and it was too slow for your use case? But it is nice that AI can help to explore such side projects you would never start otherwise because of time.

-- J.

cbruno...@gmail.com schrieb am Sonntag, 15. März 2026 um 03:28:25 UTC+1:

I finally got around to bringing something like NSTableView from Cocoa to the web in pure GWT. Still a work in progress, this is something I wanted to get around to for the last 10 years:

- Millions of rows,

- Slick column reordering

- Row headers

- Various selection modes

I was able to get it done while pair programming with Claude.

https://datatable.cocoawerks.com

 Claude does well with Java and GWT. It works best when it can look at your project structure and add features that are not conceptually difficult but are tedious, especially accounting for edge cases.  Its able to even understand and flawlessly add or refactor changes to UiBinder. 

I plan to release this on GitHub once its done..need to add a DataSource and the ability to have editors. But please let me know if anyone is interested in a component like this.

 

--
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/06330629-7159-400e-a74a-49214c0545cen%40googlegroups.com.