Traditionally, Java programmers write Java code for creating GUIs in an editor or using a WYSIWYG editor from with an integrated development environment (IDE). After the code has been written (or generated), a second JVM is launched in which the GUI can be evaluated and tested. When problems occur, the second JVM is shutdown, the code is modified, and the second JVM is then relaunched to re-evaluate and retest the GUI being developed.
When ACTF launches and validates a GUI using either the Eclipse Application with ACTF or Java Application with ACTF launch configurations, it is mimicking the traditional behavior noted above. A distinct JVM is launched from that in which the Eclipse installation with RAVEN is hosted and the GUI resides in that second JVM. Communication between the two JVMs is accomplished via a socket, much like the Eclipse debugger works. Such validations are called inter-JVM validations.
On the other hand, when you launch and validate a GUI from the Package Explorer in the Java Perspective, the validated GUI is rendered in the Rendered Gui View. Here, the GUI that is rendered and validated by RAVEN resides in the same JVM as that which hosts the Eclipse environment with RAVEN and this is an intra-JVM validation.
There are several advantages to intra-JVM GUI renderings: