From OpenNMS

Contents 1 Class and method naming 1.1 Class naming 1.2 Method naming 2 OpenNMS daemons 2.1 Other JMX services 2.1.1 XSLTProcessor 2.1.2 HttpAdaptor 2.1.3 HttpAdaptorMgmt 2.2 Other JMX stuff 2.2.1 FastExit 3 Other components 3.1 bootstrap 3.2 install 3.3 web

Class and method naming

Class naming

Ends in in Case 

This indicates a base class

Ends in Manager 

Ends in Factory 

Ends in Test 

Starts with Mock

Ends in Config

Method naming

Starts with test 

OpenNMS daemons

See the Daemons page.

Other JMX services

XSLTProcessor

HttpAdaptor

HttpAdaptorMgmt

Other JMX stuff

FastExit

As of 2006-04-14, this has been renamed to Manager in the unstable branch to better reflect its function.

Other components

bootstrap

The bootstrap loader for the OpenNMS daemon. This sets up the huge class path of JARs that OpenNMS needs, along with a few properties and it keeps the command-line from being three miles long (yeah, we can set an environment variable to do this, but wait... there's more!). It will help us out to eventually run on non-Unix platforms. In fact, now, if you have a standard OpenNMS install, you can start up OpenNMS by doing "java -jar /path/to/opennms_bootstrap.jar", and the bootstrap will figure out where the OpenNMS bits are relative to the JAR file. Cool, eh? I thought so.

install

Our installer. Sets up the database and the web app. Do leave home without it.

web

The webUI is the web interface that the end user interacts with. Early in 2005 Matt and Mike began setting up some testing using jWebUnit and HttpUnit. There are some tests done for the user manipulation pages and a base class for some common components of a web page. As development continues, spring will be used.