WebApp Plug-in Release Notes

Release 0.9.0 Beta
January 20, 2003

This software is OSI Certified Open Source Software.
OSI Certified is a certification mark of the Open Source Initiative.

1. Target Operating Environments
2. Compatibility with Previous Release
3. Known Issues
   3.1 WebApp Plug-in
   3.2 Tomcat Adapter
   3.3 Jetty Adapter

1. Target Operating Environments

The WebApp Plug-in has been tested on the following Java 2 Platform implementations:

Operating system	Processor architecture	Java 2 Platforms
Microsoft® Windows®	Intel x86	Sun Java 2 SDK, Standard Edition, version 1.3.1 for Microsoft Windows
		Sun Java 2 SDK, Standard Edition, version 1.4 for Microsoft Windows
Linux	Intel x86	Sun Java 2 SDK, Standard Edition, version 1.3.1 for Linux x86
		Sun Java 2 SDK, Standard Edition, version 1.4 for Linux x86

The following table describes the combinations of operating system and Java 2 Platform used when testing the WebApp Plug-in configurations. The status column indicates the level of testing: "Primary" means a full tested configuration; "Secondary" means a configuration which is only lightly tested; "Untested" means a configuration that has received no testing, but which should work. Note that the Linux GTK configuration is considered early access for the 2.0 release; it has been tested, but is not product quality in this release [Eclipse.org].

Window system	Java 2 Platform (see above table)	Operating Environment	Eclipse Version	Testing Status
Win32	Windows on Intel x86	Windows 2000	2.0	Primary
			2.0.1	Primary
			2.0.2	Untested
		Windows XP	2.0	Untested
			2.0.1
			2.0.2
		Windows ME	2.0	Untested
			2.0.1
			2.0.2
		Windows 98SE	2.0	Untested
			2.0.1
			2.0.2
		Windows NT	2.0	Secondary
			2.0.1	Untested
			2.0.2	Untested
Motif	Linux on Intel x86	RedHat Linux 7.2 x86	2.0	Untested
			2.0.1
			2.0.2
		SuSE Linux 7.3 x86	2.0	Untested
			2.0.1
			2.0.2
		Other Linux; kernel version 2.4.7, and XFree86 version 4.1.0	2.0	Untested
			2.0.1
			2.0.2
	Solaris on SPARC	Sun Solaris 8 SPARC	2.0	Untested
			2.0.1
			2.0.2
	HP-UX on hp9000 PA-RISC	HP-UX 11i hp9000	2.0	Untested
			2.0.1
			2.0.2
	AIX on PowerPC	IBM AIX 5.1 on PowerPC	2.0	Untested
			2.0.1
			2.0.2
GTK	Linux on Intel x86	RedHat Linux 7.2 x86 GTK 2.0*	2.0	Early access; untested
			2.0.1	Early access; secondary
			2.0.2	Early access; untested
		SuSE Linux 7.3 x86 GTK 2.0	2.0	Early access; untested
			2.0.1
			2.0.2
		Other Linux; kernel version 2.4.7, and GTK 2.0	2.0	Early access; untested
			2.0.1
			2.0.2

* Note actually tested with RedHat Linux 8.0 x86.

Internationalization

The WepApp Plug-in user interface, including dialogs and error messages, are externalized and tested in the following locales:

English

2. Compatibility with Previous Release

Not applicable (this is the first release).

3. Known Issues

3.1 WebApp Plug-in

A NullPointerException occurs when performing a right click on a Web Application project.

The workaround to this problem is to restart the Eclipse workbench and try again. This problem occurs intermittently and seems to be connected to the enablesfor parameter of the menu action. The problem is more prevalent on Linux. (Resolved in release 0.9.0)

A FileNotFoundException or NullPointerException after deleting the ‘.servers’ project or sub-folder.

The ‘.servers’ project may have been deleted whilst a web application server was running. Stop the server before deleting the ‘.servers’ project. The workaround to this problem is to restart the Eclipse workbench and try again.

A BindException, in the console, while starting a web application server.

A service is already running on the specified port, this is sometimes due to a previous web application server process not terminating correctly. The workaround to this problem is to restart the system (PC). Alternatively a different service is ‘legally’ running on the port therefore the default port number of the web application server can be changed in the plug-in preferences.ini and the Eclipse workbench restarted.

Context name has to be re-entered after initial checkout from CVS

The context name is a persistent property, however persistent properties are not managed by the Eclipse CVS interface and therefore the context name defaults to an empty string when a web application project is first checked out of a CVS repository. The workaround is simply to re-enter the context name in the web application properties screen when the project is first checked out of the CVS repository.

3.2 Tomcat Adapter

None.

3.3 Jetty Adapter

A DebugException when the server is stopped on RedHat/Linux.

When the Jetty server is stopped a DebugException is written to the Eclipse workspace log but the server seems to shutdown correctly. This probelm does not occur on Windows 2000 and may be a bug specific to the Linux JDK or Eclipse GTK. The workaround is simply to ignore the error as the server does shutdown and can be restarted normally.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.