Use the latest, greatest, fastest JVM you can get your hands on for your platform. The compiler's performance is dependent on the performance of the JVM it is running on, so the faster a JVM you can find to run it on, the shorter your compile times will be. At a minimum you need to use a Java 2 or later JVM to run the compiler (J2SE 1.3 for AspectJ 1.1). We realize that this constraint can be a problem for users who don't currently have a Java 2 JVM available.

You might want to remove the Microsoft JVM, which Microsoft no longer supports, in favor of the more recent Sun Microsystems JVM. To remove the Microsoft JVM, perform the following steps: The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\JAVA_VM registry subkey (to remove the Microsoft Internet Explorer (IE) options When Internet Explorer 7 is installed on Windows XP, ctfmon.exe runs in the background without purpose, and when the Run entry for ctfmon.

The AspectJ compiler or weaver is required at some point, but many people can use AspectJ without changing their build or deployment process significantly. For aspects that are not required to compile, you can use the AspectJ binary weaver, run at build-time or class-load-time. You can write aspects using the original code style (which must be compiled with the AspectJ compiler) or using the annotation style new in AspectJ 5 (which may be compiled with Javac or the AspectJ compiler).

But at this time, unfortunately not. The two compilers are just not at all compatible. In an ideal world, there would be a wonderful Open Source extensible compiler framework for Java that both GJ and AspectJ would be built on top of, and they would seamlessly interoperate along with all other extensions to Java that you might be interested in, but that's not the case (yet?).

No. A virtual machine requires a set of core libraries to run applications. Some of these libraries are packaged as a part of a CLDC implementation along with the virtual machine. In addition, the capabilities of CLDC can be extended by adding profiles such as the Mobile Information Device Profile (MIDP) and/or optional packages.

Yes. CLDC-based applications can execute in other Java Virtual Machines, provided that the required CLDC libraries, profiles, and/or optional packages are also available.

Those VMs are designed for statically typed languages. That's fine, since Java, C#, and lots of other languages are statically typed. Perl isn't. For a variety of reasons, it means that Perl would run more slowly there than on an interpreter geared towards dynamic languages. The .NET VM didn't even exist when we started development, or at least we didn't know about it when we were working on the design. We do now, though it's still not suitable. Sure we will. They're just not our first target.

In AspectJ 1.0, the PARSER for ajc is written by hand. This choice was made with full awareness of the generator tools out there. (Jim had for example used the excellent javacc tool for building the parser for JPython (now Jython)). One of the reasons that AspectJ uses a hand-written parser is that using javacc taught Jim about the LL-k design for parsers (pioneered by antlr). As opposed to the state-machine parsers produced by yacc, these parsers are very readable and writable by humans.

No, you cannot. Java requires a huge amount of memory and considerable processing horsepower to run. Here is our advice: One of the things that makes Java so big is its support for graphics. If you need graphics in your application, the IPm is not suited for your application (since it is a blind node). If you don't need graphics, we suggest porting your application to efficient and highly portable C code. We have been told that Java is not as portable as Sun Microsystems would have you believe.

J2SE 1.3 or later is required. We have not tested extensively with the latest 1.5 JVM. So we packaged a 1.4.x JVM with the latest installer of D2K 4.1.1.

J-DSP is a set of Java applets that require a Java virtual machine to run properly. Before launching J-DSP, the courseware will provide you with the opportunity to link to Sun to download the latest Java virtual machine at http://java.com/en/index.jsp (Windows-only). If you are a Mac user you can download a current Java virtual machine directly from Apple at http://docs.info.apple.com/article.html?artnum=120209.

A6) NSIcom CrEme JVM will work. Follow the Software Application Installation Application Note. This may require additional program memory. If so, from the download page, download and install the NP-612S 20M Program Memory Image. Follow the Windows CE Download Instructions.

The best compiler bug report is a reproducible test case, standalone code that demonstrates the problem. Sometimes with aspects, a test case requires several files, if not some way to capture the behavior. Here's how we recommend submitting test cases: Write the test case so that when the compiler bug is fixed, the test completes normally without output (e.g., expected compiler errors are issued, or classes produced run correctly). This usually means writing one or more source files.

DB/XML Transform has two modes: graphical user interface mode, and non-graphical mode. For the graphical user interface (the default mode), you will need Java Virtual Machine or Java Runtime Environment 1.2 or higher. The latest JDK version for Windows platforms is 1.3, available for download on Sun's website. For your convenience, we have included the JRE 1.3 in one of our DB/XML Transform install program.

Since AspectJ requires Java 2 or later, it will not run on the Microsoft JVM, which does not support Java 2. No. Some previous versions of AspectJ had this requirement. In AspectJ 1.0, javac can still be used as ajc back end by using the -usejavac flag. You can also run ajc in preprocessor mode to generate Java source (.java) files to be compiled using javac or another java compiler. Neither option is supported in AspectJ 1.1.

Microsoft (because of a court battle with Sun Microsystems) no longer offers the base installer for the Microsoft Java Virtual Machine (JVM). If you have no version of the Microsoft JVM installed and need one in order to run ToolBook's DHTML, you can download and install the JVM using this link: Click here to download Microsoft VM I use Windows XP. When I try to load Tier 2 and 3 courses, all the course material is garbled and loading at the same time.

No. Protégé requires a JDK 1.4 compatible virtual machine (Protégé 3.1 requires JDK 1.4 , Protégé 3.2 beta requires JDK 1.5). The last we are aware of, the MSJVM only supports JDK 1.1. Microsoft also plans to terminate support for the MSJVM on September 30, 2004.

ajc can be used to develop programs that are targeted at the Java 1.1 platform, even though the ajc compiler won't run on that platform. Here's an example of using ajc in this sort of cross-compilation mode (assuming a Windows platform with all the default installation directories): ajc -target 1.1 -bootclasspath c:\jdk1.1.7\lib\classes.zip \ -classpath c:\aspectj1.0\lib\aspectjrt.jar -extdirs "" \ -argfile jdk11system.lst This same technique can be used if you want to run ajc on a JDK 1.

The Microsoft Java Virtual Machine (MSJVM) is technology that has been included in some versions of Microsoft Internet Explorer, a component of Microsoft Windows?. This technology allows certain types of programs, called Java applications or Java applets, to run on Windows-based computers. The only change is the date of end of support for the MSJVM, to December 31, 2007, from September 30, 2004.

Usually the default memory configuration of your VM should be sufficient to work with SQL Developer. If you want to increase the available memoy anyway you will have to start the application with additional command line options. If you use a Sun Microsystem Java VM open a shell window, change to the SQL Developer folder and type java -Xmx256m -jar sqldeveloper.jar to start with a maximum heap memory of 256 MB. The default maximum heap size is 64 MB.

Go to your start button and click on Run. Type in "command" (in Windows 98) or "cmd" (Windows 2000 or XP) and click OK. At the command prompt type in "jview" and hit Enter. The very top line should read "Microsoft ? command-line loader for java version #.##.####". Those #'s should be 4.79.2339 or above. If your version is not up-to-date, see the Computer Requirements for a link to an update version of the JVM.

The JDK, also called the Java Software Development Kit (SDK), is the full suite of tools required to develop, package and publish Java applications. The Sun Java SDK includes the full Java class library, with a compiler, decompiler, profiler, JAR signer, key signing tool and many other tools.

The AspectJ tools run on any Java 2 Platform compatible platform. The AspectJ compiler produces classes that run on any Java 1.1 (or later) compatible platform.

AspectJ is a registered trademark of Palo Alto Research Center, Incorporated (PARC), used with permission. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.

On Linux RootCause has been tested with Sun JVMs 1.4.0 through 5.0 and IBM's 1.4 JVM. Linux RootCause does not work with gcj. We have provided support for older versions of Java for specific customers: please contact us if you have a specific need. Some of our probes, most notably java_memstat make use of the JVMPI debugging interface, which has turned out to be unreliable in earlier versions, and which has been eliminated entirely in Java 1.6.

The latest version of WordRider requires at least version 1.5 of the Java 2 platform, and therefore will not be compatible with Microsoft's Virtual Machine.

The latest version of jEdit, version 4.3, requires at least version 1.5 of the Java 2 platform, and therefore may not be compatible with 3rd party virtual machines.

There will be a WebSphere install for the client container. This install will put the JVM and any necessary WebSphere classes on the remote client machine.