|
From: Hubert F. <Hub...@ab...> - 2007-10-05 11:04:20
|
Did you try:
wrapper.java.library.path.append_system_path=3Dtrue
in the config file?
hth
hub
>>> Thorsten Lampe <kar...@ya...> 05.10.2007 12:59 >>>
I installed a service using a local account (namely Administrator for =
testing purposes) and have experienced that afterwards calling
System.getEnv().get("PATH")
(or a system call "set %PATH%" from within my Java application)
returns only the PATH variable exactly as defined in the Administrator's =
variables - whereas I would have expected the standard Windows behavior of =
appending Administrator's PATH to the system PATH.
Can anyone tell me why this happens when using the service wrapper? Or is =
this the default Windows behavior when starting any service using a local =
user account?
The problem resulting for my app is that it makes an external system call =
to a batch file of a third-party product which, in turn, expects java.exe =
to be on the PATH. Now when I start my Java application manually everything=
runs fine (since "C:\Windows\system32" is on the (global system) PATH and =
JRE copies its java.exe there) but using the service wrapper it fails =
because the batch file started from within my Java app cannot locate =
java.exe on the PATH (which is now cut down to the Administrator user =
PATH).
While I could, of course, include the java home dir to the user PATH or =
modify the batch file telling it where to find java, I would not really =
want to do this since it implies yet another adjustment to make on any =
system where my application will be installed.
Any help is appreciated.
Thorsten
Die etwas anderen Infos rund um das Thema Reisen. BE A BETTER =
WELTENBUMMLER! www.yahoo.de/clever
|