Hi Berto, Hi Mike, can you give me some more details about your plugin-design? What architecture are you using for the several applications, MVC or MVP?
Regards, Daniel On 11 Jun., 20:36, lemaiol <lema...@gmail.com> wrote: > HI Mike, > > If I got it right, you want a main GWT application (own WAR) and > several other GWT applications (own WAR each) that could be loaded > altogether in the same host page (the one from the main application) > and communicate using a "dispatching" interface (maybe an event bus). > I have implemented exactly this for a customer and it is definitely > possible. > > The problem is mainly how to communicate GWT classes which have been > compiled and "linked" in different applications. Also when the Java > classes are the same (shared through a common library) the GWT compile > process produces a result that is neither linked together because of > the separated compilations nor linked together at load time. JSNI > comes to the rescue allowing the embedding of native JS code that > remains the same even after the compile process (ignored by GWT > compiler). > > I used JavaScriptObject classes to define the plugins common data > model and implemented a pair of JSNI classes to do the gluing. I also > used a server side mechanism to configure the plugins repository and > to generate the GWT host page dynamically. This will load the plugins > from the remote web applications and generate some required > structures. > > If this is what you need, just tell me which details you are > interested in. > > What you mentioned about using EventBus out of GWT would be an > improvement. Could you point me to where you read about it? Have you > got also other threads about this topic? I would like to learn about > others needs and ideas. > > Hope it helps, > Berto > > On Jun 9, 12:30 pm, manstis <michael.ans...@gmail.com> wrote: > > > > > > > > > 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 google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
