1.0 Release Notes
READ THIS Before You Build and Install
The only platforms for which we have a binary release for webclient 1.0 are Win32 and RedHat linux and Solaris Sparc. All other platforms must build their own mozilla and webclient. We hope to have other binary builds available before the next release.
Webclient 1.0 depends on Netscape 6 or Mozilla M18. You can get a binary bundle, or you can build webclient from source. If you build webclient from source, you must first build Mozilla. For instructions on building Mozilla M18 please visit http://www.mozilla.org/build/.
Installing the 1.0 Release
Win32
This section explains how to install and run webclient using the win32 binary distribution.
Install JRE 1.3.0_01 from http://java.sun.com/products/archive/j2se/1.3.0_01/jre/.
Set the system environment variable JDKHOME to be the location where you installed the JRE. Note!!!, if you installed the JRE into a directory like
C:\Program Files\JavaSoft\JRE\1.3.0_01
, which contains spaces, you must use the funky ~1 convention for long filenames. That is,JDKHOME=C:\PROGRA~1\JavaSoft\JRE\1.3.0_01
Install Netscape 6, from http://home.netscape.com/browsers/, or Mozilla M18, from http://www.mozilla.org/projects/seamonkey/release-notes/m18.html.
Run the browser installed in the previous step and configure any proxy settings you may need to operate the browser.
Using the browser from the previous step, visit the xpinstall page for the webclient win32 binary: http://www.mozilla.org/projects/blackwood/webclient/release-notes/1_0-xpi.html. Click on the "Webclient for Win32 Platforms" button.
Exit the browser. Locate the directory where you installed the browser from the first step. In that directory hierarchy, find the directory that contains the file xpcom.dll. Set that directory as the value of the environment variable
MOZILLA_FIVE_HOME
. NOTE!!!: if the directory contains spaces, use the goofy Windows ~1 convention.For example, if the xpcom.dll directory is
the value ofC:\Program Files\Netscape\Netscape 6
MOZILLA_FIVE_HOME
should be:C:\PROGRA~1\Netscape\NETSCA~1
Add
%MOZILLA_FIVE_HOME%
to your system PATH.Due to bug 57689, you must de-install the java plugin in the browser. Do this by cd-ing to
%MOZILLA_FIVE_HOME%\plugins
and removing the NPOJI600.dll and NPJAVA*.dll files, if present. You can re-install the java plugin by re-copying the files from%JDKHOME%\jre\bin
to the plugins directory.cd to
%MOZILLA_FIVE_HOME%\javadev\example
type
.\runem
This should run the webclient test browser
UNIX
This section explains how to install and run webclient using the unix binary distributions. This has only been tested on RedHat 6.2. and Solaris 2.8
Install JRE 1.3.0_01 from http://java.sun.com/products/archive/j2se/1.3.0_01/jre/.
Set the system environment variable JDKHOME to be the location where you installed the JRE, something like
/usr/java/jdk1.3.0_01
.Install Netscape 6, from http://home.netscape.com/browsers/, or Mozilla M18, from http://www.mozilla.org/projects/seamonkey/release-notes/m18.html.
Run the browser installed in the previous step and configure any proxy settings you may need to operate the browser.
Using the browser from the previous step, visit the xpinstall page for the webclient linux binary: http://www.mozilla.org/projects/blackwood/webclient/release-notes/1_0-xpi.html. Click on the "Webclient for Linux Platforms" or "Webclient for Solaris SPARC" button, which ever is appropriate for your system.
Exit the browser. Locate the directory where you installed the browser from the first step. In that directory hierarchy, find the directory that contains the file libxpcom.so. Set that directory as the value of the environment variable
MOZILLA_FIVE_HOME
.cd to
$MOZILLA_FIVE_HOME/javadev/example
type
./runem
This should run the webclient test browser
Building the 1.0 Release
Build Instrictions -- Cross Platform
This section explains the steps one has to perform before building 1.0 on any platform.
Get the mozilla M18 source tarball.
Build Mozilla M18 WITH DEBUG ENABLED. For instructions on how to do that, go to http://www.mozilla.org/build/. Let's assume you built it into directory $MOZILLA.
Once Mozilla M18 is successfully built, you must run it to create a profile, then you must configure the proxy settings, if you are behind a firewall. If mozilla can't see external web pages, neither can webclient.
Install JDK1.2.2 or 1.3 from http://java.sun.com/. We have made an effort to not have any Java2 specific usage in the webclient code, but we haven't tested webclient with older JDKs. It's likely that webclient will work with older JDKs, but some small tweaking may have to be done. There is a bug on this. See the Known Bugs section of this document.
Unpack the webclient source, from http://www.mozilla.org/projects/blackwood/webclient/src/webclient_1_0_src.tar.gz into $MOZILLA.
IMPORTANT: DO NOT USE WINZIP TO UNPACK THE TARBALL. Doing so may cause some files to end up in the wrong place. I'm not sure why this is, but on all platforms use gunzip and tar -xvf to unpack the tarball. For example, on unix:
cp webclient_1_0_src.tar.gz $MOZILLA cd $MOZILLA gunzip webclient_1_0_src.tar.gz tar -xvf webclient_1_0_src.tar
And on win32:
copy webclient_1_0_src.tar.gz %MOZILLA% cd %MOZILLA% gunzip webclient_1_0_src.tar.gz tar -xvf webclient_1_0_src.tar
Note that on win32, gunzip and tar come from the cygnus package, which you needed to build mozilla.
This will give you the following directory hierarchy
$MOZILLA java/ Makefile.win Makefile.in makefiles config/ dom/ external/ util/ webclient/
In addition to the environment variables required for building mozilla, make sure the following environment variables are defined:
- JDKHOME
- the absolute path to your JDK installation. For example,
C:\jdk1.2.2
- MOZILLA_FIVE_HOME
- the mozilla bin directory. For example,
D:\Projects\mozilla\dist\win32_d.obj\bin
- BUILD_WEBCLIENT_ONLY
- 1
Build Instructions -- Unix
As of 1.0, the only UNIX platform on which webclient is known to work is Solaris 2.7 and 2.8 (Sparc and Intel) and RedHat Linux 6.1+. Support for Linux was provided by Jason Mawdsley, and Louis-Philippe Gagnon.
Follow the instructions in Build Instrictions -- Cross Platform. If you're building on Solaris, this document, mozSolBuild.html, may be of help.
The compiler you use to build mozilla must be the same compiler you use to build webclient. Also, you must use gnu make to make both mozilla and webclient.
re-run ./configure in the top-level mozilla source directory, BUT ADD THE FOLLOWING OPTION to your configure options:
--with-java-supplement
. This will cause the proper makefiles to be generated to build webclient.You should end up with the following makefiles, relative to mozilla/java
./webclient/classes_spec/Makefile ./webclient/src_moz/motif/Makefile ./webclient/src_moz/Makefile ./webclient/src_share/Makefile ./webclient/Makefile ./dom/Makefile ./dom/classes/Makefile ./dom/jni/Makefile ./dom/src/Makefile ./dom/tests/src/Makefile ./dom/tests/src/api/Makefile ./util/classes/Makefile ./util/Makefile ./Makefile
Ensure your LD_LIBRARY_PATH includes the following directories:
The directory where your system's X libs live $MOZILLA/dist/bin $MOZILLA/dist/lib $MOZILLA/dist/lib/components $MOZILLA/dist/components
run gmake in the mozilla/java directory. This should descend the following directories, in this order,
util, dom, webclient
, and result in a built webclient.A script should be created,
mozilla/java/webclient/src_moz/runem
that will run the test browser. cd to the src_moz directory and type ./runem to run the test application.
If you don't have these makefiles, you won't be able to build webclient.
Build Instructions -- Win32
set MOZ_DEBUG=1 in your environment
set PATH so that it contains %MOZILLA_FIVE_HOME% and %MOZILLA_FIVE_HOME%/components.
Follow the instructions in Build Instrictions -- Cross Platform
cd $MOZILLA\java
nmake -f Makefile.win
This should build the mozilla util classes, the javaDOM, and webclient.cd $MOZILLA\java\webclient\src_moz
.\runem <ABSOLUTE_URL> This should run the test browser.
Uninstalling the 1.0 Build
Uninstalling if you're using the binary install
cd $MOZILLA_FIVE_HOME
rm -rf javadev
rm -rf *webclient* *javadom* components/*javadom*
Uninstalling if you've built from Source
Cross Platform
Follow the instructions for removing mozilla in the mozilla M18 release notes.
cd $MOZILLA
rm -rf ./java
Unix
Do the cross platform uninstall.
cd $MOZILLA/dist/bin
rm libwebclient*.so libjavadomjni.so
Windows
Do the cross platform uninstall.
cd $MOZILLA\dist\WIN32_D.OBJ\bin
del webclient.dll javadomjni.dll
Available and Unavailable Features
Known Issues
Browser and General Issues
Webclient may crash on exit on Linux and Solaris. You may want to kill the browser using Ctrl-C. This is due to mozilla bug http://bugzilla.mozilla.org/show_bug.cgi?id=59530.
Webclient hasn't yet been stress tested, so there are probably lots of issues that will come up with a little use.
Basic authentication doesn't work if the cache is enabled. Workaround: disable cache. See bug http://bugzilla.mozilla.org/show_bug.cgi?id=61669.
The libwidget_gtk.so shipped with Netscape 6 on Linux is missing a symbol needed by webclient:
handle_gdk_event__FP9_GdkEventPv
If you see errors containing this symbol when running webclient on linux, try using this libwidget_gtk.so .
On Solaris, make sure gtk libs are in your LD_LIBRARY_PATH.
When using the DOM viewer, the text field that displays the text of the currently selected node isn't sized properly. Can someone please fix this?
Printing
Printing is not yet implemented.
Plugins
You can run plugins inside webclient, but on win32, the Java plugin will not work. You must remove the java plugin. Please see the section on installing the win32 binary in this file.
Bookmarks and History
Both the Bookmarks and History interfaces are incompletely implemented.
Profiles
If webclient is acting funny, it may be due to conflicting mozilla registry file. Follow the steps in the mozilla M18 release notes to remove the registry, then re-run mozilla m18 to generate a new registry.
Known Bugs
Webclient freezes after a period of use. See http://bugzilla.mozilla.org/show_bug.cgi?id=64332. On linux, you can work around this by using JDK 1.3.1.
Embedding apps can't setCurrentHistoryIndex. See http://bugzilla.mozilla.org/show_bug.cgi?id=47278
Webclient needs to be displayed to be used. See http://bugzilla.mozilla.org/show_bug.cgi?id=44075
For the complete list, follow this bugzilla link, or go to bugzilla's query page at http://bugzilla.mozilla.org/query.cgi and query for all bugs on the component "Java APIs to WebShell".