System Requirements

[Return to Index]

The system requirements for using TiniHttpServer 1.0 differ depending on whether you want to just use the distributed server as-is or use it with your own servlets.

Using TiniHttpServer as Distributed

To use TiniHttpServer as distributed, you must have:

A TINI board.
TINI 1.02d firmware installed. TiniHttpServer 1.0 will not run on other versions of the firmware.
The TiniHttpServer software.

Using Your Servlets with TiniHttpServer

If you want to write your own servlets for TINI, you must download and properly install :

All of the above, plus...
Java 2 SDK (Standard Edition) version 1.3 (or version 1.4). This is also known as JDK 1.3 (or JDK 1.4)
IMPORTANT: Version 1.2 will not work. See below for an explanation why.
The class files from the Java Servlet Specification 2.2 of the JSDK. You do not need to download an entire implementation, just the class files (i.e. servlet.jar) from the specification. The build process will abort with a (hopefully) useful error message if it detects JSDK version 2.3.
Ant version 1.4.1. The provided build environment is based on Ant. Ant is an open source, cross platform build tool written in Java. The supplied build environment has been tested on Windows NT 4.0 and SuSE Linux 7.0.
TiniAnt 1.2.0. TiniAnt is a free plug-in for Ant written by Sean Kelly that integrates the TINI build process into Ant.

Using TiniHttpServer on non-TINI Platforms

If you want to use TiniHttpServer on non-TINI platforms, you must download and properly install:

All of the above, plus...
Either one of the following 1-Wire API for Java releases:
- 1.00 Beta Release (Recommended)
  
  OR
- 0.01 Final Release
Technically, TiniHttpServer only requires this for 1-Wire support. TiniHttpServer's default build option for non-TINI systems, however, currently includes 1-Wire servlets causing this to be required. If you remove all 1-Wire related servlets from the build process, the 1-Wire API for Java is not required.

Why JDK 1.2 Does Not Work

When Ant runs the Java compiler (javac), it always uses the -sourcepath switch. It seems that when a source file depends on a pre-existing class file which in turn depends on the file being compiled and the -sourcepath switch is used, the javac from (Sun's) JDK 1.2 (for Windows NT) will fail with an error message similar to "Foo.java: class Foo is already defined in file Foo.java". At least that's my theory for why the error message occurs. This problem does not occur with JDK 1.3. If you can shed some light on this, please drop me a line.