Replace 'e.g.' with 'for example' in documentation and comments
Closes gh-33515
This commit is contained in:
committed by
Sam Brannen
parent
e55fe9077f
commit
8941e2876e
@@ -343,14 +343,14 @@
|
||||
<!--
|
||||
The constructor-arg tag can have an optional index attribute,
|
||||
to specify the exact index in the constructor argument list. Only needed
|
||||
to avoid ambiguities, e.g. in case of 2 arguments of the same type.
|
||||
to avoid ambiguities, for example, in case of 2 arguments of the same type.
|
||||
-->
|
||||
<!ATTLIST constructor-arg index CDATA #IMPLIED>
|
||||
|
||||
<!--
|
||||
The constructor-arg tag can have an optional type attribute,
|
||||
to specify the exact type of the constructor argument. Only needed
|
||||
to avoid ambiguities, e.g. in case of 2 single argument constructors
|
||||
to avoid ambiguities, for example, in case of 2 single argument constructors
|
||||
that can both be converted from a String.
|
||||
-->
|
||||
<!ATTLIST constructor-arg type CDATA #IMPLIED>
|
||||
|
||||
@@ -90,7 +90,7 @@
|
||||
elements followed, etc. If none of the specified profiles are active at time of
|
||||
parsing, then the entire element and its contents will be ignored.
|
||||
|
||||
If a profile is prefixed with the NOT operator '!', e.g.
|
||||
If a profile is prefixed with the NOT operator '!', for example,
|
||||
|
||||
<beans profile="p1,!p2">
|
||||
|
||||
@@ -152,8 +152,8 @@
|
||||
<xsd:annotation>
|
||||
<xsd:documentation><![CDATA[
|
||||
A default bean name pattern for identifying autowire candidates:
|
||||
e.g. "*Service", "data*", "*Service*", "data*Service".
|
||||
Also accepts a comma-separated list of patterns: e.g. "*Service,*Dao".
|
||||
for example, "*Service", "data*", "*Service*", "data*Service".
|
||||
Also accepts a comma-separated list of patterns: for example, "*Service,*Dao".
|
||||
See the documentation for the 'autowire-candidate' attribute of the
|
||||
'bean' element for the semantic details of autowire candidate beans.
|
||||
]]></xsd:documentation>
|
||||
@@ -308,7 +308,7 @@
|
||||
|
||||
Singletons are most commonly used, and are ideal for multi-threaded
|
||||
service objects. Further scopes, such as "request" or "session", might
|
||||
be supported by extended bean factories (e.g. in a web environment).
|
||||
be supported by extended bean factories (for example, in a web environment).
|
||||
|
||||
Inner bean definitions inherit the scope of their containing bean
|
||||
definition, unless explicitly specified: The inner bean will be a
|
||||
@@ -341,7 +341,7 @@
|
||||
Hence, it needs to be specified per concrete bean definition. It can be
|
||||
shared through the 'default-lazy-init' attribute at the 'beans' level
|
||||
and potentially inherited from outer 'beans' defaults in case of nested
|
||||
'beans' sections (e.g. with different profiles).
|
||||
'beans' sections (for example, with different profiles).
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
@@ -389,7 +389,7 @@
|
||||
Hence, it needs to be specified per concrete bean definition. It can be
|
||||
shared through the 'default-autowire' attribute at the 'beans' level
|
||||
and potentially inherited from outer 'beans' defaults in case of nested
|
||||
'beans' sections (e.g. with different profiles).
|
||||
'beans' sections (for example, with different profiles).
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
<xsd:simpleType>
|
||||
@@ -595,7 +595,7 @@
|
||||
<xsd:annotation>
|
||||
<xsd:documentation><![CDATA[
|
||||
The exact index of the argument in the constructor argument list.
|
||||
Only needed to avoid ambiguities, e.g. in case of 2 arguments of
|
||||
Only needed to avoid ambiguities, for example, in case of 2 arguments of
|
||||
the exact same type.
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
@@ -604,7 +604,7 @@
|
||||
<xsd:annotation>
|
||||
<xsd:documentation><![CDATA[
|
||||
The exact type of the constructor argument. Only needed to avoid
|
||||
ambiguities, e.g. in case of 2 single argument constructors
|
||||
ambiguities, for example, in case of 2 single argument constructors
|
||||
that can both be converted from a String.
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
@@ -613,7 +613,7 @@
|
||||
<xsd:annotation>
|
||||
<xsd:documentation><![CDATA[
|
||||
The exact name of the argument in the constructor argument list.
|
||||
Only needed to avoid ambiguities, e.g. in case of 2 arguments of
|
||||
Only needed to avoid ambiguities, for example, in case of 2 arguments of
|
||||
the exact same type. Note: This requires debug symbols to be
|
||||
stored in the class file in order to introspect argument names!
|
||||
]]></xsd:documentation>
|
||||
@@ -899,7 +899,7 @@
|
||||
<xsd:documentation><![CDATA[
|
||||
An array can contain multiple inner bean, ref, collection, or value elements.
|
||||
This configuration element will always result in an array, even when being
|
||||
defined e.g. as a value for a map with value type Object.
|
||||
defined, for example, as a value for a map with value type Object.
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
<xsd:complexType>
|
||||
|
||||
@@ -104,7 +104,7 @@
|
||||
<xsd:attribute name="name" type="xsd:string" use="required">
|
||||
<xsd:annotation>
|
||||
<xsd:documentation><![CDATA[
|
||||
Defines the name of a custom bean scope that the annotated type registers, e.g. "conversation".
|
||||
Defines the name of a custom bean scope that the annotated type registers, for example, "conversation".
|
||||
Such a scope will be available in addition to the standard "singleton" and "prototype" scopes
|
||||
(plus "request", "session" and "globalSession" in a web application environment).
|
||||
]]></xsd:documentation>
|
||||
|
||||
@@ -69,7 +69,7 @@
|
||||
which will be returned by all calls to getBean with the given id), or
|
||||
"prototype" (independent instance resulting from each call to getBean).
|
||||
Default is "singleton". Further scopes, such as "request" or "session",
|
||||
might be supported by extended bean factories (e.g. in a web environment).
|
||||
might be supported by extended bean factories (for example, in a web environment).
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
@@ -110,7 +110,7 @@
|
||||
which will be returned by all calls to getBean with the given id), or
|
||||
"prototype" (independent instance resulting from each call to getBean).
|
||||
Default is "singleton". Further scopes, such as "request" or "session",
|
||||
might be supported by extended bean factories (e.g. in a web environment).
|
||||
might be supported by extended bean factories (for example, in a web environment).
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
@@ -151,7 +151,7 @@
|
||||
which will be returned by all calls to getBean with the given id), or
|
||||
"prototype" (independent instance resulting from each call to getBean).
|
||||
Default is "singleton". Further scopes, such as "request" or "session",
|
||||
might be supported by extended bean factories (e.g. in a web environment).
|
||||
might be supported by extended bean factories (for example, in a web environment).
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
@@ -209,7 +209,7 @@
|
||||
which will be returned by all calls to getBean with the given id), or
|
||||
"prototype" (independent instance resulting from each call to getBean).
|
||||
Default is "singleton". Further scopes, such as "request" or "session",
|
||||
might be supported by extended bean factories (e.g. in a web environment).
|
||||
might be supported by extended bean factories (for example, in a web environment).
|
||||
]]></xsd:documentation>
|
||||
</xsd:annotation>
|
||||
</xsd:attribute>
|
||||
|
||||
Reference in New Issue
Block a user