Ranchers,
Does anyone out there know of a way to enforce the default
java security policy without having to manually include it as a system property on the command line argument when starting an instance of the JVM?
I've been starting it like this:
java -Djava.security.manager TestClient
This works but what if someone started the TestClient without the -Djava.security.manager all bets are off!
What I want to do is enforce any code run on a particular system, irrespective of how the JVM was invoked, to use the default security manager. I can ensure that only one instance of the JRE is loaded on the system.
Is this doable?
Any assisatance greatly appreciated...
TIA,
Mario