Setting Up for JWAVE Client Development
The only thing you need to set for JWAVE client development is the CLASSPATH environment variable. Set the CLASSPATH on a JWAVE client to include (at least):
(UNIX) RW_DIR/classes/JWave.jar
(WIN) RW_DIR\classes\JWave.jar
where RW_DIR is the main Rogue Wave installation directory.
The JWAVE Client documentation is referenced with:
(UNIX) RW_DIR/classes/docs/api/packages.html
(WIN) RW_DIR\classes\docs\api\packages.html
Example client side development code is located in subdirectories of:
(UNIX) RW_DIR/classes/jwave_demos
(WIN) RW_DIR\classes\jwave_demos
To use JWAVE Beans, you need to:
Add Swing 1.1 or later to CLASSPATH (swing.jar or swingall.jar).Import the JWaveBeans.jar into BDK 1.0_mar98 or an IDE like JavaStudio.To run client applets, you need a browser or appletviewer with access to the JWAVE Manager (usually through a Web server). Make sure that the CLASSPATH does not include any JWAVE JAR files or classes. (JWAVE applets can only communicate with the JWAVE Manager if the applets are served by that server—having these classes in CLASSPATH causes a security error.) note | You must have access to the JWAVE server for JWAVE client applications to work properly. |
To run client applications (in other words, applications outside of a browser), you also must have JWaveConnectInfo.jar in your CLASSPATH. See notes in the README file in the subdirectories of RW_DIR/classes/jwave_demos for other hints on setting up your environment. 
