Possible to disable GWT EntryPoint during runtime?

1
votes

In my GWT 2.5 application, I got two entry points. EntryPoint A is the main application and EntryPoint B provides a widget version of my application.

Depending on a startup parameter, which I supply to the container, I want to enable/disable EntryPoint B. How can I achieve that? I know how to disable an EntryPoint completely during compile time by removing the correspondig declaration from my *.gwt.xml file.

4
gwtentry-point
Can u tell me how you are passing startup parameter to Container and what is that container? - Adarsha
Very simple, I e.g. use system variables, which I can retrieve via System.getProperty. Also, I have defined a GWT RPC interface to transfer those values to the client if needed. - Sebi

4 Answers

2
votes

Seems like you could create two modules, where each provide a different entry point. Both would inherit from the common logic module. Each then has a different boostrap JavaScript URL (the .nocache.js). Disadvantage is that those will be completely different scripts to browser, so no caching benefits if you switch between widget and full version.

You can also do simple test within entry point method whether the entry point should be executed - just return if not. You can for instance check whether expected container element exists in DOM, or URL, or whatever. There is no much problem if two entry points are executed in a single module.

2
votes

An GWT application can have only one Entrypoint. So instead of 2 Applications you can create 2 containers say ContainerA and ContainerB. In Entrypoint's onModuleLoad method you do an RPC call to fetch the Container deciding parameter. And based on the parameter you do 

public void onModuleLoad()
{ 
      getRPCService.getStartUpParameter( AsyncCallBack<Parameter>
      { 
             public void onFailure()
             {
             }

             public void onSuccess(Parameter parameter)
             {
                   if( ContainerARequired( parameter ) )
                   {
                          RoolLayoutPanel.get().add( ContanerA )
                   }
                   else
                   {
                          RoolLayoutPanel.get().add( ContanerB )
                   }
             }
      });
}

With this method your js size will increase. So use code splitting and Run Async concepts to split the big js file in to smaller ones. And with this you can load only required js in to the browser.

0
votes

In your gwt.xml

<define-property name="disableEntryPoint" values="true,false" />

<!-- Provide a default -->
<set-property name="alternateFeatures" value="false" />


<replace-with class="com.example.EntryPoint1">
  <when-type-is class="com.example.EntryPoint2" />
  <when-property-is name="disableEntryPoint" value="false" />
</replace-with>

Refer this :http://code.google.com/p/google-web-toolkit/wiki/ConditionalProperties

0
votes

maybe, it's better to have one application by own one entry point. in result, you will have 2 modules with own context and access paths:

  • /entryA
  • /entryB

also, two files:

  • EntryA.gwt.xml
  • EntryB.gwt.xml

those will include common stuff from Application.gwt.xml