public class BrowserPluginService extends AbstractAction
Modifier and Type | Field and Description |
---|---|
private BrowserExtractorManager |
extractorManager |
actionParamKey, handledActions, httpHeaders, isDefaultAction, replacements, replacementsInitialized, servletModule
engine, initScript, persistentObjects, scriptManager, startScript, stopScript
autoStart, isInitialized, isRunning, logging, loggingModule, moduleManager
Constructor and Description |
---|
BrowserPluginService() |
Modifier and Type | Method and Description |
---|---|
java.util.Collection<Module> |
getDependencies(ModuleManager manager)
Returns all the modules this module depends on.
|
boolean |
handleAction(javax.servlet.http.HttpServletRequest request,
javax.servlet.http.HttpServletResponse response,
ModulesServlet.HttpMethod _method,
java.lang.String _action,
User user)
Handles this action.
|
void |
init(ModuleManager manager,
java.util.HashMap<java.lang.String,java.lang.Object> settings)
Initialises the module.
|
void |
start(ModuleManager manager)
Starts the module.
|
protected java.io.PrintWriter |
startPluginResponse(javax.servlet.http.HttpServletResponse response,
int code,
java.lang.String text) |
void |
stop(ModuleManager manager)
Stops the module.
|
addHandledAction, doReplacements, handleRequest, isHandleAction, setActionParamKey, setHttpHeaders
getScriptEngine
isInitialized, isRunning, requireLogging, toString
private BrowserExtractorManager extractorManager
public void init(ModuleManager manager, java.util.HashMap<java.lang.String,java.lang.Object> settings) throws ModuleException
Module
Initialises the module. After constructor, this is the first method called in the life cycle of a module. It should not perform anything time consuming or anything with notable outside side effects. It should only read the parameters and initialise the module so that it can later be started. Note that a module being initialised doesn't mean that it necessarily will ever be started.
A ModuleException may be thrown if something vital is missing from the parameters or they are not sensible. In some cases you may not want to throw an exception even if vital initialisation information is missing. If, for example, it is possible that the module is initialised in some other way between the init and the start method calls. A ModuleException may also be thrown at the start method if the module is still not initialised.
init
in interface Module
init
in class AbstractAction
manager
- The module manager handling this module. You may keep a
reference to it if needed.ModuleException
public void stop(ModuleManager manager)
Module
stop
in interface Module
stop
in class AbstractAction
manager
- The module manager handling this module.public void start(ModuleManager manager) throws ModuleException
Module
start
in interface Module
start
in class AbstractAction
manager
- The module manager handling this module.ModuleException
public java.util.Collection<Module> getDependencies(ModuleManager manager) throws ModuleException
Module
getDependencies
in interface Module
getDependencies
in class AbstractAction
manager
- The module manager handling this module.ModuleException
protected java.io.PrintWriter startPluginResponse(javax.servlet.http.HttpServletResponse response, int code, java.lang.String text)
public boolean handleAction(javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response, ModulesServlet.HttpMethod _method, java.lang.String _action, User user) throws javax.servlet.ServletException, java.io.IOException, ActionException
AbstractAction
handleAction
in class AbstractAction
request
- The HTTP Request.response
- The HTTP response._method
- The HTTP method of the request._action
- The parsed action id.user
- The logged in user, or null if not applicable.javax.servlet.ServletException
java.io.IOException
ActionException
Copyright 2004-2015 Wandora Team