Guide: JVM Transmuting for Speed
When JWrapper launches your application it will, wherever possible, transmute the JVM into the JVM that your app needs rather than starting a new JVM for your application since this is quicker and is a single JVM launch, equivalent to any other native installer/launcher method.
This means networking and possibly Swing has been initialised before your application launches. Any JVM Options you specify will be used even during the launch of the transmuting JVM but if your app needs to perform functions before any standard libraries are loaded and used you can specify that your app has a completely new unused JVM each time by specifying a top level tag <MustFork> with a value of ‘true’:
<MustFork>true</MustFork>
This means networking and possibly Swing has been initialised before your application launches. Any JVM Options you specify will be used even during the launch of the transmuting JVM but if your app needs to perform functions before any standard libraries are loaded and used you can specify that your app has a completely new unused JVM each time by specifying a top level tag <MustFork> with a value of ‘true’:
<MustFork>true</MustFork>