|
|
Recommended: Sing it, brah! 5 fabulous songs for developers
JW's Top 5
Featured White Papers
- Measuring Risk to Improve Java Software Quality
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Sponsored Links
-
Graph databases are 1000x faster than relational.
Learn More!
-
Career opportunities at Harman- Careers That'll Rock Your Socks Off.
Learn More!
-
Developer-friendly Java PDF libraries by Qoppa Software
Live Demos
-
Stop blaming your app! Diagnose Java performance issues.
Free tool >
-
UrbanCode: Go From Continuous Integration to
Continuous DeliveryLearn More!
Limited mainly to untrusted applets
Submitted by metatech on Fri, 09/02/2011 - 10:13.
Tags:
Back to:
www.javaworld.com/javaworld/jw-12-1998/jw-12-securityrules.html.
Although the article does not mention it explicitly, these recommndations are primarily aimed for applications running as untrusted applets in a browser. Trusted applets or applications using the normal system classpath (Java desktop applications or Java EE applications) can anyway use the Java reflection API to bypass most of those restrictions (by calling for instance "setAccessible").
About Us | Advertise | Contact Us | Terms of Service/Privacy | AdChoices
Copyright, 2006-2013 Infoworld, Inc. All rights reserved.