> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/spring/spring-features/spring-aop/after-returning-advice.md).
# After Returning Advice
After returning advice is executed after the target method successfully returns a result. It allows to perform additional actions based on the returned result. Some of the use cases are described below.
**Logging**: It can be used to log method response. This can be helpful for debugging, auditing, or monitoring purposes.
**Notification**: It it can be used to trigger notification logic such as sending SMS, Email etc. after successful response.
#### Sample Examples
#### Scenario 1: Triggering SMS on the successful method invocation
Create custom annotation
***SmsOnSuccess.java***
```java
package org.example.sms;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
@Target(ElementType.METHOD) // Annotation will be applicable on methods only
@Retention(RetentionPolicy.RUNTIME) // Annotation will be available to the JVM at runtime
public @interface SmsOnSuccess {
}
```
Create Aspect class
***SmsOnSuccessAspect.class***
package org.example.sms;
import lombok.extern.slf4j.Slf4j;
import org.aspectj.lang.annotation.AfterReturning;
import org.aspectj.lang.annotation.Aspect;
import org.springframework.stereotype.Component;
@Slf4j
@Aspect
@Component
public class SmsOnSuccessAspect {
@AfterReturning("@annotation(SmsOnSuccess)")
public void sendSmsOnSuccess() {
log.info("Sending SMS...");
}
}
Controller Class
***PaymentApi.java***
```java
package org.example.controller;
import lombok.RequiredArgsConstructor;
import lombok.extern.slf4j.Slf4j;
import org.example.Model.Transaction;
import org.example.service.PaymentService;
import org.example.sms.SmsOnSuccess;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
@Slf4j
@RestController
@RequiredArgsConstructor
@RequestMapping("/payment")
public class PaymentApi {
private final PaymentService paymentService;
@SmsOnSuccess
@PostMapping("/process")
public ResponseEntity processTransaction(@RequestBody Transaction transaction) {
log.info("Started processing transaction {}", transaction);
paymentService.processPayment(transaction);
return ResponseEntity.accepted().build();
}
}
```
Run the application and trigger the API
Output
#### Scenario 2: Logging method response using pointcut expression
Create Aspect class
***LoggingAspect.java***
```java
package org.example.logging;
import lombok.extern.slf4j.Slf4j;
import org.aspectj.lang.JoinPoint;
import org.aspectj.lang.annotation.*;
import org.springframework.stereotype.Component;
@Slf4j
@Aspect
@Component
public class LoggingAspect {
private static final String AFTER_RETURNING_POINTCUT ="execution(* org.example.controller.*.*(..))";
@AfterReturning(pointcut = AFTER_RETURNING_POINTCUT, returning = "result")
public void logResponse(JoinPoint joinPoint, Object result) {
log.info("JoinPoint - {}", joinPoint);
log.info("Response - {}", result);
}
}
```
{% hint style="info" %}
Note that pointcut expression matches any class and any method defined under `org.example.controller` package
{% endhint %}
Create controller class
***DataApi.java***
```java
package org.example.controller;
import lombok.RequiredArgsConstructor;
import org.example.Model.InputData;
import org.example.Model.OutputData;
import org.example.service.DataService;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
@RestController
@RequiredArgsConstructor
@RequestMapping("/data")
public class DataApi {
private final DataService dataService;
@PostMapping("/extract")
public ResponseEntity getData(@RequestBody InputData inputData) {
return new ResponseEntity<>(
dataService.extractData(inputData),
HttpStatus.OK
);
}
}
```
Run the application, trigger the API and verify the logs
Output
{% hint style="info" %}
Note: The code snippet given in this page is just for understanding and does not contain complete code. (For e.g. missing service class code snippet)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://www.pranaypourkar.co.in/the-programmers-guide/spring/spring-features/spring-aop/after-returning-advice.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.