Re: [Wrapper-user] does wrapper depend on JAVA_HOME?

[Leif M. <le...@ta...>]

Eugen,
The Wrapper does not do anything with the JAVA_HOME environment
variable. As long as you are not referencing it in your wrapper.conf file
then there is also no way for the application running the JVM to reference
it.
JAVA_HOME is usually passed to the JVM using a system property like:

-Djavahome=%JAVA_HOME%

It is perfectly safe to do the following:
wrapper.java.command=../jre/bin/java

One option is to define the JAVA_HOME environment variable within
your wrapper.conf file as follows:

set.JAVA_HOME=../jre
wrapper.java.command=%JAVA_HOME%/bin/java

This has the benefit of making it easy to reference the JRE location
throughout your wrapper.conf file. The user can also use a system
value by simply commenting out the set line.

Cheers,
Leif



Cocalea, Eugen wrote:

> Hello,
>
> This is a bit tricky, because not even me know what the question is about.
>
> I have a java application that I want to run as a windows service and
> I use wrapper to do this.
>
> My app wrapper.conf used to have
>
> wrapper.java.command=%JAVA_HOME%/bin/java
>
> The problem is that I have to run different versions of the
> application, that are certified against different JREs.
>
> So, my question is: if I hardcode the path to the JRE I need in
> wrapper.java.command, do I need to check anything else to see if the
> application really uses that JRE?
>
> Example:
>
> - JAVA_HOME points to JRE 1.3
>
> - I need to run the app with JRE 1.4
>
> - wrapper.java.command is <JRE1.4_install_path>/bin/java
>
> I should be safe, correct? *_Assuming my application doesn't use
> JAVA_HOME._*
>