JWarp Core Components

Context and Service Runtime Engine

• The main component is the context manager, which is implemented as singleton.
• After loading an XML configuration the context manager will consist of one or more service contexts.
• Each service context has its own service manager who is responsible for loading and reloading the services and other management tasks.
• Running within each service manager are several services. All services implement a common runtime interface.
• Each context furthermore contains a resolver. A resolver is a lookup component for handling various kinds of system resources. The resolver itself can also be easily implemented via JNDI, thus making the JWarp runtime environment available outside. All services that inherit from the org.jwarp.service.AService class automatically register under /services/<servicetype>/<servicename>. Some services, such as the connection pool service and the cache service, additionally register their cache/pool instances in a subtree.

If these basic components are understood, then the architecture of the way JWarp functions should be easy to grasp. To illustrate the connections between the components, look at the following architectural overview: