1.2 Release Notes
READ THIS Before You Build and Install
The only platform for which we have a binary release for webclient 1.2 are Win32 and RedHat GNU/Linux 7.2 . All other platforms must build their own mozilla and webclient. We hope to have other binary builds available before the next release.
Webclient 1.2 depends on Mozilla 0.9.9. 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 0.9.9 please visit http://www.mozilla.org/build/.
Installing the 1.2 Release
Win32
This section explains how to install and run webclient using the win32 binary distribution.
Un-install any existing webclient installations.
Install JRE 1.3 from http://java.sun.com/j2se/1.3/.
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.1_01
, which contains spaces, you must use the funky ~1 convention for long filenames. That is,JDKHOME=C:\PROGRA~1\JavaSoft\JRE\1.3.1_01
-
Install Mozilla 0.9.9, from http://www.mozilla.org/releases/. If you install Mozilla. DO NOT CHECK the QuickStart box in the installer. It may work, I just haven't tried it.
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_2-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.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
Un-install any existing webclient installations.
Install JRE 1.3 from http://java.sun.com/j2se/1.3/.
Set the system environment variable JDKHOME to be the location where you installed the JRE, something like
/usr/java/jdk1.3.1_01
.Install Netscape 6.1, from http://home.netscape.com/browsers/, or Mozilla 0.9.9, from http://www.mozilla.org/releases/.
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_2-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
.Make sure no process with the name "xpicleanup" is still running after the browser exits.
cd to
$MOZILLA_FIVE_HOME/javadev/example
type
sh ./runem.bat
This should run the webclient test browser
Building the 1.2 Release
Build Instructions -- Cross Platform
This section explains the steps one has to perform before building 1.2 on any platform.
Get the mozilla 0.9.9 source tarball.
Build Mozilla 0.9.9 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 0.9.9 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_2_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_2_src.tar.gz $MOZILLA cd $MOZILLA gunzip webclient_1_2_src.tar.gz tar -xvf webclient_1_2_src.tar
And on win32:
copy webclient_1_2_src.tar.gz %MOZILLA% cd %MOZILLA% gunzip webclient_1_2_src.tar.gz tar -xvf webclient_1_2_src.tar
Note that on win32, gunzip and tar come from the cygnus package, which you needed to build mozilla.
Check out the webclient source from CVS.
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
This will give you the following directory hierarchy
$MOZILLA java/ Makefile.win Makefile.in makefiles config/ dom/ external/ util/ 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 Instructions -- 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.2 Build
Uninstalling if you're using the binary install
Stop any running mozilla or webclient instances
cd $MOZILLA_FIVE_HOME
rm -rf javadev
rm -rf *webclient* *javadom* *blackconnect* components/*javadom* components/*bcorb* components/*bcjava* components/*bcTest* components/*bcxpcom*
Uninstalling if you've built from Source
Cross Platform
Follow the instructions for removing mozilla in the mozilla 0.9.9 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 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.
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 0.9.9 release notes to remove the registry, then re-run mozilla 0.9.9 to generate a new registry.
Known Bugs
Can't do File->New Window on unix: Bug 156712. This one is a real stumper for me.
The freeze bug has been fixed!
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".