In my configuration files, I'm trying to use a <cfg:shell> element that invokes a batch file (on Windows - it would be a shell script on another platform). This batch file needs to make use of a system environment variable that was added by an installation package.
I noticed that while newly created command prompts know about the new environment variable, the batch file run from XXE does not. Stopping and restarting XXE made no difference. It was not until I rebooted the computer that the command prompt created by the <cfg:shell> element knew about the new environment variable. This makes me wonder if the real problem is somehow Java related, but a search on the Internet did not help me discover anything. Does anyone have an idea as to what the problem may be? (Yes, I know that forcing all my users to reboot after they run the installation package would solve the problem, but I'm really trying to avoid that.) Thanks, --Andy
