Cross-cutting concerns concept in Spring Boot - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Spring Boot aspect for logging.

Spring Boot

import org.aspectj.lang.annotation.[1];

@Aspect
public class LoggingAspect {
    // aspect code
}

Drag options to blanks, or click blank then click option'

AComponent

BAspect

CService

DRepository

Attempts:

3 left

💡 Hint

Common Mistakes

Using @Component instead of @Aspect

Forgetting to import the correct annotation

The @Aspect annotation marks the class as an aspect for cross-cutting concerns like logging.

2fill in blank

medium

Complete the code to define a pointcut expression for all methods in service package.

Spring Boot

@Pointcut("execution(* com.example.service..*[1]*(..))")
public void serviceMethods() {}

Drag options to blanks, or click blank then click option'

A.

B+

C*

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using '*' which results in ..*** a non-standard pattern

Using '+' which is used for subclass matching in parameters

The . separates the class name pattern * from the method name pattern * in the execution pointcut.

3fill in blank

hard

Fix the error in the advice annotation to run before methods matched by pointcut.

Spring Boot

@[1]("serviceMethods()")
public void beforeAdvice() {
    System.out.println("Before method execution");
}

Drag options to blanks, or click blank then click option'

ABefore

BAfter

CAround

DPointcut

Attempts:

3 left

💡 Hint

Common Mistakes

Using @After instead of @Before

Using @Pointcut instead of advice annotation

The @Before annotation runs advice before the matched methods.

4fill in blank

hard

Fill both blanks to create an aspect that logs method execution time.

Spring Boot

public @[1] class PerformanceAspect {

    @Around("execution(* com.example..*.*(..))")
    public Object logExecutionTime(ProceedingJoinPoint joinPoint) throws Throwable {
        long start = System.currentTimeMillis();
        Object proceed = joinPoint.[2]();
        long executionTime = System.currentTimeMillis() - start;
        System.out.println(joinPoint.getSignature() + " executed in " + executionTime + "ms");
        return proceed;
    }
}

Drag options to blanks, or click blank then click option'

AAspect

BComponent

Cproceed

Dproceed()

Attempts:

3 left

💡 Hint

Common Mistakes

Using @Component instead of @Aspect

Calling proceed without parentheses

The class must be annotated with @Aspect to define an aspect. The method proceed() runs the original method.

5fill in blank

hard

Fill all three blanks to define a Spring bean for an aspect with logging advice.

Spring Boot

@[1]
public class LoggingAspect {

    @[2]("execution(* com.example..*.*(..))")
    public void logBefore() {
        System.out.println("Method called");
    }

    @Bean
    public LoggingAspect [3]() {
        return new LoggingAspect();
    }
}

Drag options to blanks, or click blank then click option'

AAspect

BBefore

CloggingAspect

DComponent

Attempts:

3 left

💡 Hint

Common Mistakes

Using @Component instead of @Aspect

Using @After instead of @Before

Naming the bean method with uppercase letters

The class must be annotated with @Aspect to define an aspect. The advice uses @Before. The bean method name is usually camelCase.

Practice

1. What is the main purpose of cross-cutting concerns in a Spring Boot application?

easy

A. To manage database connections and queries

B. To define the main business logic of the application

C. To create user interface components

D. To handle common tasks like logging and security across multiple parts of the app

Solution

1. Step 1: Understand the role of cross-cutting concerns

   Cross-cutting concerns are tasks that affect many parts of an application, such as logging, security, or transaction management.

2. Step 2: Identify their purpose in Spring Boot

   Spring Boot uses cross-cutting concerns to keep these common tasks separate from business logic, improving code clarity and reuse.

3. Final Answer:

   To handle common tasks like logging and security across multiple parts of the app -> Option D

4. Quick Check:

   Cross-cutting concerns = common tasks across app [OK]

Hint: Cross-cutting concerns handle shared tasks across many parts [OK]

Common Mistakes:

• Confusing cross-cutting concerns with main business logic
• Thinking they manage database or UI directly
• Assuming they are only for security

2. Which annotation is used in Spring Boot to define an aspect for cross-cutting concerns?

easy

A. @Aspect

B. @Controller

C. @Service

D. @Repository

Solution

1. Step 1: Recall Spring AOP annotations

   Spring Boot uses Aspect-Oriented Programming (AOP) to implement cross-cutting concerns, and the key annotation to define an aspect is @Aspect.

2. Step 2: Differentiate from other annotations

   @Controller is for web controllers, @Service for service layer, and @Repository for data access. None of these define aspects.

3. Final Answer:

   @Aspect -> Option A

4. Quick Check:

   Aspect annotation = @Aspect [OK]

Hint: Use @Aspect to mark cross-cutting concern classes [OK]

Common Mistakes:

• Choosing @Controller or @Service by mistake
• Confusing @Aspect with @Component
• Not knowing which annotation defines an aspect

3. Given this Spring Boot aspect code snippet:

@Aspect
public class LoggingAspect {
  @Before("execution(* com.example.service.*.*(..))")
  public void logBefore() {
    System.out.println("Method called");
  }
}

What will happen when a method in com.example.service package is called?

medium

A. The message "Method called" will print after the method executes

B. The message "Method called" will print before the method executes

C. No message will print because the pointcut is incorrect

D. The method call will be blocked and not executed

Solution

1. Step 1: Understand the @Before advice

   The @Before annotation means the method logBefore() runs before the matched method executes.

2. Step 2: Analyze the pointcut expression

   The pointcut execution(* com.example.service.*.*(..)) matches any method in any class inside com.example.service package.

3. Final Answer:

   The message "Method called" will print before the method executes -> Option B

4. Quick Check:

   @Before advice prints message before method [OK]

Hint: @Before runs code before matched methods [OK]

Common Mistakes:

• Confusing @Before with @After advice
• Thinking pointcut matches other packages
• Assuming method is blocked

4. Identify the error in this Spring Boot aspect code:

@Aspect
public class SecurityAspect {
  @Before("execution(* com.example..*(..))")
  public void checkSecurity() {
    // security check code
  }
}

medium

A. The pointcut expression syntax is invalid

B. The method name must start with 'validate'

C. The advice method must return a value

D. The class is missing @Component or @Configuration annotation

Solution

1. Step 1: Examine the pointcut expression

   The pointcut execution(* com.example..*(..)) has invalid syntax because it is missing the method name pattern .*. Correct syntax is execution(* com.example..*.*(..)) to match any method in com.example package and subpackages.

2. Step 2: Rule out other options

   Advice methods can be void and have any name; missing bean annotation is secondary.

3. Final Answer:

   The pointcut expression syntax is invalid -> Option A

4. Quick Check:

   Pointcut requires .* for method pattern [OK]

Hint: Pointcut syntax: execution(* pkg..*.*(..)) [OK]

Common Mistakes:

• Thinking it's missing @Component annotation
• Believing method name must start with 'validate'
• Assuming advice must return a value

5. You want to apply a logging aspect only to methods annotated with @Transactional in your Spring Boot app. Which pointcut expression correctly targets these methods?

hard

A. execution(@Transactional * *(..))

B. within(@Transactional *)

C. @annotation(org.springframework.transaction.annotation.Transactional)

D. args(@Transactional)

Solution

1. Step 1: Understand pointcut for annotations

   To target methods with a specific annotation, Spring AOP uses the @annotation pointcut designator with the full annotation class name.

2. Step 2: Evaluate options

   @annotation(org.springframework.transaction.annotation.Transactional) uses @annotation(org.springframework.transaction.annotation.Transactional), which correctly matches methods annotated with @Transactional. Other options are invalid or incorrect syntax.

3. Final Answer:

   @annotation(org.springframework.transaction.annotation.Transactional) -> Option C

4. Quick Check:

   Use @annotation for method-level annotation matching [OK]

Hint: Use @annotation with full annotation class for method targeting [OK]

Common Mistakes:

• Using execution with annotation incorrectly
• Confusing within and args pointcuts
• Not specifying full annotation package