Hi Roland,

You would need SWV 6.1 with the Isolation feature to work by default however; it's not released yet.
I don't know if you either could have a copy of the javaw.exe in the "reader" layer or if it's possible to point the path where the javaw.exe executable is located within the "reader" layer (guess it would depend on the configuration possibility within the reader application).

Which application is it, do we know it?

I don't want to isolate, but the idea of having a copy of the javaw.exe file in the app layer sound nice. I'm going to try that one out. I guess the only downside of having that file in the app layer is that it needs to be updated as soon as there's a new java version being deployed.

I don't think that it is a common known application. It's called VSS Reader. You'll find the setup here.

Thanks for your great support AngelD.

Easier way to get this all done.

So you've got two layers, one with the app and one with the JRE correct?  And you want to make sure the Java layer is active when you run the program that requires it (I've never seen a java.exe that won't auto launch but I'm not super familiar with Java)?

Use onevent notifications to set this all up, you can use on post Activate to make sure the other layer is active (and if you want make it so the java.exe launches).

SWV does have isolation, but you only need that if you need more then one version of Java running at the same time, with only one instance isolation isn't needed.

Oh thought we were talking about different java versions :d

Jordan,
If I recall correct, didn't someone create a tool to handle layer dependencies a while ago on the old Juice site (should have been migrated to connect)?

yes.  SWV adds dependences as well but all they do is make sure a specific layer is activate and not that the content inside the layer is running (though there are many ways to do that like placing a shortcut in the startup folder) after an activate.

We have no problems with Java so far (only one version in house and the layer is set to auto-activate). And the javaw.exe starts fine even though it's in a different layer. So I neither need isolation nor an OnEventAction.

The only problem I've got is that the app (when in use) is running in our JRE layer (through starting the javaw.exe from that layer). And thus settings from inside the app layer have no effect.

I'll try the workaround AngelD proposed, to include the same javaw.exe in the app layer.

Sorry for misleading you guys and thanks for your ongoing support!