com.gwtplatform.mvp.client.annotations

Annotation Type ProxyCodeSplitBundle

@Target(value=TYPE)
public @interface ProxyCodeSplitBundle

Use this annotation if you want to have certain Proxys and their associated Presenters to sit behind one split point and to be compiled into one javascript file separately from others.

Use this annotation if you already have too much code splitting using ProxyCodeSplit and it is more efficient to group Presenters because they share a bulk of their code. You will also have to set up your own implementation of a ProviderBundle.

ProviderBundles can be created manually or be generated by GWTP. For the manual approach the bundleClass() and id() need to be defined.

Here is an example use of ProxyCodeSplitBundle using manual declaration:

 @ProxyCodeSplitBundle(bundleClass = MyPresenterBundle.class, id = MyPresenterBundle.ID_Object1)
 public interface MyProxy extends ProxyPlace<Object1> {
 }
 

If you use GWTP's generation of ApplicationController all bundles will be automatically generated for you, all that you need are string identifiers for each unique bundle. The best way to keep your bundles in order is to create an interface that identifies your bundles.

public interface Bundles {
   String MAIN = "Main";
   String OTHER = "Other";
 }

Here is an example use of {@link ProxyCodeSplitBundle} when using GWTP's generation feature:

{@code
 @ProxyCodeSplitBundle(Bundles.MAIN)
 public interface MyProxy extends ProxyPlace<Object1> {
 }

See Also:

ProviderBundle, Code Splitting

Optional Element Summary

Optional Elements

Modifier and Type	Optional Element and Description
Class<? extends ProviderBundle>	bundleClass
int	id
String	value

Element Detail

bundleClass

public abstract Class<? extends ProviderBundle> bundleClass

Default:

com.gwtplatform.mvp.client.annotations.ProxyCodeSplitBundle.NoOpProviderBundle.class

id

public abstract int id

Default:

-1

value

public abstract String value

Default:

""