| In this topic |
 |
|||||
| Known Issues |
Known Issues for the Microsoft VM for Java
- Using package-managed classes with
existing tools:
A tool called clspack creates all the .zip files that are usually included in the %WINDIR%\Java\Classes, and are now stored in the package manager. It is provided in the SDK\bin directory. You can use it by setting the path to \bin (set path=c:\sdk-java.30p1\bin;%path%) or copying it into the %windir% directory (assuming that the files were unzipped into their default location).
In addition, the value of the CLASSPATH registry setting is prepended with a reference to this generated classes.zip file (if one is not currently there). The compiler provided with the SDK (jvc.exe) checks this location by default for classes—there is no need to set the CLASSPATH environment variable.
For other compilers that do not check this location by default, set the CLASSPATH environment variable with:
set CLASSPATH=%WINDIR%\Java\Classes\Classes.zip
before running the compiler. It's a good idea to place this command in a batch file for easy use.
- Any class calling the ActiveXControl class needs to be trusted. If an applet intends to host an ActiveX Control using the ActiveXControl class, it needs to be signed with the "fully trusted" permission. Any class calling the ActiveXControl class needs to be on the CLASSPATH or have the right permissions ascribed to it through package management. If the jactivex tool is used to host an ActiveX Control, the classes output by the tool end up using the ActiveXControl class. So any code using the classes output by jactivex needs to be trusted.
- Some of the XML Data Source Object (DSO) functionality requires Internet Explorer version 4.0 or higher.
- The following components of the XML
specification have not yet been implemented:
- Conditional sections in the DTD (INCLUDE & IGNORE keywords).
- Some aspects of character encoding.
For more information and an updated version of the Microsoft® XML Parser, go to the XML website.