开发者

Annotated Spring @Controller also as Bean?

开发者 https://www.devze.com 2023-03-02 14:57 出处:网络
Can an annotated Spring MVC Control开发者_运维技巧ler also be annotated with @Component/@Service type of annotations and be used both as a controller and as a bean?Edit: placing more emphasis on the s

Can an annotated Spring MVC Control开发者_运维技巧ler also be annotated with @Component/@Service type of annotations and be used both as a controller and as a bean?


Edit: placing more emphasis on the software design aspect, and updating the API link to SpringV3

As mentioned in other answers, this is not an ideal approach to Spring MVC, but nevertheless the controller will already be available for autowiring in your ApplicationContext.

It's already a Bean in your ApplicationContext, so you can auto-wire it by type. There's no need to add an @Component annotation.

From the Spring API Docs: "This annotation serves as a specialization of @Component, allowing for implementation classes to be autodetected through classpath scanning."

http://static.springsource.org/spring/docs/3.0.x/api/org/springframework/stereotype/Controller.html

The same holds true for @Service.

Although I've done it myself, I would not normally recommend this design approach.

If possible, refactor the required functionality into a separate bean, which can then be (auto-)wired into both the @Controller, and any other bean, as required.

If, as you have commented, you are 'cornered' into this decision (as I was, by previous design choices), then so be it.

HTH


It can but it shouldn't. A web controller should be an entry point, nothing else.

Any reusable logic it performs should be in a dedicated service layer, not in the controller itself


No, sounds like it's doing too much. One or the other, not both. I don't know if it's possible (I doubt it), but I'm sure it's not advisable.


I think that you should hear more about patterns like Front Controller, MVC, DAO and Multitier architecture and so on.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号