Main class used to startup and configure jk. It manages the conf/jk2.properties file
and is the target of JMX proxy.
It implements a policy of save-on-change - whenever a property is changed at
runtime the jk2.properties file will be overriden.
You can edit the config file when tomcat is stoped ( or if you don't use JMX or
other admin tools ).
The format of jk2.properties:
TYPE[.LOCALNAME].PROPERTY_NAME=VALUE
Set a property on the associated component. TYPE will be used to
find the class name and instantiate the component. LOCALNAME allows
multiple instances. In JMX mode, TYPE and LOCALNAME will form the
JMX name ( eventually combined with a 'jk2' component )
NAME=VALUE
Define global properties to be used in ${} substitutions
class.COMPONENT_TYPE=JAVA_CLASS_NAME
Adds a new 'type' of component. We predefine all known types.
Instances are created the first time a component name is found. In addition,
'handler.list' property will override the list of 'default' components that are
loaded automatically.
Note that the properties file is just one (simplistic) way to configure jk. We hope
to see configs based on registry, LDAP, db, etc. ( XML is not necesarily better )
- TYPE[.LOCALNAME].PROPERTY_NAME=VALUE
- Set a property on the associated component. TYPE will be used to
find the class name and instantiate the component. LOCALNAME allows
multiple instances. In JMX mode, TYPE and LOCALNAME will form the
JMX name ( eventually combined with a 'jk2' component )
- NAME=VALUE
- Define global properties to be used in ${} substitutions
- class.COMPONENT_TYPE=JAVA_CLASS_NAME
- Adds a new 'type' of component. We predefine all known types.
Instances are created the first time a component name is found. In addition, 'handler.list' property will override the list of 'default' components that are loaded automatically. Note that the properties file is just one (simplistic) way to configure jk. We hope to see configs based on registry, LDAP, db, etc. ( XML is not necesarily better )