Examples of PluginManager

cero.plugin.PluginManager
This class gives you acces to all the plugins you might want to use. It is a singleton, and you must *NOT* try to instanciate it, as it will throw an Exception if you do. Use getInstance instead to get a reference on the PluginManager. @author Telem
ch.rakudave.jnetmap.plugins.PluginManager
com.ecyrd.jspwiki.plugin.PluginManager
Manages plugin classes. There exists a single instance of PluginManager per each instance of WikiEngine, that is, each JSPWiki instance.
A plugin is defined to have three parts:
1. The plugin class
2. The plugin parameters
3. The plugin body
For example, in the following line of code:
```
 [{INSERT com.ecyrd.jspwiki.plugin.FunnyPlugin  foo='bar' blob='goo' abcdefghijklmnopqrstuvw 01234567890}] 
```
The plugin class is "com.ecyrd.jspwiki.plugin.FunnyPlugin", the parameters are "foo" and "blob" (having values "bar" and "goo", respectively), and the plugin body is then "abcdefghijklmnopqrstuvw\n01234567890". The plugin body is accessible via a special parameter called "_body".
If the parameter "debug" is set to "true" for the plugin, JSPWiki will output debugging information directly to the page if there is an exception.
The class name can be shortened, and marked without the package. For example, "FunnyPlugin" would be expanded to "com.ecyrd.jspwiki.plugin.FunnyPlugin" automatically. It is also possible to define other packages, by setting the "jspwiki.plugin.searchPath" property. See the included jspwiki.properties file for examples.
Even though the nominal way of writing the plugin is
```
 [{INSERT pluginclass WHERE param1=value1...}], 
```
it is possible to shorten this quite a lot, by skipping the INSERT, and WHERE words, and dropping the package name. For example:
```
 [{INSERT com.ecyrd.jspwiki.plugin.Counter WHERE name='foo'}] 
```
is the same as
```
 [{Counter name='foo'}] 
```
Plugin property files

Since 2.3.25 you can also define a generic plugin XML properties file per each JAR file.
```
   Janne Jalkanen  foo.css code   Janne Jalkanen   
```
Plugin lifecycle

Plugin can implement multiple interfaces to let JSPWiki know at which stages they should be invoked:
- InitializablePlugin: If your plugin implements this interface, the initialize()-method is called once for this class before any actual execute() methods are called. You should use the initialize() for e.g. precalculating things. But notice that this method is really called only once during the entire WikiEngine lifetime. The InitializablePlugin is available from 2.5.30 onwards.
- ParserStagePlugin: If you implement this interface, the executeParse() method is called when JSPWiki is forming the DOM tree. You will receive an incomplete DOM tree, as well as the regular parameters. However, since JSPWiki caches the DOM tree to speed up later places, which means that whatever this method returns would be irrelevant. You can do some DOM tree manipulation, though. The ParserStagePlugin is available from 2.5.30 onwards.
- WikiPlugin: The regular kind of plugin which is executed at every rendering stage. Each new page load is guaranteed to invoke the plugin, unlike with the ParserStagePlugins.
@since 1.6.1
com.eteks.sweethome3d.plugin.PluginManager
Sweet Home 3D plug-ins manager. @author Emmanuel Puybaret
com.gitblit.manager.PluginManager
The plugin manager maintains the lifecycle of plugins. It is exposed as Dagger bean. The extension consumers supposed to retrieve plugin manager from the Dagger DI and retrieve extensions provided by active plugins. @author David Ostrovsky @author James Moger
com.valhalla.pluginmanager.PluginManager
Allows the user to download, install, and upgrade plugins all from within the application that the plugins are used in @author Adam Olsen @version 1.0
com.volantis.osgi.cm.plugin.PluginManager
Manages {@link ConfigurationPlugin} instances.
Warning: This is a facade provided for use by user code, not for implementation by user code. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.
@mock.generate
de.kilobyte22.app.kibibyte.plugin.PluginManager
Created with IntelliJ IDEA. User: Stephan Date: 07.03.13 Time: 07:59 @author Stephan @copyright Copyright 2013 Stephan
de.sciss.meloncillo.plugin.PlugInManager
devplugin.PluginManager
The PluginManager provides some useful methods for a plugin. More methods may follow in future versions. @author Martin Oberhauser
fbench.plugin.PluginManager
PluginManager for FBench. General Purpose of this class is to provide easier and organised access to various of FBench Plugin components. @author Jason Park, Cheng Pang @version 20070530/JP
freenet.pluginmanager.PluginManager
hudson.PluginManager
Manages {@link PluginWrapper}s. @author Kohsuke Kawaguchi
kameleon.plugin.PlugInManager
Utility class handling the plug-ins.
Provides methods to manage (add, load and remove) different plug-ins (analyzers as well as generators). @author Schnell Michaël @version 1.0
net.sourceforge.cruisecontrol.utilities.PluginManager
net.sourceforge.squirrel_sql.client.plugin.PluginManager
Manages plugins for the application. @author Colin Bell
net.xeoh.plugins.base.PluginManager
This is your entry point to and the heart of JSPF. The plugin manager keeps track of all registed plugins and gives you methods to add and query them. You cannot instantiate the PluginManager directly, instead you

create this class the first time by a call to {@link PluginManagerFactory}.createPluginManager()

Afterwards you probably want to add some of your own plugins. During the lifetime of your application there should only be one PluginManager. The PluginManager does not have to be passed to the inside of your plugins, instead, they can request it by the @ {@link InjectPlugin}annotation (i.e, create a field 'public PluginManager manager' and add the annotation).

There are also a number of default plugins you can retrieve right away (without calling addPluginsFrom() explicitly.). These are:
- {@link PluginConfiguration} - enables you to get and set config options
- {@link PluginInformation} - provides meta information about plugins
- {@link InformationBroker} - supports information exchange between plugins while keeping them decoupled
In addition (and after loading the specific plugin) you can also retrieve a RemoteAPI.

The following configuration sub-keys are usually known for this class (see {@link PluginConfiguration}, keys must be set before createPluginManager() is being called, i.e., set in the {@link JSPFProperties} object!):
- cache.enabled - Specifies if the known plugins should be cached. Specify either {true, false}.
- cache.mode - If we should use strong caching (slow but more accurate) or weak (much faster). Specify either {stong, weak}.
- cache.file - Cache file to use. Specify any relative or absolute file path, file will be created / overwritten.
- classpath.filter.default.enabled - If Java default classpaths (e.g., jre/lib/*) should be filtered. Specify either {true, false}. Might not work on all platforms as expected.
- classpath.filter.default.pattern - Specify what to filter in addition to default classpaths. Specify a list of ';' separated tokens, e.g., "jdk/lib;jre/lib". Will be matched against URL representations, so all \\ will be converted to / (and ' ' might become %20, ...).
- logging.level - Either {OFF, FINEST, FINER, FINE, INFO, WARNING, ALL}. Specifies what to log on the console.
@see PluginManagerUtil @author Ralf Biedert
org.aavso.tools.vstar.ui.dialog.plugin.manager.PluginManager
This class manages plug-in installation, deletion, and update.
org.apache.logging.log4j.core.config.plugins.PluginManager
Loads and manages all the plugins.
org.apache.logging.log4j.core.config.plugins.util.PluginManager
Loads and manages all the plugins.
org.apache.maven.plugin.PluginManager
@author Jason van Zyl @version $Id: PluginManager.java 495147 2007-01-11 07:47:53Z jvanzyl $
org.apache.qpid.server.plugins.PluginManager
Provides access to pluggable elements, such as exchanges
org.apache.roller.business.PluginManager
Plugin management for business layer and more generally applied plugins.
org.apache.roller.model.PluginManager
Manages Roller plugins.
org.apache.roller.weblogger.business.plugins.PluginManager
Plugin management for business layer and more generally applied plugins.
org.apache.wiki.api.engine.PluginManager
org.apache.wiki.plugin.PluginManager
Manages plugin classes. There exists a single instance of PluginManager per each instance of WikiEngine, that is, each JSPWiki instance.
A plugin is defined to have three parts:
1. The plugin class
2. The plugin parameters
3. The plugin body
For example, in the following line of code:
```
 [{INSERT org.apache.wiki.plugin.FunnyPlugin  foo='bar' blob='goo' abcdefghijklmnopqrstuvw 01234567890}] 
```
The plugin class is "org.apache.wiki.plugin.FunnyPlugin", the parameters are "foo" and "blob" (having values "bar" and "goo", respectively), and the plugin body is then "abcdefghijklmnopqrstuvw\n01234567890". The plugin body is accessible via a special parameter called "_body".
If the parameter "debug" is set to "true" for the plugin, JSPWiki will output debugging information directly to the page if there is an exception.
The class name can be shortened, and marked without the package. For example, "FunnyPlugin" would be expanded to "org.apache.wiki.plugin.FunnyPlugin" automatically. It is also possible to define other packages, by setting the "jspwiki.plugin.searchPath" property. See the included jspwiki.properties file for examples.
Even though the nominal way of writing the plugin is
```
 [{INSERT pluginclass WHERE param1=value1...}], 
```
it is possible to shorten this quite a lot, by skipping the INSERT, and WHERE words, and dropping the package name. For example:
```
 [{INSERT org.apache.wiki.plugin.Counter WHERE name='foo'}] 
```
is the same as
```
 [{Counter name='foo'}] 
```
Plugin property files

Since 2.3.25 you can also define a generic plugin XML properties file per each JAR file.
```
   Janne Jalkanen  foo.css code   Janne Jalkanen   
```
Plugin lifecycle

Plugin can implement multiple interfaces to let JSPWiki know at which stages they should be invoked:
- InitializablePlugin: If your plugin implements this interface, the initialize()-method is called once for this class before any actual execute() methods are called. You should use the initialize() for e.g. precalculating things. But notice that this method is really called only once during the entire WikiEngine lifetime. The InitializablePlugin is available from 2.5.30 onwards.
- ParserStagePlugin: If you implement this interface, the executeParse() method is called when JSPWiki is forming the DOM tree. You will receive an incomplete DOM tree, as well as the regular parameters. However, since JSPWiki caches the DOM tree to speed up later places, which means that whatever this method returns would be irrelevant. You can do some DOM tree manipulation, though. The ParserStagePlugin is available from 2.5.30 onwards.
- WikiPlugin: The regular kind of plugin which is executed at every rendering stage. Each new page load is guaranteed to invoke the plugin, unlike with the ParserStagePlugins.
@since 1.6.1 @deprecated will be removed in 2.10 scope. Consider using {@link DefaultPluginManager} instead
org.b3log.latke.plugin.PluginManager
Plugin loader. @author Liang Ding @version 1.0.1.0, Dec 3, 2011
org.bukkit.plugin.PluginManager
Handles all plugin management from the Server
org.datanucleus.plugin.PluginManager
Manages the registry of Extensions and Extension Points.
org.dmd.dmp.server.servlet.base.PluginManager
The PluginManager reads a plugin configuration and loads and instantiates the plugins specified. Certain plugin roles are required in order for the application to function properly. These roles include:
- Cache - which provides centralized access to named objects and allows for CRUDE operations - Create, Read, Update, Delete and Events associated with the objects it manages. A cache implementation MUST be Runnable in order to allow for proper sequencing of operations and events.
- SecurityManager - provides user authentication and session management.
org.elasticsearch.plugins.PluginManager
@author kimchy (shay.banon)
org.gradle.api.internal.plugins.PluginManager
org.gudy.azureus2.plugins.PluginManager
This class allows Azureus to be started as an embedded component and also allows plugins to be dynamically registered @author parg
org.hotswap.agent.config.PluginManager
The main agent plugin manager, well known singleton controller. @author Jiri Bubnik
org.java.plugin.PluginManager
org.jivesoftware.openfire.container.PluginManager
Loads and manages plugins. The plugins directory is monitored for any new plugins, and they are dynamically loaded.
An instance of this class can be obtained using:
XMPPServer.getInstance().getPluginManager() @author Matt Tucker @see Plugin @see org.jivesoftware.openfire.XMPPServer#getPluginManager()
org.jnode.plugin.PluginManager
Interface of manager of all plugins in the system. @author Ewout Prangsma (epr@users.sourceforge.net)
org.joget.plugin.base.PluginManager
org.jpox.plugin.PluginManager
Manages the registry of Extensions and Extension Points. @version $Revision: 1.35 $
org.objectweb.celtix.plugins.PluginManager
Provides methods for registering, unregistering and obtaining plugin objects.
org.rhq.core.pc.plugin.PluginManager
This container service will load in all plugins that can be found and will maintain the complete set of {@link #getMetadataManager() metadata} found in all plugin descriptors from all loaded plugins. You can obtain aloaded plugin's {@link PluginEnvironment environment}, including its classloader, from this object as well - see {@link #getPlugin(String)}. @author Greg Hinkle @author Jason Dobies @author John Mazzitelli
org.socialmusicdiscovery.server.business.logic.PluginManager
The plugin manager is a singleton object which manage all currently running plugins and provides functions to start/stop all enabled plugins or an individual specific plugin
org.tuba.plugins.util.PluginManager
org.xmlBlaster.authentication.plugins.PluginManager
Title: PluginManager Description: Loads security plugin @author W. Kleinertz (wkl) @version 1.0
pl.net.bluesoft.rnd.processtool.plugins.PluginManager
@author tlipski@bluesoft.net.pl
ro.fortsoft.pf4j.PluginManager
Provides the functionality for plugin management such as load, start and stop the plugins. @author Decebal Suiu
syn3d.base.PluginManager
This is a central repository for Syn3D plugins @author nicolas brodu

Examples of org.apache.wiki.api.engine.PluginManager


    private String executePlugin( String plugin, String args, String body )
        throws PluginException, IOException
    {
        WikiEngine engine = m_wikiContext.getEngine();
        PluginManager pm  = engine.getPluginManager();


        m_evaluated = true;


        Map<String, String> argmap = pm.parseArgs( args );
        
        if( body != null ) 
        {
            argmap.put( "_body", body );
        }


        String result = pm.execute( m_wikiContext, plugin, argmap );


        return result;        
    }

View Full Code Here

Examples of org.apache.wiki.plugin.PluginManager


    testEngine.saveText( "TestPage01", "Some Text for testing 01" );
    testEngine.saveText( "TestPage02", "Some Text for testing 02" );
    testEngine.saveText( "TestPage03", "Some Text for testing 03" );


    manager = new PluginManager( testEngine, props );
}

View Full Code Here

Examples of org.b3log.latke.plugin.PluginManager

     */
    public JSONObject setPluginStatus(final String pluginId, final String status) {
        final Map<String, String> langs =
                langPropsService.getAll(Latkes.getLocale());


        final PluginManager pluginManager = PluginManager.getInstance();
        final List<AbstractPlugin> plugins = pluginManager.getPlugins();


        final JSONObject ret = new JSONObject();


        for (final AbstractPlugin plugin : plugins) {
            if (plugin.getId().equals(pluginId)) {
                final Transaction transaction =
                        pluginRepository.beginTransaction();
                try {
                    plugin.setStatus(PluginStatus.valueOf(status));


                    pluginRepository.update(pluginId, plugin.toJSONObject());


                    transaction.commit();


                    pluginManager.update(plugin);


                    ret.put(Keys.STATUS_CODE, true);
                    ret.put(Keys.MSG, langs.get("setSuccLabel"));


                    return ret;

View Full Code Here

Examples of org.bukkit.plugin.PluginManager

      this.getServer().getPluginManager().disablePlugin(this);
      return;
    }


    // Register events
    PluginManager pm = this.getServer().getPluginManager();
    pm.registerEvents(this.playerListener, this);
    pm.registerEvents(this.entityListener, this);
    pm.registerEvents(this.blockListener, this);
    pm.registerEvents(this.serverListener, this);
    if (pm.isPluginEnabled("TagAPI")) {
      try {
        Class.forName("org.kitteh.tag.TagAPI");
        pm.registerEvents(new WarTagListener(), this);
        this.tagServer = true;
      } catch (ClassNotFoundException e) {
        this.tagServer = false;
      }
    }

View Full Code Here

Examples of org.bukkit.plugin.PluginManager

        // Bind the /ma, /mobarena commands to MACommands.
        commandHandler = new CommandHandler(this);
        getCommand("ma").setExecutor(commandHandler);
        getCommand("mobarena").setExecutor(commandHandler);
        
        PluginManager pm = this.getServer().getPluginManager();
        pm.registerEvents(new MAGlobalListener(this, arenaMaster), this);
    }

View Full Code Here

Examples of org.bukkit.plugin.PluginManager

    public void saveConfig() {
        plugin.saveConfig();
    }


    private Permission registerPermission(String permString, PermissionDefault value) {
        PluginManager pm = plugin.getServer().getPluginManager();


        Permission perm = pm.getPermission(permString);
        if (perm == null) {
            perm = new Permission(permString);
            perm.setDefault(value);
            pm.addPermission(perm);
        }
        return perm;
    }

View Full Code Here

Examples of org.bukkit.plugin.PluginManager

        worlds.add(s.toLowerCase());
      }
    }
    debug = config.getBoolean("Plugin.Debug", false);


    PluginManager pm = getServer().getPluginManager();
    pm.registerEvents(new MobListener(this), this);
    pm.registerEvents(new TomeListener(this), this);
    pm.registerEvents(new SocketListener(this), this);
    pm.registerEvents(new EffectsListener(this), this);
    pm.registerEvents(new SetListener(this), this);


    getCommand("diablodrops").setExecutor(new DiabloDropCommand(this));


    ShapelessRecipe re = new ShapelessRecipe(new IdentifyTome());
    re.addIngredient(3, Material.BOOK);

View Full Code Here

Examples of org.datanucleus.plugin.PluginManager

    public void initialiseTypes(StoreSchemaHandler handler, ManagedConnection mconn)
    {
        // Initialise the mappings available. Load all possible, and remove unsupported for this datastore
        RDBMSStoreManager storeMgr = (RDBMSStoreManager)handler.getStoreManager();
        ClassLoaderResolver clr = storeMgr.getNucleusContext().getClassLoaderResolver(null);
        PluginManager pluginMgr = storeMgr.getNucleusContext().getPluginManager();
        MappingManager mapMgr = storeMgr.getMappingManager();
        mapMgr.loadDatastoreMapping(pluginMgr, clr, getVendorID());


        // Load the types from plugin(s)
        handler.getSchemaData(mconn.getConnection(), "types", null);

View Full Code Here

Examples of org.datanucleus.plugin.PluginManager

    public SQLExpressionFactory(RDBMSStoreManager storeMgr)
    {
        this.storeMgr = storeMgr;
        this.clr = storeMgr.getNucleusContext().getClassLoaderResolver(null);


        PluginManager pluginMgr = storeMgr.getNucleusContext().getPluginManager();
        ConfigurationElement[] methodElems = 
            pluginMgr.getConfigurationElementsForExtension("org.datanucleus.store.rdbms.sql_method", null, null);
        if (methodElems != null)
        {
            for (int i=0;i<methodElems.length;i++)
            {
                String datastoreName = methodElems[i].getAttribute("datastore");
                String className = methodElems[i].getAttribute("class");
                String methodName = methodElems[i].getAttribute("method").trim();
                String sqlMethodName = methodElems[i].getAttribute("evaluator").trim();


                String key = getSQLMethodKey(datastoreName, className, methodName);
                methodClassByDatastoreMethodName.put(key, sqlMethodName);
            }
        }


        ConfigurationElement[] operationElems = 
            pluginMgr.getConfigurationElementsForExtension("org.datanucleus.store.rdbms.sql_operation", null, null);
        if (operationElems != null)
        {
            for (int i=0;i<operationElems.length;i++)
            {
                String datastoreName = operationElems[i].getAttribute("datastore");

View Full Code Here

Examples of org.datanucleus.plugin.PluginManager

    protected void setUp() throws Exception
    {
        ClassLoaderResolver clr = new JDOClassLoaderResolver();
        Properties props = new Properties();
        props.setProperty("bundle-check-action", "EXCEPTION");
        PluginManager pluginMgr = new PluginManager(null, clr, props);


        typeMgr = new TypeManager(null, pluginMgr, clr);
    }

View Full Code Here

0 1 2 3 4 5 6 7 8

TOP

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.

Examples of PluginManager

Plugin property files

Plugin lifecycle

Plugin property files

Plugin lifecycle

Examples of org.apache.wiki.api.engine.PluginManager

Examples of org.apache.wiki.plugin.PluginManager

Examples of org.b3log.latke.plugin.PluginManager

Examples of org.bukkit.plugin.PluginManager

Examples of org.bukkit.plugin.PluginManager

Examples of org.bukkit.plugin.PluginManager

Examples of org.bukkit.plugin.PluginManager

Examples of org.datanucleus.plugin.PluginManager

Examples of org.datanucleus.plugin.PluginManager

Examples of org.datanucleus.plugin.PluginManager