Jetty - Java HTTP Servlet Server Files

The JettyPhoenix library provides a simple mechanism to provide access to
phoenix services to servlets within a web servlet using the Jetty web
server. If you are not familiar with the Phoenix platform the url is
http://avalon.apache.org
Avalon is an application server framework and Phoenix is an implementation
of the Avalon framework.

For those who do not know what Jetty is please view their web site, the url is
http://www.mortbay.org

The basic idea behind this port is to make the web server operate as a component
service. The service does not support the deployment of war files, the idea
is that the sar file replaces the war file with the difference that the web
access is just a component of the application.

The service supports ssl, http, and ajp connectors as well as support
for the web.xml configuration file to configure the servlets.

The java docs contain information for configuring the service. This note
provides some basic pointers on how the service works.

To gain access to the service manager get the session object and then
get the attribute WebServer.SERVICE_MANAGER, this technique is shown
in the test package where a sample servlet and service is provided.

It is also possible to access the phoenix logger using WebService.LOGGER.

I developed this library in order to support the needs I have for my
own developments, as such I have only made use of production versions
of the components, I know that there have been some changes to some
of the phoenix stuff, especially with respect to the use of qdox, which
I believe is no longer the standard? Anyhow, to simplify things, here is
a list of packages I have used in order to build the source code:
Phoenix-4.0.2/3
Jetty-4.1.x/4.2.x

For generating out the dox and sar file the following libraries are required:
qdox-1.0.jar
phoenix-client.jar
phoenix-metagenerate.jar

There may be some other jars required for the tools depending on your version
of the JDK, I use J2SDK 1.4. I do know that this also works with J2SDK 1.3.

The distribution contains a sample build.xml file that is capable of
building the source code. The compile project is set to use the J2SDK 1.4
change this if you intend using a different version. Also the build file
sets up the directories where the dependent libraries can be found.
This will need to be adjusted to reflect where you store your libraries.

Should you have any questions or problems you are welcome to contact me
at hhenson@aosl.co.za, I can usually reasonably quickly.

Regards

Howard Henson