Versions Compared

Key

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

...

  • With a platform, there is a much clearer distinction between customization and the standard product. By introducing the use of explicit APIs, with which functionalities can be added to the basic platform, the procedure for developers is much clearer. Among other things, this leads to a much more flexible and predictable method of executing updates and migrations than before.
  • Partners who want to create their own product with XperienCentral as an OEM product underneath can also do this with the platform strategy.
  • With this platform not only partners, but also GX Software itself can easily realize new solutions or products.

 

 

Nomenclature

The origin of plugins in XperienCentral lies in the identical functionality available in GX WebManager 9 which was known as a Web Component Bundle, referred to using the 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.

 

XperienCentral Components

...

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 lies in the identical functionality available in GX WebManager 9 which was known as a Web Component Bundle, referred to using the 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.