root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 8 Packages Projects Releases Wiki Activity

Fix URL to Spring Tool Suite 

See gh-24589
This commit is contained in:
陈其苗 2020-02-25 19:21:03 +08:00 committed by Rossen Stoyanchev
parent 2afae430eb
commit 771fbde951
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/docs/asciidoc/core/core-beans.adoc
View File

@ -74,7 +74,7 @@ In most application scenarios, explicit user code is not required to instantiate
more instances of a Spring IoC container. For example, in a web application scenario, a
simple eight (or so) lines of boilerplate web descriptor XML in the `web.xml` file
of the application typically suffices (see <<context-create>>). If you use the
https://spring.io/tools/sts[Spring Tool Suite] (an Eclipse-powered development
https://spring.io/tools[Spring Tool Suite] (an Eclipse-powered development
environment), you can easily create this boilerplate configuration with a few mouse clicks or
keystrokes.
@ -1481,7 +1481,7 @@ XML configuration:
The preceding XML is more succinct. However, typos are discovered at runtime rather than
design time, unless you use an IDE (such as https://www.jetbrains.com/idea/[IntelliJ
IDEA] or the https://spring.io/tools/sts[Spring Tool Suite])
IDEA] or the https://spring.io/tools[Spring Tool Suite])
that supports automatic property completion when you create bean definitions. Such IDE
assistance is highly recommended.
@ -4649,7 +4649,7 @@ No matter the choice, Spring can accommodate both styles and even mix them toget
It is worth pointing out that through its <<beans-java, JavaConfig>> option, Spring lets
annotations be used in a non-invasive way, without touching the target components
source code and that, in terms of tooling, all configuration styles are supported by the
https://spring.io/tools/sts[Spring Tool Suite].
https://spring.io/tools[Spring Tool Suite].
****
An alternative to XML setup is provided by annotation-based configuration, which relies on
@ -8985,7 +8985,7 @@ modularity, but determining exactly where the autowired bean definitions are dec
still somewhat ambiguous. For example, as a developer looking at `ServiceConfig`, how do
you know exactly where the `@Autowired AccountRepository` bean is declared? It is not
explicit in the code, and this may be just fine. Remember that the
https://spring.io/tools/sts[Spring Tool Suite] provides tooling that
https://spring.io/tools[Spring Tool Suite] provides tooling that
can render graphs showing how everything is wired, which may be all you need. Also,
your Java IDE can easily find all declarations and uses of the `AccountRepository` type
and quickly show you the location of `@Bean` methods that return that type.