`@Controller`

See equivalent in the Servlet stackspring-doc.cn

You can define controller beans by using a standard Spring bean definition. The @Controller stereotype allows for auto-detection and is aligned with Spring general support for detecting @Component classes in the classpath and auto-registering bean definitions for them. It also acts as a stereotype for the annotated class, indicating its role as a web component.spring-doc.cn

To enable auto-detection of such @Controller beans, you can add component scanning to your Java configuration, as the following example shows:spring-doc.cn

Javaspring-doc.cn
Kotlinspring-doc.cn

@Configuration
@ComponentScan("org.example.web") (1)
public class WebConfiguration {

	// ...
}

1	Scan the `org.example.web` package.

@Configuration
@ComponentScan("org.example.web") (1)
class WebConfiguration {

	// ...
}

1	Scan the `org.example.web` package.

@RestController is a composed annotation that is itself meta-annotated with @Controller and @ResponseBody, indicating a controller whose every method inherits the type-level @ResponseBody annotation and, therefore, writes directly to the response body versus view resolution and rendering with an HTML template.spring-doc.cn

AOP Proxies

See equivalent in the Servlet stackspring-doc.cn

In some cases, you may need to decorate a controller with an AOP proxy at runtime. One example is if you choose to have @Transactional annotations directly on the controller. When this is the case, for controllers specifically, we recommend using class-based proxying. This is automatically the case with such annotations directly on the controller.spring-doc.cn

If the controller implements an interface, and needs AOP proxying, you may need to explicitly configure class-based proxying. For example, with @EnableTransactionManagement you can change to @EnableTransactionManagement(proxyTargetClass = true), and with <tx:annotation-driven/> you can change to <tx:annotation-driven proxy-target-class="true"/>.spring-doc.cn

Keep in mind that as of 6.0, with interface proxying, Spring WebFlux no longer detects controllers based solely on a type-level @RequestMapping annotation on the interface. Please, enable class based proxying, or otherwise the interface must also have an @Controller annotation.