?<xsd:annotation>
??<xsd:documentation><![CDATA[
?Spring XML Beans Schema, version 2.0
?Authors: Rob Harrop, Juergen Hoeller
?這個定義了一種簡單而又持久的方式去創建一個java組件命名空間的方式，由spring BeanFactory來管理
?有xmlBeanDefination來讀取
?This defines a simple and consistent way of creating a namespace
?of JavaBeans objects, managed by a Spring BeanFactory, read by
?XmlBeanDefinitionReader (with DefaultBeanDefinitionDocumentReader).
?
這個文件類型被多數基于spring的，包括web應用的讀取等這些基于bean工廠的
?This document type is used by most Spring functionality, including
?web application contexts, which are based on bean factories.
每一個bean元素定義了一個javabean，通常bean的類是固定的，伴隨著javabean屬性或構造參數
?Each "bean" element in this document defines a JavaBean.
?Typically the bean class is specified, along with JavaBean properties
?and/or constructor arguments.
?
一個bean的實例可以是單例模式，或者是原型模式（多例），此外bean的范圍可以在擴展了beanfactory里使用比如web環境中
?A bean instance can be a "singleton" (shared instance) or a "prototype"
?(independent instance). Further scopes can be provided by extended
?bean factories, for example in a web environment.
Bean之間的相互引用也背支持，就是說，設置一個bean的屬性或者構造參數去引用另一個bean，在同一個工廠里或者在父類的工廠里
?References among beans are supported, that is, setting a JavaBean property
?or a constructor argument to refer to another bean in the same factory
?(or an ancestor factory).
作為選擇bean的引用，內部bean定義可以被使用，單例標志通常被忽略，內部bean通常是匿名的原型模式
?As alternative to bean references, "inner bean definitions" can be used.
?Singleton flags of such inner bean definitions are effectively ignored:
?inner beans are typically anonymous prototypes.
仍然支持list，sets，maps，java.util.Propertyies
?There is also support for lists, sets, maps, and java.util.Properties
?as bean property types or constructor argument types.
??]]></xsd:documentation>
?</xsd:annotation>

?<!-- base types?? 基本類型-->
?<xsd:complexType name="identifiedType" abstract="true">
??<xsd:annotation>
???<xsd:documentation><![CDATA[?? bean的id唯一
?The unique identifier for a bean. The scope of the identifier
?is the enclosing bean factory.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:attribute name="id" type="xsd:ID">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The unique identifier for a bean.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
?</xsd:complexType>

?<!-- Top-level <beans> tag?? 最頂層beans 標簽 -->
?<xsd:element name="beans">
??<xsd:annotation>
???<xsd:documentation><![CDATA[? xsd:annotation ：說明這是注釋元素
?The top level (typically root) element. Allows the definition
?of default values for all nested bean definitions.??? 頂層元素，允許對所有嵌套的bean定義默認值
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>? <![CDATA[? 定義復合類型元素，其中引用了? description? import? alias? bean? 元素?]]>
???<xsd:sequence>
????<xsd:element ref="description" minOccurs="0"/>
????<xsd:choice minOccurs="0" maxOccurs="unbounded">
?????<xsd:element ref="import"/>
?????<xsd:element ref="alias"/>
?????<xsd:element ref="bean"/>
?????<xsd:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
????</xsd:choice>
???</xsd:sequence>
???<![CDATA[? 定義屬性元素?]]>
???<xsd:attribute name="default-lazy-init" default="false" type="xsd:boolean">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The default 'lazy-init' value; see the documentation for the
?'lazy-init' attribute of the '<bean>/' element.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="default-merge" default="false" type="xsd:boolean">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The default 'merge' value; see the documentation for the
?'merge' attribute of the various collection elements.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="default-dependency-check" default="none">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The default 'dependency-check' value; see the documentation for the
?'dependency-check' attribute of the '<bean>/' element.
?????]]></xsd:documentation>
????</xsd:annotation>
????<xsd:simpleType>
?????<xsd:restriction base="xsd:NMTOKEN">
??????<xsd:enumeration value="none"/>
??????<xsd:enumeration value="simple"/>
??????<xsd:enumeration value="objects"/>
??????<xsd:enumeration value="all"/>
?????</xsd:restriction>
????</xsd:simpleType>
???</xsd:attribute>
???<xsd:attribute name="default-autowire" default="no">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The default 'autowire' value; see the documentation for the
?'autowire' attribute of the '<bean>/' element.
?????]]></xsd:documentation>
????</xsd:annotation>
????<xsd:simpleType>
?????<xsd:restriction base="xsd:NMTOKEN">
??????<xsd:enumeration value="no"/>
??????<xsd:enumeration value="byName"/>
??????<xsd:enumeration value="byType"/>
??????<xsd:enumeration value="constructor"/>
??????<xsd:enumeration value="autodetect"/>
?????</xsd:restriction>
????</xsd:simpleType>
???</xsd:attribute>
???<xsd:attribute name="default-init-method" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The default 'init-method' value; see the documentation for the
?'init-method' attribute of the '<bean>/' element.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="default-destroy-method" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The default 'destroy-method' value; see the documentation for the
?'destroy-method' attribute of the '<bean>/' element.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
??</xsd:complexType>
?</xsd:element>
??????? <!-- 完成定義beans元素-->
<!--? 定義description元素-->
?<xsd:element name="description">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Contains informative text describing the purpose of the enclosing
?element.
?Used primarily for user documentation of XML bean definition documents.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType mixed="true">
???<xsd:choice minOccurs="0" maxOccurs="unbounded"/>
??</xsd:complexType>
?</xsd:element>
<!--? 完成定義description元素-->
<!--? 定義import元素-->
?<xsd:element name="import">
??<xsd:annotation>
???<xsd:documentation source="java:org.springframework.core.io.Resource"><![CDATA[
?Specifies an XML bean definition resource to import.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:complexContent>
????<xsd:restriction base="xsd:anyType">
?????<xsd:attribute name="resource" type="xsd:string" use="required">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The relative resource location of the XML (bean definition) file to import,
?for example "myImport.xml" or "includes/myImport.xml" or "../myImport.xml".
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
????</xsd:restriction>
???</xsd:complexContent>
??</xsd:complexType>
?</xsd:element>
?????????? <!-- 結束定義import元素-->
??????? <!-- 定義alias元素-->
?<xsd:element name="alias">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Defines an alias for a bean (which can reside in a different definition
?resource).
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:complexContent>
????<xsd:restriction base="xsd:anyType">
?????<xsd:attribute name="name" type="xsd:string" use="required">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the bean to define an alias for.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
?????<xsd:attribute name="alias" type="xsd:string" use="required">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The alias name to define for the bean.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
????</xsd:restriction>
???</xsd:complexContent>
??</xsd:complexType>
?</xsd:element>
?? <!-- 結束定義alias元素-->
?? <--定義一個組 beanElements? -->
?<xsd:group name="beanElements">
??<xsd:sequence>
???<xsd:element ref="description" minOccurs="0"/>
???<xsd:choice minOccurs="0" maxOccurs="unbounded">
????<xsd:element ref="meta"/>
????<xsd:element ref="constructor-arg"/>
????<xsd:element ref="property"/>
????<xsd:element ref="lookup-method"/>
????<xsd:element ref="replaced-method"/>
????<xsd:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
???</xsd:choice>
??</xsd:sequence>
?</xsd:group>
?<--結束定義一個組 beanElements? -->
? <--定義一個屬性組 beanAttributes? -->
?<xsd:attributeGroup name="beanAttributes">
??<xsd:attribute name="name" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Can be used to create one or more aliases illegal in an (XML) id.
?Multiple aliases can be separated by any number of spaces, commas,
?or semi-colons (or indeed any mixture of the three).
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="class" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation source="java:java.lang.Class"><![CDATA[
?The fully qualified name of the bean's class, except if it pure serves as parent for child bean definitions.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="parent" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The name of the parent bean definition.

?Will use the bean class of the parent if none is specified, but can
?also override it. In the latter case, the child bean class must be
?compatible with the parent, i.e. accept the parent's property values
?and constructor argument values, if any.

?A child bean definition will inherit constructor argument values,
?property values and method overrides from the parent, with the option
?to add new values. If init method, destroy method, factory bean and/or
?factory method are specified, they will override the corresponding
?parent settings.

?The remaining settings will always be taken from the child definition:
?depends on, autowire mode, dependency check, scope, lazy init.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="scope" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The scope of this bean: typically "singleton" (one shared instance,
?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".

?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).

?Note: This attribute will not be inherited by child bean definitions.
?Hence, it needs to be specified per concrete bean definition.

?Inner bean definitions inherit the singleton status of their containing
?bean definition, unless explicitly specified: The inner bean will be a
?singleton if the containing bean is a singleton, and a prototype if
?the containing bean has any other scope.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="abstract" type="xsd:boolean">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Is this bean "abstract", that is, not meant to be instantiated itself
?but rather just serving as parent for concrete child bean definitions?
?The default is "false". Specify "true" to tell the bean factory to not
?try to instantiate that particular bean in any case.

?Note: This attribute will not be inherited by child bean definitions.
?Hence, it needs to be specified per abstract bean definition.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="lazy-init" default="default" type="defaultable-boolean">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Indicates whether or not this bean is to be lazily initialized.
?If false, it will be instantiated on startup by bean factories
?that perform eager initialization of singletons. The default is
?"false".

?Note: This attribute will not be inherited by child bean definitions.
?Hence, it needs to be specified per concrete bean definition.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="autowire" default="default">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Controls whether bean properties are "autowired".
?This is an automagical process in which bean references don't need
?to be coded explicitly in the XML bean definition file, but rather the
?Spring container works out dependencies.

?There are 5 modes:

?1. "no"
?The traditional Spring default. No automagical wiring. Bean references
?must be defined in the XML file via the <ref/> element (or "ref"
?attribute). We recommend this in most cases as it makes documentation
?more explicit.

?2. "byName"
?Autowiring by property name. If a bean of class Cat exposes a dog
?property, Spring will try to set this to the value of the bean "dog"
?in the current container. If there is no matching bean by name, nothing
?special happens; use dependency-check="objects" to raise an error in
?that case.

?3. "byType"
?Autowiring if there is exactly one bean of the property type in the
?container. If there is more than one, a fatal error is raised, and
?you cannot use byType autowiring for that bean. If there is none,
?nothing special happens; use dependency-check="objects" to raise an
?error in that case.

?4. "constructor"
?Analogous to "byType" for constructor arguments. If there is not exactly
?one bean of the constructor argument type in the bean factory, a fatal
?error is raised.

?5. "autodetect"
?Chooses "constructor" or "byType" through introspection of the bean
?class. If a default constructor is found, "byType" gets applied.

?Note that explicit dependencies, i.e. "property" and "constructor-arg"
?elements, always override autowiring. Autowire behavior can be combined
?with dependency checking, which will be performed after all autowiring
?has been completed.

?Note: This attribute will not be inherited by child bean definitions.
?Hence, it needs to be specified per concrete bean definition.
????]]></xsd:documentation>
???</xsd:annotation>
???<xsd:simpleType>
????<xsd:restriction base="xsd:NMTOKEN">
?????<xsd:enumeration value="default"/>
?????<xsd:enumeration value="no"/>
?????<xsd:enumeration value="byName"/>
?????<xsd:enumeration value="byType"/>
?????<xsd:enumeration value="constructor"/>
?????<xsd:enumeration value="autodetect"/>
????</xsd:restriction>
???</xsd:simpleType>
??</xsd:attribute>
??<xsd:attribute name="dependency-check" default="default">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Controls whether or not to check whether all of this
?beans dependencies, expressed in its properties, are satisfied.
?The default is to perform no dependency checking.

?"simple" type dependency checking includes primitives and String
?"object" includes collaborators (other beans in the factory)
?"all" includes both types of dependency checking

?Note: This attribute will not be inherited by child bean definitions.
?Hence, it needs to be specified per concrete bean definition.
????]]></xsd:documentation>
???</xsd:annotation>
???<xsd:simpleType>
????<xsd:restriction base="xsd:NMTOKEN">
?????<xsd:enumeration value="default"/>
?????<xsd:enumeration value="none"/>
?????<xsd:enumeration value="simple"/>
?????<xsd:enumeration value="objects"/>
?????<xsd:enumeration value="all"/>
????</xsd:restriction>
???</xsd:simpleType>
??</xsd:attribute>
??<xsd:attribute name="depends-on" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The names of the beans that this bean depends on being initialized.
?The bean factory will guarantee that these beans get initialized
?before this bean.

?Note that dependencies are normally expressed through bean properties
?or constructor arguments. This property should just be necessary for
?other kinds of dependencies like statics (*ugh*) or database preparation
?on startup.

?Note: This attribute will not be inherited by child bean definitions.
?Hence, it needs to be specified per concrete bean definition.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="init-method" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The name of the custom initialization method to invoke after setting
?bean properties. The method must have no arguments, but may throw any
?exception.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="destroy-method" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The name of the custom destroy method to invoke on bean factory
?shutdown. The method must have no arguments, but may throw any
?exception.

?Note: Only invoked on beans whose lifecycle is under the full
?control of the factory - which is always the case for singletons,
?but not guaranteed for any other scope.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="factory-method" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The name of a factory method to use to create this object. Use
?constructor-arg elements to specify arguments to the factory method,
?if it takes arguments. Autowiring does not apply to factory methods.

?If the "class" attribute is present, the factory method will be a static
?method on the class specified by the "class" attribute on this bean
?definition. Often this will be the same class as that of the constructed
?object - for example, when the factory method is used as an alternative
?to a constructor. However, it may be on a different class. In that case,
?the created object will *not* be of the class specified in the "class"
?attribute. This is analogous to FactoryBean behavior.

?If the "factory-bean" attribute is present, the "class" attribute is not
?used, and the factory method will be an instance method on the object
?returned from a getBean call with the specified bean name. The factory
?bean may be defined as a singleton or a prototype.

?The factory method can have any number of arguments. Autowiring is not
?supported. Use indexed constructor-arg elements in conjunction with the
?factory-method attribute.

?Setter Injection can be used in conjunction with a factory method.
?Method Injection cannot, as the factory method returns an instance,
?which will be used when the container creates the bean.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="factory-bean" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Alternative to class attribute for factory-method usage.
?If this is specified, no class attribute should be used.
?This must be set to the name of a bean in the current or
?ancestor factories that contains the relevant factory method.
?This allows the factory itself to be configured using Dependency
?Injection, and an instance (rather than static) method to be used.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="autowire-candidate" type="xsd:boolean">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Indicates whether or not this bean should be considered when looking
?for candidates to satisfy another bean's autowiring requirements.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:anyAttribute namespace="##other" processContents="lax"/>
?</xsd:attributeGroup>
??????? <--結束定義一個屬性組 beanAttributes? -->
? <--定義一個元素 meta? -->
?<xsd:element name="meta" type="metaType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Arbitrary metadata attached to a bean definition.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
???????? <--結束定義一個元素 meta? -->
?<--定義一個類型 metaTypee? -->
?<xsd:complexType name="metaType">
??<xsd:attribute name="key" type="xsd:string" use="required">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The key name of the metadata parameter being defined.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="value" type="xsd:string" use="required">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The value of the metadata parameter being defined (as a simple String).
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
?</xsd:complexType>
?<--結束定義一個類型 metaTypee? -->
? <--定義一個元素 bean? -->
?<xsd:element name="bean">
??<xsd:annotation>
???<xsd:documentation source="java:org.springframework.beans.factory.config.BeanDefinition"><![CDATA[
?Defines a single (usually named) bean.

?A bean definition may contain nested tags for constructor arguments,
?property values, lookup methods, and replaced methods. Mixing constructor
?injection and setter injection on the same bean is explicitly supported.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:complexContent>
????<xsd:extension base="identifiedType">
?????<xsd:group ref="beanElements"/>
?????<xsd:attributeGroup ref="beanAttributes"/>
????</xsd:extension>
???</xsd:complexContent>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 bean? -->
<--定義一個元素 constructor-arg? -->
?<xsd:element name="constructor-arg">
??<xsd:annotation>
???<xsd:documentation source="java:org.springframework.beans.factory.config.ConstructorArgumentValues">
????<![CDATA[<!--
?Bean definitions can specify zero or more constructor arguments.
?This is an alternative to "autowire constructor".
?Arguments correspond to either a specific index of the constructor
?argument list or are supposed to be matched generically by type.

?Note: A single generic argument value will just be used once, rather
?than potentially matched multiple times (as of Spring 1.1).

?constructor-arg elements are also used in conjunction with the
?factory-method element to construct beans using static or instance
?factory methods.
???-->]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:sequence>
????<xsd:element ref="description" minOccurs="0"/>
????<xsd:choice minOccurs="0" maxOccurs="1">
?????<xsd:element ref="bean"/>
?????<xsd:element ref="ref"/>
?????<xsd:element ref="idref"/>
?????<xsd:element ref="value"/>
?????<xsd:element ref="null"/>
?????<xsd:element ref="list"/>
?????<xsd:element ref="set"/>
?????<xsd:element ref="map"/>
?????<xsd:element ref="props"/>
?????<xsd:any namespace="##other" processContents="strict"/>
????</xsd:choice>
???</xsd:sequence>
???<xsd:attribute name="index" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The exact index of thr argument in the constructor argument list.
?Only needed to avoid ambiguities, e.g. in case of 2 arguments of
?the exact same type.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="type" type="xsd:string">
????<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
?that can both be converted from a String.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="ref" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?A short-cut alternative to a nested "<ref bean='...'/>" element.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="value" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?A short-cut alternative to a nested "<value>...<value/>"
?element.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 constructor-arg? -->
<--定義一個元素 property? -->
?<xsd:element name="property" type="propertyType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Bean definitions can have zero or more properties.
?Property elements correspond to JavaBean setter methods exposed
?by the bean classes. Spring supports primitives, references to other
?beans in the same or related factories, lists, maps and properties.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
<--結束定義一個元素 property? -->
<--定義一個元素 lookup-method? -->
?<xsd:element name="lookup-method">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?A lookup method causes the IoC container to override the given method
?and return the bean with the name given in the bean attribute. This is
?a form of Method Injection. It is particularly useful as an alternative
?to implementing the BeanFactoryAware interface, in order to be able to
?make getBean() calls for non-singleton instances at runtime. In this
?case, Method Injection is a less invasive alternative.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:complexContent>
????<xsd:restriction base="xsd:anyType">
?????<xsd:attribute name="name" type="xsd:string">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the lookup method. This method must take no arguments.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
?????<xsd:attribute name="bean" type="xsd:string">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the bean in the current or ancestor factories that
?the lookup method should resolve to. Often this bean will be a
?prototype, in which case the lookup method will return a distinct
?instance on every invocation. This is useful for single-threaded objects.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
????</xsd:restriction>
???</xsd:complexContent>
??</xsd:complexType>
?</xsd:element>
??????? <--結束定義一個元素 lookup-method? -->
?<--定義一個元素 replaced-method? -->
?<xsd:element name="replaced-method">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Similar to the lookup method mechanism, the replaced-method element
?is used to control IoC container method overriding: Method Injection.
?This mechanism allows the overriding of a method with arbitrary code.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:sequence>
????<xsd:choice minOccurs="0" maxOccurs="unbounded">
?????<xsd:element ref="arg-type"/>
????</xsd:choice>
???</xsd:sequence>
???<xsd:attribute name="name" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The name of the method whose implementation must be replaced by the
?IoC container. If this method is not overloaded, there is no need
?to use arg-type subelements. If this method is overloaded, arg-type
?subelements must be used for all override definitions for the method.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
???<xsd:attribute name="replacer" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation source="java:org.springframework.beans.factory.support.MethodReplacer"><![CDATA[
?Bean name of an implementation of the MethodReplacer interface in the
?current or ancestor factories. This may be a singleton or prototype
?bean. If it is a prototype, a new instance will be used for each
?method replacement. Singleton usage is the norm.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 replaced-method? -->
<--定義一個元素 arg-type? -->
?<xsd:element name="arg-type">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Identifies an argument for a replaced method in the event of
?method overloading.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType mixed="true">
???<xsd:choice minOccurs="0" maxOccurs="unbounded"/>
???<xsd:attribute name="match" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?Specification of the type of an overloaded method argument as a String.
?For convenience, this may be a substring of the FQN. E.g. all the
?following would match "java.lang.String":
?- java.lang.String
?- String
?- Str

?As the number of arguments will be checked also, this convenience
?can often be used to save typing.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 arg-type? -->
<--定義一個元素 ref? -->
?<xsd:element name="ref">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Defines a reference to another bean in this factory or an external
?factory (parent or included factory).
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:complexContent>
????<xsd:restriction base="xsd:anyType">
?????<xsd:attribute name="bean" type="xsd:string">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the referenced bean.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
?????<xsd:attribute name="local" type="xsd:IDREF">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the referenced bean. The value must be a bean ID,
?and thus can be checked by the XML parser, thus should be preferred
?for references within the same bean factory XML file.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
?????<xsd:attribute name="parent" type="xsd:string">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the referenced bean *in a parent factory*.
??????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
????</xsd:restriction>
???</xsd:complexContent>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 ref? -->
<--定義一個元素 idref? -->
?<xsd:element name="idref">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?The id of another bean in this factory or an external factory
?(parent or included factory).
?While a regular 'value' element could instead be used for the
?same effect, using idref in this case allows validation of local
?bean ids by the XML parser, and name completion by supporting tools.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:complexContent>
????<xsd:restriction base="xsd:anyType">
?????<xsd:attribute name="bean" type="xsd:string">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the referenced bean.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
?????<xsd:attribute name="local" type="xsd:IDREF">
??????<xsd:annotation>
???????<xsd:documentation><![CDATA[
?The name of the referenced bean. The value must be a bean ID,
?and thus can be checked by the XML parser, thus should be preferred
?for references within the same bean factory XML file.
???????]]></xsd:documentation>
??????</xsd:annotation>
?????</xsd:attribute>
????</xsd:restriction>
???</xsd:complexContent>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 idref? -->
<--定義一個元素 value? -->
?<xsd:element name="value">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Contains a string representation of a property value.
?The property may be a string, or may be converted to the required
?type using the JavaBeans PropertyEditor machinery. This makes it
?possible for application developers to write custom PropertyEditor
?implementations that can convert strings to arbitrary target objects.

?Note that this is recommended for simple objects only. Configure
?more complex objects by populating JavaBean properties with
?references to other beans.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType mixed="true">
???<xsd:choice minOccurs="0" maxOccurs="unbounded"/>
???<xsd:attribute name="type" type="xsd:string">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The exact type that the value should be converted to. Only needed
?if the type of the target property or constructor argument is
?too generic: for example, in case of a collection element.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 value? -->
<--定義一個元素 null? -->
?<xsd:element name="null">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Denotes a Java null value. Necessary because an empty "value" tag
?will resolve to an empty String, which will not be resolved to a
?null value unless a special PropertyEditor does so.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType mixed="true">
???<xsd:choice minOccurs="0" maxOccurs="unbounded"/>
??</xsd:complexType>
?</xsd:element>
<--結束定義一個元素 null -->
<--定義一個元素元素集合 collectionElements? -->
?<!-- Collection Elements -->
?<xsd:group name="collectionElements">
??<xsd:sequence>
???<xsd:choice minOccurs="0" maxOccurs="unbounded">
????<xsd:element ref="bean"/>
????<xsd:element ref="ref"/>
????<xsd:element ref="idref"/>
????<xsd:element ref="value"/>
????<xsd:element ref="null"/>
????<xsd:element ref="list"/>
????<xsd:element ref="set"/>
????<xsd:element ref="map"/>
????<xsd:element ref="props"/>
????<xsd:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
???</xsd:choice>
??</xsd:sequence>
?</xsd:group>
??????? <--結束定義一個元素集合 collectionElements? -->
<--定義一個元素 list? -->
?<xsd:element name="list" type="listOrSetType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?A list can contain multiple inner bean, ref, collection, or value
?elements. Java lists are untyped, pending generics support in Java5,
?although references will be strongly typed. A list can also map to
?an array type. The necessary conversion is automatically performed
?by the BeanFactory.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
??????? <--結束定義一個元素 list? -->
??????? <--定義一個元素 set? -->
?<xsd:element name="set" type="listOrSetType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?A set can contain multiple inner bean, ref, collection, or value
?elements. Java sets are untyped, pending generics support in Java5,
?although references will be strongly typed.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
???????? <--結束定義一個元素 set? -->
????????? <--定義一個元素 map? -->
?<xsd:element name="map" type="mapType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?A mapping from a key to an object. Maps may be empty.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
???????? <--結束定義一個元素 map? -->
????????? <--定義一個元素 entry? -->
?<xsd:element name="entry" type="entryType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?A map entry can be an inner bean, ref, value, or collection.
?The key of the entry is given by the "key" attribute or child element.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
???????? <--結束定義一個元素 entity? -->
????????? <--定義一個元素 props? -->
?<xsd:element name="props" type="propsType">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?Props elements differ from map elements in that values must be strings.
?Props may be empty.
???]]></xsd:documentation>
??</xsd:annotation>
?</xsd:element>
?<--結束定義一個元素 props? -->
? <--定義一個元素 key? -->
?<xsd:element name="key">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?A key element can contain an inner bean, ref, value, or collection.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType>
???<xsd:group ref="collectionElements"/>
??</xsd:complexType>
?</xsd:element>
???????? <--結束定義一個元素 key? -->
?<--定義一個元素 prop -->
?<xsd:element name="prop">
??<xsd:annotation>
???<xsd:documentation><![CDATA[
?The string value of the property. Note that whitespace is trimmed
?off to avoid unwanted whitespace caused by typical XML formatting.
???]]></xsd:documentation>
??</xsd:annotation>
??<xsd:complexType mixed="true">
???<xsd:choice minOccurs="0" maxOccurs="unbounded"/>
???<xsd:attribute name="key" type="xsd:string" use="required">
????<xsd:annotation>
?????<xsd:documentation><![CDATA[
?The key of the property entry.
?????]]></xsd:documentation>
????</xsd:annotation>
???</xsd:attribute>
??</xsd:complexType>
?</xsd:element>
???????? <--結束定義一個元素 prop? -->
?<--定義一個元素 propertytype? -->
?<xsd:complexType name="propertyType">
??<xsd:sequence>
???<xsd:element ref="description" minOccurs="0"/>
???<xsd:choice minOccurs="0" maxOccurs="1">
????<xsd:element ref="meta"/>
????<xsd:element ref="bean"/>
????<xsd:element ref="ref"/>
????<xsd:element ref="idref"/>
????<xsd:element ref="value"/>
????<xsd:element ref="null"/>
????<xsd:element ref="list"/>
????<xsd:element ref="set"/>
????<xsd:element ref="map"/>
????<xsd:element ref="props"/>
????<xsd:any namespace="##other" processContents="strict"/>
???</xsd:choice>
??</xsd:sequence>
??<xsd:attribute name="name" type="xsd:string" use="required">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?The name of the property, following JavaBean naming conventions.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="ref" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?A short-cut alternative to a nested "<ref bean='...'/>".
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="value" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?A short-cut alternative to a nested "<value>...</value>"
?element.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
?</xsd:complexType>
?<--結束定義一個元素 propertytype? -->
? <--定義一個類型 baseCollectionType? -->
?<!-- Collection Types -->

?<!-- base collection type -->
?<xsd:complexType name="baseCollectionType">
??<xsd:attribute name="merge" type="defaultable-boolean">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Enables/disables merging for collections when using parent/child beans.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
?</xsd:complexType>
?<--結束定義一個類型 baseCollectionType? -->
? <--定義一個類型 typedCollectionType? -->
?<!-- base type for collections that have (possibly) typed nested values -->
?<xsd:complexType name="typedCollectionType">
??<xsd:complexContent>
???<xsd:extension base="baseCollectionType">
????<xsd:attribute name="value-type" type="xsd:string">
?????<xsd:annotation>
??????<xsd:documentation source="java:java.lang.Class"><![CDATA[
?The default Java type for nested values. Must be a fully qualified
?class name.
??????]]></xsd:documentation>
?????</xsd:annotation>
????</xsd:attribute>
???</xsd:extension>
??</xsd:complexContent>
?</xsd:complexType>
? <--結束定義一個類型 typedCollectionType? -->
??? <--定義一個類型 mapType? -->
?<!-- 'map' element type -->
?<xsd:complexType name="mapType">
??<xsd:complexContent>
???<xsd:extension base="typedCollectionType">
????<xsd:sequence>
?????<xsd:choice minOccurs="0" maxOccurs="unbounded">
??????<xsd:element ref="entry"/>
?????</xsd:choice>
????</xsd:sequence>
????<xsd:attribute name="key-type" type="xsd:string">
?????<xsd:annotation>
??????<xsd:documentation source="java:java.lang.Class"><![CDATA[
?The default Java type for nested entry keys. Must be a fully qualified
?class name. ?
??????]]></xsd:documentation>
?????</xsd:annotation>
????</xsd:attribute>
???</xsd:extension>
??</xsd:complexContent>
?</xsd:complexType>
? <--結束定義一個類型 mapType? -->
??? <--定義一個類型 entryType? -->
?<!-- 'entry' element type -->
?<xsd:complexType name="entryType">
??<xsd:sequence>
???<xsd:element ref="key" minOccurs="0"/>
???<xsd:group ref="collectionElements"/>
??</xsd:sequence>
??<xsd:attribute name="key" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?Each map element must specify its key as attribute or as child element.
?A key attribute is always a String value.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="key-ref" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?A short-cut alternative to a to a "key" element with a nested
?"<ref bean='...'/>".
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="value" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?A short-cut alternative to a nested "<value>...</value>"
?element.
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
??<xsd:attribute name="value-ref" type="xsd:string">
???<xsd:annotation>
????<xsd:documentation><![CDATA[
?A short-cut alternative to a nested "<ref bean='...'/>".
????]]></xsd:documentation>
???</xsd:annotation>
??</xsd:attribute>
?</xsd:complexType>
?<--結束定義一個類型 entryType? -->
? <--定義一個類型 listOrSetType? -->
?<!-- 'list' and 'set' collection type -->
?<xsd:complexType name="listOrSetType">
??<xsd:complexContent>
???<xsd:extension base="typedCollectionType">
????<xsd:group ref="collectionElements"/>
???</xsd:extension>
??</xsd:complexContent>
?</xsd:complexType>
? <--結束定義一個類型 listOrSetType? -->
?? <--定義一個類型 propsType? -->
?<!-- 'props' collection type -->
?<xsd:complexType name="propsType">
??<xsd:complexContent>
???<xsd:extension base="baseCollectionType">
????<xsd:sequence>
?????<xsd:choice minOccurs="0" maxOccurs="unbounded">
??????<xsd:element ref="prop"/>
?????</xsd:choice>
????</xsd:sequence>
???</xsd:extension>
??</xsd:complexContent>
?</xsd:complexType>
? <--結束定義一個類型 propsType? -->
??? <--定義一個類型 defaultable-boolean? -->
?<!-- simple internal types -->
?<xsd:simpleType name="defaultable-boolean">
??<xsd:restriction base="xsd:NMTOKEN">
???<xsd:enumeration value="default"/>
???<xsd:enumeration value="true"/>
???<xsd:enumeration value="false"/>
??</xsd:restriction>
?</xsd:simpleType>
? <--結束定義一個類型 defaultable-boolean? -->
</xsd:schema>