To use Java Server, you need a server environment (to run the server itself) as well as a client environment (from which to run administrative tools).
To run the server, you need a Java runtime environment that conforms with the JDK 1.1 FCS interfaces in order to run Java Server Beta. For many platforms, you can download a version from java.sun.com.
Note that on UNIX, you will probably want some special support to automatically run Java Server as the default web server, and to run it as some user other than "root". At this time, we provide this support only for Solaris SPARC platforms. However, we do provide Posix-compatible sources for the native code needed to provide this functionality on other UNIXes.
Java Server is not currently supported on the Macintosh for lack of JDK 1.1 support on that platform. Until JDK 1.1 is available, Macintosh will only run the Alpha2 version of the Java Server.
The administration applet may not work on all web browsers. It depends on the browser being JDK 1.0.2 compatible (which most browsers are). For the Beta release, JDK 1.1 compatible browsers will not work.
Current versions of Netscape Navigator (3.0), Microsoft Internet Explorer (3.0), and 1.0.2 AppletViewer are known to work. You may not be able to use the administrative tools to administer Java Server if you use older web browsers.
File.renameTo() has different semantics on Solaris and Win32. This routine is a thin veneer over the rename() call in the C library. On Win32, rename() is defined such that it is an error if the destination file exists. On Solaris, the destination file can exist and rename() has the affect of unlinking it.
Counter Servlet doesn't run on the win32 platform.
When running the Java Web Server on a read only file system, log files are attempted to be created even though the log level is 0.
InvokerServlet doesn't set the path information variable, PATH_INFO, when servlets are loaded through the invoker as /servlet alias.
The path, $HTTPD_HOME/servlets, was included in the CLASSPATH of the java-server.startup script which wouldn't allow automatic reloading of servlets when the script was executed.
When making a change on any screen and going to another section and with the cursor is left at the selection point, the dialog boxes will fill up the task bar.
Virtual hosting was hosed due to a bug in the header parsing code.
The FingerServlet was writing the finger request to the http client socket which has now been corrected to write to the correct socket with a timeout added in.
SSIncludeServlet was fixed to read from a buffered stream which would avoid major performance problems.
If input stream has already been read, it returns null from getParameterNames() instead of throwing an exception from IllegalArgumentException(().
Content length of form request structure needs to be set whether keep alive was requested by the client.
Using a double slash to access a URL will bypass all http authentication mechanisms. For example: http://localhost:8080//protected.html will show the protected page without a request for login.
There is a list of known bugs and their workarounds. Please look at these (on the Java Server web site) before you report a bug. The list will be updated as problems are discovered.
There is a list of frequently asked questions, which you should consult to learn about parts of Java Server, including particularly the Java Server programming interfaces.
http://Server_Host_Name:9090)
For a high-level overview of servlets, see the Beta version of the Servlet API White Paper.
http://www.javasoft.com.
Top
java-server-feedback@java.sun.com