We really need something like this too. We've developed a workbench UI,
that has plugins - all currently compile time. Would be nice to be able to
have those as runtime plugins, even if they are self contained GWT apps. As
you pointed out you can not just simply pass those objects between
It seems like this is a common request. I wonder if there is anything the GWT
team can put into the roadmap, that would allow for the compilation of a core
application. Then the later compilation, aka “linking”, of other gwt code -
where the user annotates things not to be pruned, so they can
We really need something like this too. We've developed a workbench UI,
that has plugins - all currently compile time. Would be nice to be able to
have those as runtime plugins, even if they are self contained GWT apps. As
you pointed out you can not just simply pass those objects between the
Davide,
GWT is not really made to be deployed as multiple GWT compilation units.
This is done for the sake of performance.
I had similar requirements as you I needed to be able to co-host multiple
GWT applications on one page (a portal system) but they are compiled
separately and developed by
I have to support the deployment of additional modules in order to
dynamically extend my employer's GWT application, adding new features or
customizing the existing ones.
I mean *something like a plugin system which dynamically loads and executes
new code deployed at any point of time*.
The
