multiple modules

[aswath-veersoft]

Hi,
There are 30-40 gwt modules we created. They are used in servlets/jsps. So, a page refresh is required to use the modules.
Does this project help in using the gwt modules with out doing page refreshes.
See the link for the turducken pattern
http://www.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams

Thanks

[gilberto-torrezan]

Hi @aswath-veersoft, thanks for your interest in gwt-views.

Unfortunately gwt-views is focused for single-module, multi "places" (views) scenario. I haven't used it on a multi module environment, and I don't know how the project would behave (in this context, "multi module" in the sense of multi entry points).

Although, if you have a single module per page, and that module contains some sort of views navigation, gwt-views can really help.

Using the diagram used at the presentation, gwt-views is a good virtual historian, but cannot be used as an inter-app event bus. You still need to implement it to enable multi modules communication within the same page.

[aswath-veersoft]

Any chances of making it like that pattern. Adding more stuff in one module has limitations as mentioned in that module. So, turducken is required for large gwt projects.

[gilberto-torrezan]

For the inter-app event bus, take a look at this project: https://github.com/sambathl/interapp-eventbus

For modifications on this project to support turducken, do you have a proof-of-concept open-source project so I can use as example and testing environment?

[aswath-veersoft]

I have seen the interapp-eventbus project.
My project (it is a erp project) has menu's redendered through jsps (header). Every menu click, the server request happens to a jsp which comes back with common menus and different gwt module.
I have such 15-20 menus. So, a page refresh is happening as the user navigates the site.
I am looking for help to avoid page refreshes. Will turducken and this gwt-views help to avoid page refreshes?
The project is available at http://ag-mobilewebapp.appspot.com.

[gilberto-torrezan]

I don't know, as I understand turducken would help with multiple modules on the same page (the inter-app event bus makes possible to share events and communication among the modules), while gwt-views helps you to manage the navigation (URL history and tokens) of a given module.

Since the navigation is managed by the jsp, gwt-views adds little value to the project. As I understand, each jsp page renders a GWT module, so you don't need a turducken strategy since there aren't multiple modules and entry points in a single page - you would only need a inter-app event bus when you have multiple modules.

So in your case I don't know how to avoid full page refreshes without a huge refactory on your project, either by removing jsp and handling the navigation via GWT, or removing GWT and using something more lightweight between the pages to reduce the rendering latency.