Pointcut expressions in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a pointcut expression in Spring AOP?

A pointcut expression defines where advice should be applied by matching method executions or join points in the code.

beginner

Explain the use of the execution() designator in pointcut expressions.

The execution() designator matches method executions based on method signature patterns like return type, method name, and parameters.

intermediate

What does the pointcut expression execution(* com.example.service.*.*(..)) mean?

It matches the execution of any method with any return type, in any class inside the <code>com.example.service</code> package, with any number of arguments.

intermediate

How can you combine multiple pointcut expressions?

You can combine pointcuts using logical operators like && (and), || (or), and ! (not) to create complex matching rules.

beginner

What is the role of wildcards (*) and double dots (..) in pointcut expressions?

The wildcard * matches any single part like a method name or type, while .. matches any number of parameters or sub-packages.

Which pointcut designator matches method executions by signature?

A this()

B within()

C execution()

D args()

The execution() designator matches method executions based on method signatures.

What does the wildcard * represent in a pointcut expression?

A No match

B Any number of parameters

C Any sub-package

D Any single part like a method name or type

The * wildcard matches any single part such as a method name or type.

How do you exclude a pointcut from another using logical operators?

A !

B ||

C &&

D ==

The ! operator negates a pointcut, effectively excluding it.

Which expression matches all methods in a package and its sub-packages?

A execution(* com.example..*.*(..))

B execution(* com.example.*.*(..))

C within(com.example.*)

D args(com.example..*)

The double dot .. matches sub-packages, so com.example..* includes all sub-packages.

What does execution(public * *(..)) match?

A Any method with no parameters

B Any public method with any return type and any parameters

C Only private methods

D Only methods returning void

It matches any public method regardless of return type or parameters.

Describe how pointcut expressions help in applying advice in Spring AOP.

Think about how you tell Spring where to run extra code.

Explain the difference between the wildcards * and .. in pointcut expressions.

One is for single parts, the other for multiple parts.

Practice

1. What does a pointcut expression in Spring Boot primarily do?

easy

A. Create new methods dynamically at runtime

B. Define the database connection settings

C. Select methods where extra code (advice) should run

D. Replace existing methods with new implementations

Solution

1. Step 1: Understand the purpose of pointcut expressions

   Pointcut expressions specify where additional code, called advice, should be applied in existing methods without changing those methods.

2. Step 2: Differentiate from other concepts

   They do not create or replace methods, nor configure databases. Their role is to select join points (methods) for advice.

3. Final Answer:

   Select methods where extra code (advice) should run -> Option C

4. Quick Check:

   Pointcut expression = Select methods for advice [OK]

Hint: Pointcuts pick methods to add code without changing them [OK]

Common Mistakes:

• Confusing pointcuts with method creation
• Thinking pointcuts configure databases
• Believing pointcuts replace method code

2. Which of the following is the correct syntax to match all methods in package com.example.service using a pointcut expression?

easy

A. execution(* com.example.service..*(..))

B. execution(com.example.service.*.*(..))

C. execution(* com.example.service.*(..))

D. execution(* com.example.service.*.*(..))

Solution

1. Step 1: Understand the execution syntax

   The syntax execution(* com.example.service.*.*(..)) matches any return type, any class in the package com.example.service, and any method with any parameters.

2. Step 2: Analyze other options

   execution(com.example.service.*.*(..)) misses the wildcard for return type. execution(* com.example.service..*(..)) uses double dot .. which matches subpackages, not just the package. execution(* com.example.service.*(..)) misses the class wildcard.

3. Final Answer:

   execution(* com.example.service.*.*(..)) -> Option D

4. Quick Check:

   Use * for any class and method in package [OK]

Hint: Use * for any class and method in a package [OK]

Common Mistakes:

• Omitting the return type wildcard *
• Using .. instead of * for classes
• Missing method wildcard *

3. Given the pointcut expression execution(public * com.example.repo.*Repository.find*(..)), which methods will it match?

medium

A. All methods named 'find' in any class in com.example.repo

B. All public methods starting with 'find' in any class ending with 'Repository' in package com.example.repo

C. All public methods in any class in com.example.repo

D. Only methods named exactly 'find' in any class ending with 'Repository'

Solution

1. Step 1: Break down the expression

   public * means any public return type, com.example.repo.*Repository matches classes ending with 'Repository' in the package, and find*(..) matches methods starting with 'find' with any parameters.

2. Step 2: Match options to expression meaning

   All public methods starting with 'find' in any class ending with 'Repository' in package com.example.repo correctly describes all public methods starting with 'find' in classes ending with 'Repository' in the package. Others are either too broad or too narrow.

3. Final Answer:

   All public methods starting with 'find' in any class ending with 'Repository' in package com.example.repo -> Option B

4. Quick Check:

   execution(public * com.example.repo.*Repository.find*(..)) = All public methods starting with 'find' in any class ending with 'Repository' in package com.example.repo [OK]

Hint: Look for wildcards * and method name patterns carefully [OK]

Common Mistakes:

• Ignoring method name prefix 'find*'
• Confusing class name pattern *Repository
• Missing public modifier effect

4. Identify the error in this pointcut expression: execution(* com.example..service.*(..)

medium

A. Missing closing parenthesis at the end

B. Incorrect use of double dots '..' in package name

C. Wildcard '*' cannot be used for method names

D. Return type '*' is invalid

Solution

1. Step 1: Check syntax completeness

   The expression is missing a closing parenthesis ')' at the end, which is required to close the execution() expression.

2. Step 2: Validate other parts

   Double dots '..' are valid to match subpackages, '*' is valid for method names, and '*' is valid for return type.

3. Final Answer:

   Missing closing parenthesis at the end -> Option A

4. Quick Check:

   Check parentheses balance in execution() [OK]

Hint: Count parentheses carefully in pointcut expressions [OK]

Common Mistakes:

• Forgetting closing parenthesis
• Misunderstanding '..' usage
• Thinking '*' is invalid for methods or return types

5. You want to create a pointcut expression that matches all methods in any class within com.app.service and its subpackages, but only methods that have exactly two parameters of any type. Which expression is correct?

hard

A. execution(* com.app.service..*.*(*, *))

B. execution(* com.app.service.*.*(..))

C. execution(* com.app.service..*.*(.., ..))

D. execution(* com.app.service..*.*(*))

Solution

1. Step 1: Understand package and subpackage matching

   com.app.service..* matches classes in the package and all subpackages.

2. Step 2: Match method parameters exactly

   (* , *) means exactly two parameters of any type. (..) means any number of parameters, so it's incorrect here.

3. Step 3: Analyze options

   execution(* com.app.service..*.*(*, *)) correctly matches all classes in package and subpackages with exactly two parameters. Others either match any number of parameters or wrong parameter counts.

4. Final Answer:

   execution(* com.app.service..*.*(*, *)) -> Option A

5. Quick Check:

   Use (*, *) for exactly two parameters [OK]

Hint: Use (*, *) to match exactly two parameters [OK]

Common Mistakes:

• Using (..) to match exact parameter count
• Confusing single * with .. for subpackages
• Missing commas between parameters