public class JettyServerComponent extends java.lang.Object implements ManagementComponent
You must provide the jetty config file in the bootstrap.properties file for a Jetty instance to startup.
See the Jetty Guide for more information on configuration options.
For adding webapps to the server the jettyWebappBase parameter can be used.
Modifier and Type | Field and Description |
---|---|
static java.lang.String[] |
ATTR_BOOTSTRAP_KEYS |
static java.lang.String |
ATTR_JMX_ADAPTER_UID |
static java.lang.String |
ATTR_JMX_SERVICE_URL |
static java.lang.String |
DEFAULT_JETTY_PORT |
Constructor and Description |
---|
JettyServerComponent() |
Modifier and Type | Method and Description |
---|---|
void |
destroy()
Destroy the management component making it require re-initialisation.
|
void |
init(java.util.Properties properties)
Initialise the management component.
|
void |
setClassLoader(java.lang.ClassLoader classLoader) |
void |
start()
Had to do some tricks for proper classloading.
|
void |
stop()
Stop the management component.
|
public static final java.lang.String DEFAULT_JETTY_PORT
public static final java.lang.String ATTR_JMX_SERVICE_URL
public static final java.lang.String ATTR_JMX_ADAPTER_UID
public static final java.lang.String[] ATTR_BOOTSTRAP_KEYS
public void setClassLoader(java.lang.ClassLoader classLoader)
setClassLoader
in interface ManagementComponent
public void init(java.util.Properties properties) throws java.lang.Exception
ManagementComponent
init
in interface ManagementComponent
properties
- configuration properties that have been built during bootstrap.java.lang.Exception
- if initialisation fails.public void start() throws java.lang.Exception
start
in interface ManagementComponent
java.lang.Exception
public void stop()
ManagementComponent
stop
in interface ManagementComponent
public void destroy() throws java.lang.Exception
ManagementComponent
destroy
in interface ManagementComponent
java.lang.Exception