Great product, keep up the good work.
I found the documentation on the JRE bundle in the manual a little bit lacking however. I would add more detail on:
- The fact that even if you don't specify a "Path without JRE" in the Media section, it still builds an installer without JRE, and if you hit the "Play" button, it will run that one!
- Where the JRE is installed to ([TARGETDIR])
- If a JRE is bundled with the installer, will the .exe application launcher for the java app always use this JRE or might it use another installed JRE? I still don't know the answer to this.
Sorry if these are documented and I missed them.
Bruce.
Suggested Articles
Not using installed JRE
I'm using the Media / JRE Folder to bundle a JVM with the application.
When I run the installer on a machine with no pre-existing JVM, the install works fine and I can see the JVM (and JAI, which was installed in the bundled JVM I used) inside my application folder.
However, when I try to launch the application, I immediately get an error stating that no valid JVM can be found, and asking that I go and download one.
I played with the version restrictions to the point I'm convinced that's not the issue.
I am using a shortcut to launch the application, because we need to pass command-line params. Could it be that the shortcut doesn't know to use the bundled JVM instead of a registered JVM?
When I run the installer on a machine with no pre-existing JVM, the install works fine and I can see the JVM (and JAI, which was installed in the bundled JVM I used) inside my application folder.
However, when I try to launch the application, I immediately get an error stating that no valid JVM can be found, and asking that I go and download one.
I played with the version restrictions to the point I'm convinced that's not the issue.
I am using a shortcut to launch the application, because we need to pass command-line params. Could it be that the shortcut doesn't know to use the bundled JVM instead of a registered JVM?
possibly the JVM type setting?
I cannot understand from the documentation what the Client and Server JVMs mean in Favor Client, Favor Server, Server Only.
It seems when I use Client JVM and an MSI, the installer works, more or less, but when I use Server JVM and an exe, the installer fails to find the installed JVM.
Does that make sense?
It seems when I use Client JVM and an MSI, the installer works, more or less, but when I use Server JVM and an exe, the installer fails to find the installed JVM.
Does that make sense?
Hi,
We couldn't reproduce your problem. If the minimum and maximum version are correctly set there shouldn't be any trouble.
If you bundle the JRE with your package the application should find it no matter if you launch it using a shortcut.
If possible, could you send the AIP to support at advancedinstaller dot com? We will then try to figure out the problem.
Also could you provide a location where we could download the MSI that has these problems?
Regarding the second question, the Client and Server refer to the JVM (jvm.dll) present in the jdkx.x.x\jre\bin\client and jdkx.x.x\jre\bin\server\ folders, where x.x.x stands for the JDK version. If the Server option doesn't work is probably you don't have JDK installed, only "simple" JRE, that comes just with the Client type.
The type of the package (EXE or MSI) doesn't have anything to do with this.
Regards,
Mihai
We couldn't reproduce your problem. If the minimum and maximum version are correctly set there shouldn't be any trouble.
If you bundle the JRE with your package the application should find it no matter if you launch it using a shortcut.
If possible, could you send the AIP to support at advancedinstaller dot com? We will then try to figure out the problem.
Also could you provide a location where we could download the MSI that has these problems?
Regarding the second question, the Client and Server refer to the JVM (jvm.dll) present in the jdkx.x.x\jre\bin\client and jdkx.x.x\jre\bin\server\ folders, where x.x.x stands for the JDK version. If the Server option doesn't work is probably you don't have JDK installed, only "simple" JRE, that comes just with the Client type.
The type of the package (EXE or MSI) doesn't have anything to do with this.
Regards,
Mihai
Last edited by Mike on Tue Oct 25, 2005 8:16 am, edited 2 times in total.
The Client vs Server JVM issue I believe explains the difficulty I was having.
I misinterpreted it to represent the difference between the JVM on the install machine vs. the JVM on the server building the installer.
Now that I have switched to using Prefer Client (we are only bundling the JRE) it seems to find the JVM correctly each time.
--Sean
I misinterpreted it to represent the difference between the JVM on the install machine vs. the JVM on the server building the installer.
Now that I have switched to using Prefer Client (we are only bundling the JRE) it seems to find the JVM correctly each time.
--Sean