Page History

...

Starting Point for Integration

I began designing an integration between Wicket and GWT, but never followed through to implementation. I concluded that the work of massaging GWT into some kind of cohesive development environment with Wicket outweighed the benefit to my project at the time I write this. Improvements come in the form of an incremental Eclipse builder for GWT, or other niftyness spawning from the GoogleplexHere is a partial design for wrapping GWT widgets with Wicket components.

Class Diagram

This class diagram captures the design of a potential integration between Wicket and GWT.

...

FooComponent and FooService implement an example GWT-widget-as-wicket-component.

Obstacles

I concluded that the work of massaging GWT into some kind of cohesive development environment with Wicket outweighed the benefit to my project at the time I write this. Getting the GWT development shell to render pages out of their servlet which were also passed through the Wicket servlet filter was trivial, but that's where I stopped. Rectifying the URI schemes for the two frameworks to get them to cooperatively render a page was the next step. A specialized Wicket URICodingStrategy might help here.

Other improvements may come in the form of an incremental Eclipse builder for GWT, or other niftyness spawning from the Googleplex.