|
Q. What is being released? back to top
A. A binary version of the PersonalJava application environment for
Windows CE devices. This code is targeted for devices running version 2.11
of the Windows CE operating system and should run on the following processors:
MIPS (R4000 Compatible) / SH3. The device should have at minimum 16 MB of
storage.
Q. How long has this implementation been available? back to
top
A. This implementation became available in May 2000. The Beta 1 implementation has been available since December 21, 1999.
The Beta 2 implementation became available in March 2000.
Q. On what Windows CE devices will I be able to run this code? back to top
A. This code should be able to run on devices running version 2.11 of the
Windows CE operating system with one of the following processors: MIPS
(R4000 Compatible) / SH3. The device should have at minimum 16 MB of
storage and a 16 color or grayscale display. We have successfully certified
with the PersonalJava Runtime Environment conformance compatability kit
on the following devices : IBM Workpad Z50, Compaq Aero 2100, HP Jornada
430 SE.
Q. Will there be an x86 or an x86 emulation environment made available? back to top
A. There are no plans for an x86 or x86 emulation implementation at present.
Q. Will SH1 or SH2 CPUs be supported? back to top
A. There are no plans for a SH1 or SH2 implementation at present. If a port
to these platforms is required, the best solution is to license the code
from Sun, and produce your own version. For more information, please contact
us via the feedback alias: personaljava-wince@sun.com.
Q. Will there be a version for the StrongARM processor? back to top
A. We are currently working on StrongARM support. We currently plan to have a
beta available around the end of October 2000.
Q. Will there be a version for Windows CE 2.0? back to top
A. No. 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.
Q. Will this work on Windows CE 2.12? back to top
A. This was targeted for Windows CE 2.11, and has not been fully tested on
Windows CE 2.12. We are not aware of any incompatibilities between
2.11 and 2.12 that would cause problems. If you know of any, please
let us know.
Q. Will this work on PocketPC 3.0? back to top
A. This was targeted for Windows CE 2.11, and has not been fully tested on
CE 3.0. There are some incompatibilities between 2.11 and 3.0 that
will cause problems, the most noticeable of which is a problem
refreshing the title bar of an application on CE 3.0.
Q. Will there be a version for PocketPC 3.0? back to top
A. We are currently working on improved 3.0 support. We currently plan
to have a beta available around the end of October 2000.
Q. How can I configure Pocket IE to work with this? back to top
A. This version is not a plugin for Pocket IE, but rather an
implementation of the PersonalJava Runtime Environment.
Q. How do I load this code onto my Windows CE device? back to top
A. The binary comes packaged in a Microsoft "CAB" file. Ensure sufficient
storage (~2.5MB) is available on the target device before downloading.
Download the appropriate CAB file for the processor your device runs on.
Copy the CAB file to the "Start Menu" on the target device. Begin
installation by selecting the file from "Start Menu" when downloaded to
target device. After successful installation, ensure sufficient memory
is available on target device to allow applications to execute.
Q. Why does the CAB file not run correctly? back to top
A. Ensure that the entire zip file has been downloaded and correctly
expanded. 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.
Q. Why does the Beta 1 implementation not uninstall correctly? back to top
A. 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 these files
and remove the tests directory "\Program Files\Java\Java Tests" manually.
Rerun the uninstaller and then manually remove the Java directory for a
complete uninstall. The Beta 2 implementation should uninstall correctly.
Q. What will I be able to do with this code after it is loaded onto my Windows CE
device? back to top
A. You will be able to run applications or applets written in the Java
programming language to the PersonalJava technology API specification,
version 1.1.x. You can find
the specification at http://java.sun.com/products/personaljava/.
Q. Where can I find support? back to top
A. There is no support provided with this product. However, comments or
problem reports can be sent to personaljava-wince@sun.com.
Q. Can I distribute this code? back to top
A. Please refer to the click-thru license for more details.
Q. Is this implementation optimized in any way? back to top
A. This implementation has a smaller memory footprint than the Beta 1
implementation. However, the PersonalJava runtime environment for Windows CE
is not intended to be a fully optimized product.
Q. Why will applications written for Java 2 Platform, Standard Edition not run
on this implementation? back to top
A. This implementation of PersonalJava runtime environment is based on
JDK 1.1.x. software. Hence, some code written for Java 2 Platform, Standard
Edition may not run on our implementation.
Q. What command line options are supported? back to top
A. 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
|
Q. How is the classpath set? back to top
A. 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.
Q. How can I change the classpath (or any command line parameter) for my
application without having to edit the registry? back to top
A. You can use a '.lnk' file to do this. These are created when you create
shortcuts. You can then edit the properties of the shortcut to modify
command line parameters.
Q. Can I use the PersonalJava Runtime Environment to run applets? back to top
A. Yes, this can be used to run applets stored on the local file system.
See the README for more details.
Q. How do I run executable jar files? back to top
A. 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.
Q. What optional packages does this implementation include? back to top
A. The following packages are fully implemented as specified in the 1.1.3
PersonalJava specification in this version:
java.awt
java.io
java.math
java.rmi
java.sql
java.util.zip
The optional package java.security is not implemented.
|
Q. Does this implementation include JDBC API classes? back to top
A. This implementation includes java.sql, which is an optional package.
Hence, JDBC API will work.
Q. Does this implementation include Java Native Interface (JNI) support? back to top
A. Yes, JNI support is included.
Q. Does this implementation include CORBA support? back to top
A. No, the java.idl package is not supported.
Q. What are the license restrictions on deployment of this implementation? back to top
A. Please refer to the click-thru license for further details.
Q. Will this implementation run on the Philips Nino 300/500 Series? back to top
A. This implementation should now run on the Nino, which uses a MIPS R3000
processor. However, since Philips has discontinued the Nino, it is proving
difficult to support it.
Q. Will this implementation run on the Compaq Aero 1500 series (with a 16
color grayscale display)? back to top
A. The Compaq 1500 is not 16 color by default. Please follow these steps:
1.Go to QUtilities -> Contrast
2.Set the device for higher picture quality, then tap reset.
3.Verify that the device is in higher quality mode, and then re-run
the application.
Q. Where can I find sample applications to run on this implementation? back to top
A. As this port supports most of the AWT many simple 'hello world' examples
should work. Try some of the examples from the online tutorials.
| 
Print-friendly Version
