passing generated data in and out of GWT that doesn't come from the RPC is a bit messy... there are a few ways to do it, but you really want to avoid trying to do that unless GWT initiates the call.
I suspect that is the reason most people who have looked into it have abandoned the idea of integration. However, I start to see it as a possibility because of the way in GWT you can attach GWT components to any DOM element... one way to integrate would be to have wicket generate the GWT side based upon its own configuration and bind the GWT components to the wicket/html equivalent elements. That is by no means a hard plan, but certainly something to try... Not sure yet how that would work on the server side though (not enough experience with Wicket). - Brill Pappin On Wed, May 14, 2008 at 1:42 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > you can always generate a callback url using urlfor(interface) and > then pass that url to the gwt component. for example of this see how > Link generates a url that results in onLinkClicked() being invoked on > it. > > -igor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
