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 Delivery

  Learn More!

Sponsored Links

Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs

Taming Tiger, Part 3

Decorate your code with Java annotations

By Tarak Modi, JavaWorld.com, 07/19/04

Page 4 of 4

1. The first thread (role set to "HR") has access only to the unRestrictedMethod() and partiallyRestrictedMethod2() methods.
2. The second thread (role set to "Manager") has access to the unRestrictedMethod(), partiallyRestrictedMethod(), and partiallyRestrictedMethod2() methods.
3. Neither thread has access to the fullyRestrictedMethod() method.
4. Both threads can access the unRestrictedMethod() method.
5. Both threads were able to create an instance of the AnnotationsTest class because the class was annotated with the SecurityPermission annotation SecurityPermission("All"). If All was changed to None, then neither thread could have created an instance of the class.

The best way to see what's going on is to play around with the code and change the values of the various SecurityPermission annotations that are sprinkled around the AnnotationsTest class.

Finally, an awesome exercise would be to use AspectJ to define and implement the appropriate pointcuts that would allow you to completely remove the manual call to SecurityBlanket.checkPermission() from your code. Now that would be real "magic," and AspectJ makes it easy.

Conclusion

This concludes my three-part series on J2SE 5. Along the way, I have covered many interesting new language features, some more useful than others. I talked at length about the new Java metadata facility called annotations in this article. Annotations provide us with a host of new capabilities. Expect to see many tools in the next couple of years that capitalize on Java annotations to provide new value-added services either at compile time by code modification or at runtime.

About the author