You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

1.3 Release Notes

READ THIS Before You Build and Install

The only platform for which we have a binary release for webclient 1.3 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.3 depends on Mozilla 1.0.1 or Netscape 7.0.1. 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 1.0.1 please visit http://www.mozilla.org/build/.


Installing the 1.3 Release

Win32

This section explains how to install and run webclient using the win32 binary distribution.

  1. Un-install any existing webclient installations.

  2. Install JRE 1.3 from http://java.sun.com/j2se/1.3/.

  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

  4. Install Mozilla 1.0.1, from http://www.mozilla.org/releases/, or install Netscape 7.0 If you install Mozilla. DO NOT CHECK the QuickStart box in the installer. It may work, I just haven't tried it.

  5. Run the browser installed in the previous step and configure any proxy settings you may need to operate the browser.

  6. 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_3-xpi.html. Click on the "Webclient for Win32 Platforms" button.

  7. 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 

    C:\Program Files\Netscape\Netscape 6
    the value of MOZILLA_FIVE_HOME should be: 
    C:\PROGRA~1\Netscape\NETSCA~1

  8. Add %MOZILLA_FIVE_HOME% to your system PATH.

  9. cd to %MOZILLA_FIVE_HOME%\javadev\example

  10. type 

    .\runem

  11. 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

  1. Un-install any existing webclient installations.

  2. Install JRE 1.3 from http://java.sun.com/j2se/1.3/.

  3. Set the system environment variable JDKHOME to be the location where you installed the JRE, something like /usr/java/jdk1.3.1_01.

  4. Install Netscape 6.1, from http://home.netscape.com/browsers/, or Mozilla 1.0.1, from http://www.mozilla.org/releases/.

  5. Run the browser installed in the previous step and configure any proxy settings you may need to operate the browser.

  6. 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_3-xpi.html. Click on the "Webclient for Linux Platforms" or "Webclient for Solaris SPARC" button, which ever is appropriate for your system.

  7. 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.

  8. Make sure no process with the name "xpicleanup" is still running after the browser exits.

  9. cd to $MOZILLA_FIVE_HOME/javadev/example

  10. type 

    sh ./runem.bat

  11. This should run the webclient test browser

Building the 1.3 Release

Build Instructions -- Cross Platform

This section explains the steps one has to perform before building 1.3 on any platform.

  1. Get the mozilla 1.0.1 source tarball.

  2. Build Mozilla 1.0.1 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.

  3. Once Mozilla 1.0.1 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.

  4. Install JDK1.3.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.

  5. Unpack the webclient source, from http://www.mozilla.org/projects/blackwood/webclient/src/webclient_1_3_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_3_src.tar.gz $MOZILLA
cd $MOZILLA
gunzip webclient_1_3_src.tar.gz
tar -xvf webclient_1_3_src.tar

    And on win32:

      copy webclient_1_3_src.tar.gz %MOZILLA%
cd %MOZILLA%
gunzip webclient_1_3_src.tar.gz
tar -xvf webclient_1_3_src.tar

      Note that on win32, gunzip and tar come from the cygnus package, which you needed to build mozilla.

    -->

  6. Check out the webclient source from CVS.

    7. This will give you the following directory hierarchy

    $MOZILLA
  java/
    Makefile.win
    Makefile.in
    makefiles
    config/
    dom/
    external/
    util/
    webclient/

  7. 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.3.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.3, the only UNIX platform on which webclient is known to work is RedHat Linux 7.2+. Support for Linux was provided by Jason Mawdsley, and Louis-Philippe Gagnon.

  1. Follow the instructions in Build Instructions -- Cross Platform. If you're building on Solaris, this document, mozSolBuild.html, may be of help.

  2. 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.

  3. 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.

  4. 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

    5. If you don't have these makefiles, you won't be able to build webclient.

  5. 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

  6. 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.

  7. 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.

Build Instructions -- Win32

  1. set MOZ_DEBUG=1 in your environment

  2. set PATH so that it contains %MOZILLA_FIVE_HOME% and %MOZILLA_FIVE_HOME%/components.

  3. Follow the instructions in Build Instructions -- Cross Platform

  4. cd $MOZILLA\java

  5. nmake -f Makefile.win

    This should build the mozilla util classes, the javaDOM, and webclient.

  6. cd $MOZILLA\java\webclient\src_moz

  7. .\runem <ABSOLUTE_URL> This should run the test browser.

Uninstalling the 1.3 Build

Uninstalling if you're using the binary install

  1. Stop any running mozilla or webclient instances

  2. cd $MOZILLA_FIVE_HOME

  3. rm -rf javadev

  4. 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 1.0.1 release notes.

  1. cd $MOZILLA

  2. rm -rf ./java

Unix

  1. Do the cross platform uninstall.

  2. cd $MOZILLA/dist/bin

  3. rm libwebclient*.so libjavadomjni.so

Windows

  1. Do the cross platform uninstall.

  2. cd $MOZILLA\dist\WIN32_D.OBJ\bin

  3. 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 1.0.1 release notes to remove the registry, then re-run mozilla 1.0.1 to generate a new registry.

Known Bugs