NativeJ 4.7.12

NativeJ generates Win32 native launchers for your Java applications. No more ugly batch files!
The launchers generated by NativeJ look and behave exactly like native Win32 programs.
Automatically generates Win32 native EXE for your Java applications. No more ugly batch files!
They possess their own custom icons when viewed in Explorer, and they do not appear as another java.exe or javaw.exe in the process list.
You can generate launchers that behave like console programs, or graphical programs, or even Win32 services.
Besides looking and feeling like native apps, these launchers also have another advantage: speed.
Executing a batch file requires first loading up the command processor, which steps through each line of the batch file before it encounters the line which calls the Java frontend java.exe or javaw.exe.
This frontend imposes further overhead as it parses the command-line arguments before loading the JVM with the proper parameters.
The native launchers generated by NativeJ eliminates all these overhead and load the JVM directly, resulting in snappier program loading.
NativeJ is available in two versions:
Standard Edition. The following features are not available in the standard edition: Win32 service creation, JAR files embedding, version information, customization of strings and messages.
Professional Edition. All features are available in the professional edition, including: Win32 service creation, JAR files embedding, version information, customization of strings and messages.
Main features:
- Custom icon. Each executable is represented by a unique icon, just like native apps.
- Native behaviour. When the user double-clicks on the EXE to run your application, there wont be an annoying console window popping up briefly.
- Faster startup. Executing a batch file involves a great deal of overhead, including loading the command processor and parsing the batch file. The native EXE loads the JVM directly, resulting in snappier program startup.
- Native splash screen. Display a splash screen of your choice immediately upon startup while your application loads.
- Unique process name. When viewed in the task list, the user sees tomcat.exe, or jedit.exe, instead of the nondescript java.exe, or javaw.exe. This is particularly important for personal firewall programs, which depend on unique process names to trigger the appropriate filter rules.
- Install as service. NativeJ generates executables that can be installed as a Win32 service natively, with the ability to specify dependencies