Versions Compared

Old Version 17

changes.mady.by.user Matthew Wagner

Saved on

compared with

New Version 18

changes.mady.by.user Matthew Wagner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
themeEclipse
...
public class Activator extends ComponentBundleActivatorBase {
  /**
   * Creates and returns the bundle definition of the plugin.
   * @return the bundle definition of the plugin.
   */
  @Override
  protected
ComponentBundleDefinition getBundleDefinition() {
    ComponentBundleDefinitionImpl componentBundleDefinition =
      new ComponentBundleDefinitionImpl();   
componentBundleDefinition.setId(WCBConstants.BUNDLE_ID);   
componentBundleDefinition.setName(WCBConstants.BUNDLE_NAME);   
componentBundleDefinition.setNameSpace(WCBConstants.NAMESPACE_URI);   
componentBundleDefinition.setDescription(WCBConstants.BUNDLE_DESCRIPTION);   
componentBundleDefinition.setComponentDefinitions(getComponentDefinitions());   
    return componentBundleDefinition;
  }
...

 

  

Nomenclature

The origin of plugins in XperienCentral comes from the identical functionality available in GX WebManager 9 which were known as Web Component Bundles, referred to using the shortened abbreviation WCB. Because of this legacy, you will come across the string "WCB" in functions, methods, properties and parameters in the source code and Java classes exposed by XperienCentral for developing plugins. The phased-out term "WCB" is identical to the term "plugin" used in all XperienCentral documentation.