Ginjector modules in Gwtptabsample

[Ignacio Baca Moreno-Torres]

In the gwtptabsample project the new bootstrapping technique was used (https://github.com/ArcBees/GWTP/wiki/Bootstrapping-in-GWTP) but I have some doubts.

This is the modules and extensions code used in the Module.gwt.xml

  <set-configuration-property name="gin.ginjector.modules"

                              value="com.gwtplatform.samples.tab.client.gin.ClientModule,

                                     com.gwtplatform.samples.tab.client.application.ui.UiModule"/>

  <set-configuration-property name="gin.ginjector.extensions"

                              value="com.gwtplatform.samples.tab.client.gin.GinjectorExtension"/>

First: Why only ClientModule and UiModule are added to the value field? The module structure is ClientModule -- install --> ApplicationModule -- install --> UiModule. Why ApplicationModule isn't required to be in the gin.ginjector.modules attribute?

Second: What's extensions for? I suppose extensions are required in the same way that ClientGingector was required before... Maybe add the extensions example in the Bootstrapping in GWTP document might be useful.

[Christian Goudreau]

You're right, UiModule shouldn't be there.

GinjectorExtension allows you to create a Ginjector with custom bindings that you need to have access too for the tabs.

--
 
 

--
Christian Goudreau

www.arcbees.com

[Christian Goudreau]

FYI, extensions isn't needed in other samples.

--
Christian Goudreau

www.arcbees.com