This release is FCS version 1.2 and has been tested using
JDK 1.1.6 (except for the XFileChooser component) and JDK1.2.
This release includes the following:
To make use of the entire WebNFS 1.2 FCS release, you must have JDK 1.2 or later installed on your system. Therefore we recommend you install JDK 1.2 if you have not already. It may be found at http://www.java.sun.com/products/index.html.
If you are using JDK 1.1.6, you must also have the Swing 1.1 set (available at http://java.sun.com/products/jfc/index.html#download-swing) in order to use the XFileChooser. You can use the other WebNFS components without Swing 1.1.
There is a bug (#4169763) that requires the a patch for XFileChooser to work correctly. We expect this bug to be fixed in JDK 1.2.1. For more on using this patch, see below.
Because of a problem with file recursion in the JDK 1.2 JFileChooser, you must use a patch we provide in order to make the WebNFS Bean (XFileChooser) work properly. This patch consists of three *.class files found in the JFileChooser-patch directory of this product.
If you are using JDK 1.2, use the -Xbootclasspath option to include the JFileChooser-patch directory. For example, for Solaris, you might say something like:
% java -Xbootclasspath:../JFileChooser-patch:$JAVA_HOME/jre/lib/rt.jar:/home/me/SDK12.jar:. myProg
If you are using JDK 1.1.6, set your CLASSPATH variable to include the JFileChooser-patch directory. For example:
export CLASSPATH=../JFileChooser-patch:../webnfs.zip:/usr/java/lib/classes.zip:/swing.jar: /multi.jar
Requirements:
Requires JDK1.2
A new package has been added to the WebNFS SDK that contains the methods for the WebNFS Bean (XFileChooser).
The XFileChooser provides a high level component that developers can utilize in designing user interfaces. This component is a file selector box that allows users to view files/directories and select a file either locally or remotely via NFS URLs. This project utilizes two existing APIs:
The XFileChooser depends on the Java Development Kit 1.2 since it extends an existing Bean provided in JDK1.2, the JFileChooser. It inherits methods that are defined in the JFileChooser. Please refer to the javadocs of the JFileChooser.
The XFileChooser is a Bean that can notify other Beans
that are registered listeners
of its property changes and action events. The other Beans register
themselves by calling the method addActionListener
or addPropertyChangeListener. The events generated by the
XFileChooser Bean (also known as the WebNFS Bean) are categorized in
two types:
The XFileChooser can be incorporated into a Bean-aware Java editor
or tool (for example, BeanBox(tm)) by importing the xfilechooser.jar file.
Inside such a builder tool, the XFileChooser Bean will be identified by a
unique icon on the designer palette. The Bean supports a
property sheet that allows users to customize the Bean.
Customizable features include: set the dialog type, dialog
title, file selection mode, enable hidden files, approve text button,
tooltip, approve button mnemonic, set look and feel,
and set current directory.
ID | Synopsis | Severity | Priority |
---|---|---|---|
4123748 | Client code doesn't escape "%" when evaluating relative UR | 5 | 3 |
4155312 | Spurious retransmissions from Windows/NT | 5 | 4 |
4155313 | Threads writing to common XFileOutputStream sometimes hang | 5 | 4 |
4215784 | Can't reference to Unix root with file URL | 4 | 4 |
4216189 | Bean Combo box does not show path if filename=nfs://buttonhead/ | 4 | 4 |
The following are some of the JFileChooser bugs that may be of interest to the programmer. For a full list of JFileChooser bugs, see the JDK 1.2 documentation or the JDK 1.1 documentation.
You should test your client application against both WebNFS-enabled servers and non-WebNFS-enabled servers. Currently three commercial WebNFS-enabled servers are available:
WebNFS client applications should assume that the server is WebNFS enabled. Please refer to the WebNFS Client Specification (RFC2054), section 7 "Contacting the Server" for details on recommended coding techniques.
However, if you do not have access to a WebNFS enabled server, your application should still work. The WebNFS client code falls back to what the server supports.
Last modified: March 26, 1999