Polish documentation for stereotype names

This commit is contained in:
Sam Brannen
2016-06-08 14:38:51 +02:00
parent c9de6f23ef
commit da051b87e6

View File

@@ -5402,9 +5402,9 @@ and the equivalent using XML
[NOTE]
====
You can also disable the default filters by setting `useDefaultFilters=false` on the annotation or
providing `use-default-filters="false"` as an attribute of the <component-scan/> element. This
providing `use-default-filters="false"` as an attribute of the `<component-scan/>` element. This
will in effect disable automatic detection of classes annotated with `@Component`, `@Repository`,
`@Service`, or `@Controller`.
`@Service`, `@Controller`, or `@Configuration`.
====
@@ -5551,14 +5551,14 @@ analogous to how the container selects between multiple `@Autowired` constructor
When a component is autodetected as part of the scanning process, its bean name is
generated by the `BeanNameGenerator` strategy known to that scanner. By default, any
Spring stereotype annotation ( `@Component`, `@Repository`, `@Service`, and
`@Controller`) that contains a `name` value will thereby provide that name to the
Spring stereotype annotation (`@Component`, `@Repository`, `@Service`, and
`@Controller`) that contains a _name_ `value` will thereby provide that name to the
corresponding bean definition.
If such an annotation contains no `name` value or for any other detected component (such
If such an annotation contains no _name_ `value` or for any other detected component (such
as those discovered by custom filters), the default bean name generator returns the
uncapitalized non-qualified class name. For example, if the following two components
were detected, the names would be myMovieLister and movieFinderImpl:
were detected, the names would be `myMovieLister` and `movieFinderImpl`:
[source,java,indent=0]
[subs="verbatim,quotes"]
@@ -5910,7 +5910,7 @@ Please use Spring's stereotype model for building custom component annotations.
[[beans-standard-annotations-limitations]]
=== Limitations of the standard approach
=== Limitations of JSR-330 standard annotations
When working with standard annotations, it is important to know that some significant
features are not available as shown in the table below: