| Default implementation of the application initializer interface.
Supported configuration parameters:
- org.java.plugin.boot.applicationPlugin
- ID of plug-in to start. There is no default value for this parameter.
In common scenario, this is the only parameter that you must provide.
- org.java.plugin.boot.integrityCheckMode
- Regulates how to check plug-ins integrity when running JPF. Possible
values:
full, light, off. The
default value is full.
- org.java.plugin.boot.pluginsCollector
- Plug-ins location collector class, for details see
org.java.plugin.boot.PluginsCollector . Default is
org.java.plugin.boot.DefaultPluginsCollector .
- org.java.plugin.boot.pluginsWhiteList
- Location of the file with plug-in identifiers that should be only
accepted by this application initializer. This is optional parameter.
- org.java.plugin.boot.pluginsBlackList
- Location of the file with plug-in identifiers that should not be
accepted by this application initializer. This is optional parameter.
Note that all given configuration parameters are passed to
org.java.plugin.ObjectFactory.newInstance(ExtendedProperties) when running JPF (see bellow). This allows you to configure JPF precisely.
Black and white lists of plug-ins
In some situations you may want to temporary exclude some of your plug-ins
from the application scope. This may be achieved with help of while and black
lists - simple plain text files that contain lists of plug-in identifiers to
be included/excluded from the application. Each identifies should be in
separate line. You may provide unique plug-in ID also.
What is application plug-in?
When application starts, the
org.java.plugin.boot.Boot.main(String[]) method executed calling
DefaultApplicationInitializer.initApplication(BootErrorHandler,String[]) to get initialized
instance of
org.java.plugin.boot.Application (or
org.java.plugin.boot.ServiceApplication ) class. The method
DefaultApplicationInitializer.initApplication(BootErrorHandler,String[]) in this implementation
scans plug-in repositories to collect all available plug-in files and folders
(using special class that can be customized),
instantiates JPF and publishes all discovered plug-ins. After that it asks
org.java.plugin.PluginManager for an Application Plug-in with
ID provided as configuration parameter. Returned class instance is expected
to be of type
org.java.plugin.boot.ApplicationPlugin and it's method
org.java.plugin.boot.ApplicationPlugin.initApplication(ExtendedPropertiesString[]) called.
To the mentioned initApplication method passed a subset of
configuration properties whose names start with application plug-in ID
followed with dot character '.' (see
org.java.plugin.util.ExtendedProperties.getSubset(String) for
details).
As a result of the described procedure, the Boot get instance of
org.java.plugin.boot.Application interface, so it can start
application calling
org.java.plugin.boot.Application.startApplication method.
version:
$Id$ | 