Skip to Content

Servlet Builds

Last modified by Andrew Lindesay on 2007/06/14 19:56

What is Servlet?

Servlet is part of the J2EE standard and is basically a packaging and interfacing structure for putting applications into a server. It means (theoretically) that you can take your servlet that you have build and put it into a range of different J2EE "servlet containers" and the servlet will run. Here are some servlet containers that may or may not be suitable for your purposes;

There are some existing notes that I have written on building WebObjects applications as servlets and how to deploy this into Tomcat.

It is possible to assemble your WebObjects application into a servlet using the woproject ant tasks. Here we assume that you have setup your project with the eclipse tools and that you have the boiler-plate ant build file already.

License

WebObjects requires a license to run. Create a text file in the top level of your project and copy the license string into this file. It will have the format X-XXX-XXX-XXX-XXX-XXX-XXX-XXX-XXX-XXX wherein you obviously need to replace the X-s with letters and digits.

Servlet Single Directory Deployment

Servlet Single Directory Deployment is referred to as SSDD. The WebObjects 5.2 Release Notes touch on what this entails;

WebObjects 5.1 added support for deploying WebObjects applications in J2EE servlet containers. However, this support still required the presence of the WebObjects deployment runtime on the J2EE server. The new Servlet Single Directory Deployment (SSDD) feature of WebObjects 5.2 removes this requirement. Now, you can deploy a WebObjects application into a single, self-contained directory in a supported J2EE servlet container. The self-contained directory contains the application's .woa and all the frameworks the application requires.

  1. Load the build.xml file up and locate the section called <!-- ssdd target --> - run through the instructions there.
  2. The web.xml file is used to configure the servlet once it is running inside the servlet container. This is build from a template web.xml.template as stated in the header <-- TODO??

You may need to modify the web.xml file for your specific deployment purposes.