AspectJ Notes: Aspect Oriented Programming allows you to achieve an extra level of separation of concerns ontop of OOP methodology.<\/p>\n
Key terms:
\n– Pointcut defines wherein the code a joinpoint (injection is what they should’ve called it) will occur.
\n– Advice defines what happens at the specific joinpoint.
\n– Weaving is the process of injecting the advice into the joinpoints.<\/p>\n
Example code:<\/p>\n
\t\/\/ playing with this to see if I can get this to work \tpointcut test(): target(Main) && \tafter(): test(){ \tpointcut test2(): target(Main) && \tbefore(): test2(){ }<\/code><\/p>\npublic aspect LicenseFee {<\/p>\n
\n\t\/\/ eclipse constantly checks to see if you actually are implementing the method before weaving occurs
\n\t\/\/ almost like it actively weaves before runtime, no wonder my computer is so slow running this thing
\n\t\/\/ so that means that when I go to run tests, some errors may occur but it should be okay\/runnable despite the fact<\/p>\n
\n\t\t\t(call(void testSaveAccount()));<\/p>\n
\n\t\tSystem.out.println(\"TestSaveAccount called\");
\n\t}<\/p>\n
\n\t\t\t(call(void testOpenAccount()));<\/p>\n
\n\t\tSystem.out.println(\"Derp\");
\n\t}<\/p>\n