Examples of ModificationExtractor

• org.impalaframework.module.ModificationExtractor
  The job of a {@link ModificationExtractor} is to determine what changes are requiredto convert from the currently loaded module hierarchy (which at pre-load time will be empty), to a desired module hierarchy as determined by a second hierarchy of {@link ModuleDefinition}s.

  For example, suppose module A is the root module and it's child, module B, is loaded. Suppose also that change the desired module hierarchy so that module A will still be loaded, but it will have just one child, module C. The actions that need to take place are: B must be unloaded C must be loaded

  The advantage of the use of the {@link ModificationExtractor} is that it is possibleto edit a module configuration hierarchy offline, then apply it in one go, without having to work out individually what are the module changes required to effect this change. @author Phil Zoio

• org.impalaframework.module.modification.ModificationExtractor
• org.impalaframework.module.spi.ModificationExtractor
  The job of a {@link ModificationExtractor} is to determine what changes are requiredto convert from the currently loaded module hierarchy (which at pre-load time will be empty), to a desired module hierarchy as determined by a second hierarchy of {@link ModuleDefinition}s.

  For example, suppose module A is the root module and it's child, module B, is loaded. Suppose also that change the desired module hierarchy so that module A will still be loaded, but it will have just one child, module C. The actions that need to take place are: B must be unloaded C must be loaded

  The advantage of the use of the {@link ModificationExtractor} is that it is possibleto edit a module configuration hierarchy offline, then apply it in one go, without having to work out individually what are the module changes required to effect this change. @author Phil Zoio

Examples of org.impalaframework.module.spi.ModificationExtractor