Comment #4 by h.iverson:
Here is what happens with ConnectionManager. Patch attached is a start
of what SHOULD
happen. Basically I've start decoupling standalone functionality from
ConnectionManager class and moving it into ServerStarter and EmbeddedHttpBindServlet.
ServerStarter.main() loads Jive's classloader and creates a new
instance of
ConnectionManager
The constructor of ConnectionManager throws an IllegalStateException if
it has been
created before. Otherwise it calls ConnectionManager.start()
ConnectionManager.start() calls ConnectionManager.inititalize() and then
ConnectionManager.startModules() if it is not in "setupMode".
ConnectionManager.inititalize() calls ConnectionManager.locateHome(),
sets name and
serverName properties and adds a shutdown hook if ConnectionManager.isStandalone()
returns true. Sets "setupMode" to false if serverName is not null.
ConnectionManager.locateHome() checks for managerHome property, then manager_init.xml
from classpath to load that property, them home directory, then dies. Calls
ConnectionManager.verifyHome() on any path it finds.
ConnectionManager.verifyHome() ensures that a config file
(conf_manager.xml) exists
within directory
ConnectionManager.isStandalone() returns true if ServerStarter exists
in the class
path. false otherwise.
ConnectionManager.startModules() starts standard, SSL and HTTP binding.
ConnectionManager.startHttpBindServlet() creates a new HttpBindManager
and calls
HttpBindManager.startup()
HttpBindManager.startup() creates Jettty connectors, adds a handler
created by
HttpBindManager.createServletHandler(), and calls server.start()
HttpBindManager.createServletHandler() creates a new HttpBindServlet
and maps the
handler to /
Attachments:
connectionmanager.patch 7.6 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings