Sun Java Solaris Communities My SDN Account Join SDN
 
Archive - Java Technology Products Download

PersonalJava(TM) Runtime Environment for Windows CE - READMEn

 

CONTENTS

INTRODUCTION

Thank you for downloading this release of the PersonalJava(TM) runtime environment for Windows CE. This implementation became available in May 2000.

INSTALLATION

  • Handheld PC / Palm PC:
    1. Ensure sufficient storage (~2.5MB) is available on the target device before downloading.
    2. Download the appropriate CAB file for your processor.
    3. Copy the CAB file to the "Start Menu" on the target device.
    4. Begin installation by selecting the file from the "Start" menu when downloaded to target device.
    5. After successful installation, ensure sufficient memory is available on target device to allow applications to execute. Refer to the copyright and license for legal terms of use.

  • Installation Help
    Ensure that the entire zip file has been downloaded. The CAB file runs on the device itself once selected - no other applications are necessary. A CAB file targeted for a specific processor will not run on a device with a different processor. This implementation will not run on Windows CE 2.0.

  • Uninstallation of Beta 1
    The uninstallation of the Beta 1 implementation will result in a warning that the following files:

    \Program Files\Java\Java Tests\Welcome\Duke.gif

    and

    \Program Files\Java\README_BIN.txt

    are READ-ONLY and the uninstallation will not proceed. Delete the README_BIN.txt file and remove the tests directory
    "\Program Files\Java\Java Tests" manually. Rerun the uninstaller and then manually remove the Java(TM) directory for a complete uninstall.

NOTES

  • Processors Supported
    At this time, only the MIPS (R4000 Compatible) and the SH3 processors are supported.

    Please check the download page and FAQ for additional processor support. You need to download and install the appropriate CAB file for your processor.

  • Windows CE OS Version
    This version is not targeted for Windows CE 2.0 and there are no plans to release a version supporting Windows CE 2.0. We investigated this platform early on and found it was missing some of the I/O functions that the PersonalJava runtime environment needed. Furthermore, we saw that the market was moving to 2.11 and that the added cost in terms of development and support would not be worth it.

  • Compatibility
    This implementation of PersonalJava runtime environment is based on JDK(TM) 1.1.x. Hence, some code written for Java 2 Platform Standard Edition may not run on this implementation.

  • Application Execution
    The PersonalJava runtime environment is executed through the file "pjava.exe". All ".class" and ".jar" files are associated with the PersonalJava runtime environment. This implementation can run standard applications, executable JAR files and applets. Standard applications and executable jar files are executed by the command line or by clicking on the class itself. Applets contained in html pages are executed though the command line. Examples are given below.

    Command Line Options

    Along with the standard options the following options can be used on the command line on the HPC:

    -file

    Allows the user to enter a file of type ".class", ".jar", or ".html" on the command line. The PersonalJava runtime environment will execute any one of these file extensions :
    ".class"
    ".jar" (an application archived into a jar file)
    ".html" (a HTML page containing a Java applet)

    Examples:

    "\Program Files\Java\bin\pjava.exe" -file Test.class

    This command will invoke the PersonalJava runtime environment to run the application with the main method residing in the class "Test".

    "\Program Files\Java\bin\pjava.exe" -file Test.jar

    This command will invoke the PersonalJava runtime environment to run the application, which is archived in the jar file "Test".

    "\Program Files\Java\bin\pjava.exe" -file Test.html

    This command will invoke the PersonalJava appletviewer to run the applet in the html page "Test".

    -setcwd

    Allows the user to set the "current working directory" by using the "-setcwd" option on the command line. This is needed, for example, when running an applet where the "current working directory" is set to the directory where the html and applet classes reside.

    Example:

    "\Program Files\Java\bin\pjava.exe" -setcwd \Temp -file test

    The html page and the classes necessary for the applet are located in the directory \Temp.

    The standard command line options :

    -help

    print out these options
    -version
    print out the build version
    -v -verbose
    turn on verbose mode
    -verbosegc
    print a message when garbage collection occurs
    -noclassgc
    disable class garbage collection
    -ss<number>
    set the maximum native stack size for any thread
    -oss<number>
    set the maximum stack size for any thread
    -ms<number>
    set the initial heap size
    -mx<number>
    set the maximum heap size
    -classpath <directories separated by semicolons>
    list directories in which to look for classes

  • Setting the CLASSPATH

    For the Handheld PC Pro:

    The classpath can be set on the command line as follows:

    "\Program Files\Java\pjava.exe" -classpath
    "\Temp\OtherClasses.jar; \Classes" -file Test

    The classpath is set to include the Java class files necessary for the application. Here, the OtherClasses.jar file is located in the directory \Temp and the directory \Classes is included in the classpath also.

    Note: The quotes are necessary.

    For the Palm PC:

    A remote registry editor is required (one comes with the MS Windows CE Toolkit for Visual C++ 6.0).

    Change the following:

    HKEY_CLASSES_ROOT

    Java Class File
    Shell
    Open
    Command

    "\Program Files\Java\bin\pjava.exe" -file "%1"

    to

    "\Program Files\Java\bin\pjava.exe" -classpath "\Temp\OtherClasses.jar; \Classes" -file "%1"

    The classpath is set to include the Java class files necessary for the application. Here, the OtherClasses.jar file is located in the directory \Temp and the directory \Classes is included in the classpath also.

  • Executable JAR files

    The jar files manifest file requires a Main-Class header, indicating which class is the application's entry point. The executable JAR file is then started in the standard manner as with other applications.

    Further information on modifying the manifest file:

    JAR Files as Applications - 1.2 platform only
    http://java.sun.com/docs/books/tutorial/deployment/jar/basicsindex.html

    If the application is contained within one jar file, no other changes are needed.

    If the application is contained within more than one jar file, the classpath needs to be modified to include all the jar files required for the application (see above).

  • Optional Packages

    The following packages are fully implemented as specified in the 1.1.3 PersonalJava specification (http://java.sun.com/products/personaljava) in this version:

    java.awt
    java.io
    java.math
    java.rmi
    java.sql
    java.util.zip

    The optional package java.security is not implemented.

    Java Native Interface support is included.

    This implementation includes java.sql, hence JDBC(TM) API will work.

  • License Restrictions

    Please contact the feedback alias personaljava-wince@Sun.COM for further details regarding license restrictions on deployment of this implementation.

  • Sample Applications

    As this port supports most of the AWT many simple 'hello world' examples should work. Try some of the examples from the online tutorials.

TESTS

A test directory [\Program Files\Java\Java Tests] is included in this software bundle with a number of examples to demonstrate correct installation and operation of the PersonalJava runtime environment on the device. These tests can be accessed through the "Start Menu" under "Programs -> Java -> Java Tests" (English Locale). They include Welcome, and GUI Test.

SYSTEM REQUIREMENTS

The PersonalJava runtime environment for Windows CE software is available on these platforms:

  • Windows CE Version 2.11 on Handheld PC / Palm PC
  • Supported Processor (currently either MIPS or SH3)
  • 16 megabytes RAM recommended minimum - with ~6MB free to install and run the PersonalJava runtime environment.

SUN JAVA WEB PAGES

For additional information, refer to these Sun Microsystems pages on the World Wide Web:

http://java.sun.com/products/personaljava

PersonalJava Technology including the 1.1.3 PersonalJava(TM) Specification.

http://java.sun.com/products/personaljava/javacheck.html

JavaCheck(TM) - Platform Compatibility Insurance for your Applications and Applets

http://java.sun.com

The Java Software web site, with the latest information on Java technology, product information, news, and features.

http://java.sun.com/docs

Java Platform Documentation provides access to white papers, the Java Tutorial and other documents.

http://developer.java.sun.com

The Java Developer Connection(SM) web site. (Free registration required.) Additional technical information, news, and features; user forums; support information, and much more.

http://java.sun.com/products

Java Technology Products & API

The PersonalJava(TM) Runtime Environment for Windows CE is a product of Sun Microsystems, Inc.

Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.