Question to the forum. We are rewriting our 120K line GWT application to
run on an OSGi architecture so that we no longer deploy a megawar file and
can update individual parts of the application (currently 25 modules, will
be 85 in a year) UI and services without affecting others. We've created
I guess I would publish a JS API in the parent core application via JSNI
and then call the API methods from your submodule iFrame (via
top.apiMethodName() ) when they have loaded and need to customize the
header/footer. This would be your second solution but the other way around
which avoids
Thanks Jen's, I'll give the JSNI and postMessage() methods a try.
Sincerely,
Joseph
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
Assuming the amount of JS to export is not a lot, I also see exporting
JS and exposing it as a very viable alternative as Jen previously
pointed out.
Something else that comes to mind, a lot more involved I must admit is
to use a server-push approach. The header/footer module keeps an open
Thanks Alfredo. I'll try the intra-browser communication for now as it will
hopefully take the least overhead.
Sincerely,
Joseph
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
