|
|
|
@ -2847,8 +2847,8 @@ public class Account { |
|
|
|
|
|
|
|
|
|
<para>When used as a marker interface in this way, Spring will configure |
|
|
|
|
new instances of the annotated type (<classname>Account</classname> in |
|
|
|
|
this case) using a prototype-scoped bean definition with the same name |
|
|
|
|
as the fully-qualified type name |
|
|
|
|
this case) using a bean definition (typically prototype-scoped) with the |
|
|
|
|
same name as the fully-qualified type name |
|
|
|
|
(<classname>com.xyz.myapp.domain.Account</classname>). Since the default |
|
|
|
|
name for a bean is the fully-qualified name of its type, a convenient |
|
|
|
|
way to declare the prototype definition is simply to omit the |
|
|
|
@ -2875,7 +2875,7 @@ public class Account { |
|
|
|
|
new <classname>Account</classname> instances.</para> |
|
|
|
|
|
|
|
|
|
<para>You can also use autowiring to avoid having to specify a |
|
|
|
|
prototype-scoped bean definition at all. To have Spring apply autowiring |
|
|
|
|
dedicated bean definition at all. To have Spring apply autowiring |
|
|
|
|
use the '<literal>autowire</literal>' property of the |
|
|
|
|
<interfacename>@Configurable</interfacename> annotation: specify either |
|
|
|
|
<literal>@Configurable(autowire=Autowire.BY_TYPE)</literal> or |
|
|
|
|