Developers no longer need to call the SecurityManager from their code

843811

At least this is what I was told happens in 1.4. The class loader looks at the policy file and adds security manager call backs to classes at the appropriate points. I am also told that to cope with this the policy file has been extended to include ... well... more.

I can't find anything about this anywhere and to be honest I'm a bit sceptical.... but I have a meeting to go to tomorrow where this theory may re-emerge.

843811

Yes - the AccessController is now the preferred security "checker" (as of Java 2 security) -- lots of info on this under 1.4, in Li Gong's new (old) book etc.... perhaps just going to the security index page

http://java.sun.com/j2se/1.4/docs/guide/security/