Blogs by topic Programming and user monika_krug
| • Accessibility | • Ajax | • Blogging | • Business | • Community |
| • Databases | • Deployment | • Distributed | • Eclipse | • Education |
| • EJB | • Extreme Programming | • Games | • GlassFish | • Grid |
| • GUI | • IDE | • Instant Messaging | • J2EE | • J2ME |
| • J2SE | • Jakarta | • JavaFX | • JavaOne | • Jini |
| • JSP | • JSR | • JXTA | • LDAP | • Linux |
| • Mobility | • NetBeans | • Open Source | • OpenSolaris | • OSGi |
| • P2P | • Patterns | • Performance | • Porting | • Programming |
| • Research | • RMI | • RSS Feeds | • Search | • Security |
| • Servlets | • Struts | • Swing | • Testing | • Tools |
| • Virtual Machine | • Web Applications | • Web Design | • Web Development Tools | • Web Services and XML |
Programming
Sometimes private is not enough. You would like to prevent directly setting a member variable even from within the same class. This can be done with AspectJ.
One of the features requested in the Mustang forum was a modifier that would allow a member variable to be inherited as if it were protected, but not to be accessed by the other classes from the package. Here is how to achieve the same with AspectJ.
Aspect Oriented Development is all about the DRY principle: Don't repeat yourself! Or, as it is usually put, it's about "separating crosscutting concerns".
