Firstly, I know a lot has been said about this in the past and I have read many posts but I did not see an immediate solution so would appreciate the opinion of those more knowledgable than I.
I'd like to create a single GWT application WAR (let's call it "container") that can "host" (or embed) other GWT applications (let's call an example "editor"). All, for simplicity, would be deployed on the same web-server. The "container" has a client-side service API that uses GWT-RPC to server-side services to be shared by the "container" and "editor" e.g. "loadData(..)". Can I use gwt-exporter to export the "service" client-side API and use gwt-api-interop to create an equivalent cross-application Java "service" API that "editor" can utilise? For example, the service API has a method "addEditorToContainer(Widget)" so the "editor" can add itself to the "container". I've also read about EventBus becoming available outside of GWT(?); if I've read correctly is it possible to use a single EventBus across both applications? I appreciate this becomes trivial if I add the "editor" into the "container" application before compile-time; but ideally I want to allow for third-parties to develop "editors" without having to re- compile it into "container". In theory, all they'd need to do is reference the gwt-api-interop generated common API. Perhaps my questions are mis-guided; and, if anybody else has experience and success of writing a "pluggable" infrastructure, perhaps you'd be so kind as to share what you've learnt? With kind regards, Mike -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
