Versions Compared

Old Version 36

changes.mady.by.user Joël DRIGO

Saved on

compared with

New Version 37

changes.mady.by.user Joël DRIGO

Saved on

Key

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

Overview

The purpose of the plugin is to allow to set up a specific configuration for a Wedia portal application, by overriding a basic configuration provided by the product.

...

  • _portal

  • _portal@config

  • _portal@config@picker

The path _portal@$config@picker designates a configuration defined in 3 folders whose relative paths are successively :

...

In case of an error during the resolution, the postprocessor is ignored and therefore its value is removed from the resolved path.

Logging

Logging can be done using

  • The fr.wedia.confres.core.model.processor.PostProcessorLogger class for a log specific to the execution of custom postprocessors

  • The fr.wedia.confres.plugin.PluginLogger class to log in the WXM_CONFIG_RESOLVER main log

Example:

Code Block
package fr.wedia.confref.custom.processor;

import fr.wedia.confres.core.model.processor.PostProcessorLogger;

class CustomProcessorLoggingExample extends AbstractPostProcessor {

    private JsonElement config;
     
    public void start() {
          if ( PostProcessorLogger.info() ) {
              PostProcessorLogger.info(CustomProcessorLoggingExample.class,"starting component with config " + config);          
          }
          ...
     }

     @Override
     String getValue(ProcessorContext context) {
         if ( PostProcessorLogger.trace() ) {
             PostProcessorLogger.trace(context, CustomProcessorLoggingExample.class,"getting value from post processor for surfer " + context.getSurfer());
         }
         return ...
     }
     
}

Services

general information

...