Examples of org.osgi.service.cm.ConfigurationPlugin

org.osgi.service.cm.ConfigurationPlugin
A service interface for processing configuration dictionary before the update.
A bundle registers a {@code ConfigurationPlugin} object in order to processconfiguration updates before they reach the Managed Service or Managed Service Factory. The Configuration Admin service will detect registrations of Configuration Plugin services and must call these services every time before it calls the {@code ManagedService} or {@code ManagedServiceFactory}{@code updated} method. The Configuration Plugin service thus has theopportunity to view and modify the properties before they are passed to the Managed Service or Managed Service Factory.
Configuration Plugin (plugin) services have full read/write access to all configuration information that passes through them.
The {@code Integer} {@code service.cmRanking} registration property may bespecified. Not specifying this registration property, or setting it to something other than an {@code Integer}, is the same as setting it to the {@code Integer} zero. The {@code service.cmRanking} property determines theorder in which plugins are invoked. Lower ranked plugins are called before higher ranked ones. In the event of more than one plugin having the same value of {@code service.cmRanking}, then the Configuration Admin service arbitrarily chooses the order in which they are called.
By convention, plugins with {@code service.cmRanking < 0} or{@code service.cmRanking> 1000} should not make modifications to theproperties.
The Configuration Admin service has the right to hide properties from plugins, or to ignore some or all the changes that they make. This might be done for security reasons. Any such behavior is entirely implementation defined.
A plugin may optionally specify a {@code cm.target} registration propertywhose value is the PID of the Managed Service or Managed Service Factory whose configuration updates the plugin is intended to intercept. The plugin will then only be called with configuration updates that are targeted at the Managed Service or Managed Service Factory with the specified PID. Omitting the {@code cm.target} registration property means that the plugin is calledfor all configuration updates. @author $Id: 36cd6f091c1bb1726305702c57845ba419ca0a49 $


            // Only call the plugin if no cm.target is specified or if it
            // matches the pid of the target service
            String cmTarget = (String) pluginReference.getProperty(CM_TARGET);
            if (cmTarget == null || cmTarget.equals(pid)) {
                ConfigurationPlugin plugin = (ConfigurationPlugin) Activator.bc
                        .getService(pluginReference);
                if (plugin == null) {
                    continue;
                }
                ConfigurationDictionary dictionaryCopy = currentDictionary
                        .createCopyAndRemoveLocation();
                try {
                    plugin.modifyConfiguration(targetServiceReference,
                            dictionaryCopy);
                    if (allowModification && validateDictionary(dictionaryCopy)) {
                        currentDictionary = dictionaryCopy;
                    }
                } catch (Exception exception) {

View Full Code Here


        // call the plugins in order
        for ( int i = 0; i < plugins.length; i++ )
        {
            ServiceReference pluginRef = plugins[i];
            ConfigurationPlugin plugin = ( ConfigurationPlugin ) bundleContext.getService( pluginRef );
            if ( plugin != null )
            {
                try
                {
                    plugin.modifyConfiguration( sr, props );
                }
                catch ( Throwable t )
                {
                    log( LogService.LOG_ERROR, "Unexpected problem calling configuration plugin {0}", new Object[]
                        { toString( pluginRef ), t } );

View Full Code Here


        // call the plugins in order
        for ( int i = 0; i < plugins.length; i++ )
        {
            ServiceReference pluginRef = plugins[i];
            ConfigurationPlugin plugin = ( ConfigurationPlugin ) bundleContext.getService( pluginRef );
            if ( plugin != null )
            {
                try
                {
                    plugin.modifyConfiguration( sr, props );
                }
                catch ( Throwable t )
                {
                    log( LogService.LOG_ERROR, "Unexpected problem calling configuration plugin {0}", new Object[]
                        { toString( pluginRef ), t } );

View Full Code Here

      if (pids != null) {
        String pid = (String) properties.get(Constants.SERVICE_PID);
        if (!Arrays.asList(pids).contains(pid))
          continue;
      }
      ConfigurationPlugin plugin = (ConfigurationPlugin) pluginTracker.getService(references[i]);
      if (plugin != null)
        plugin.modifyConfiguration(managedReference, properties);
    }
  }

View Full Code Here

    final boolean[] receivedEvent = new boolean[] { false };


    // the current implementation of configuration admin seems to be prone to threading errors
    // (especially race conditions where event for updates are cumulated and not propagated properly
    // due to the asynch nature) so this plugin only expects one event really without checking the source
    ConfigurationPlugin cp = new ConfigurationPlugin() {


      public void modifyConfiguration(ServiceReference reference, Dictionary properties) {
        synchronized (monitor) {
          receivedEvent[0] = true;
          monitor.notify();

View Full Code Here

TOP

Related Classes of org.osgi.service.cm.ConfigurationPlugin

org.apache.felix.cm.impl.ConfigurationManager

org.eclipse.equinox.internal.cm.PluginManager

org.knopflerfish.bundle.cm.PluginManager

org.springframework.osgi.iandt.cm.managedproperties.ManagedPropertiesTest

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.