<?xml version="1.0" encoding="UTF-8" standalone="no"?><xsd:schema xmlns="http://jsf-spring.sourceforge.net/schema/jsf"	xmlns:xsd="http://www.w3.org/2001/XMLSchema"	xmlns:beans="http://www.springframework.org/schema/beans"	targetNamespace="http://jsf-spring.sourceforge.net/schema/jsf"	elementFormDefault="qualified" attributeFormDefault="unqualified">	<xsd:import namespace="http://www.springframework.org/schema/beans"		schemaLocation="http://www.springframework.org/schema/beans/spring-beans-2.0.xsd" />	<xsd:element name="enable-managed-bean-factory">		<xsd:annotation>			<xsd:documentation				source="java:de.mindmatters.faces.spring.factory.VariableResolverProcessor">				<![CDATA[	All managed beans will be instantiated with the original VariableResolver 	of the underlying JSF implementation.			]]>			</xsd:documentation>		</xsd:annotation>	</xsd:element>	<xsd:complexType name="renderer">		<xsd:annotation>			<xsd:documentation source="java:javax.faces.render.Renderer">				<![CDATA[	The "renderer" type represents a concrete Renderer implementation    class that should be registered under the specified component family    and renderer type identifiers, in the RenderKit associated with the    parent "render-kit" element.  Combinations of component family and renderer    type must be unique within the RenderKit associated with the parent    "render-kit" element.			]]>			</xsd:documentation>		</xsd:annotation>		<xsd:group ref="beans:beanElements" />		<xsd:attribute name="type" type="xsd:string" use="required">			<xsd:annotation>				<xsd:documentation>					<![CDATA[	The "type" attribute represents a renderer type identifier for the Renderer.				]]>				</xsd:documentation>			</xsd:annotation>		</xsd:attribute>		<xsd:attribute name="component-family" type="xsd:string"			use="required">			<xsd:annotation>				<xsd:documentation>					<![CDATA[	The "component-family" attribute represents the component family for    which the Renderer will be used.    			]]>				</xsd:documentation>			</xsd:annotation>		</xsd:attribute>		<xsd:attribute name="class" type="xsd:string" use="required">			<xsd:annotation>				<xsd:documentation>					<![CDATA[	The "class" attribute represents the fully qualified class name 	of a concrete Renderer implementation class.				]]>				</xsd:documentation>			</xsd:annotation>		</xsd:attribute>		<xsd:anyAttribute namespace="##other" processContents="lax"/>	</xsd:complexType>	<xsd:element name="render-kit">		<xsd:annotation>			<xsd:documentation				source="java:javax.faces.render.RenderKit">				<![CDATA[	The "render-kit" element represents a concrete RenderKit implementation    that should be registered under the specified "id" attribute.  If no    render-kit-id is specified, the identifier of the default RenderKit    (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed.    		]]>			</xsd:documentation>		</xsd:annotation>		<xsd:complexType>			<xsd:complexContent>				<xsd:extension base="beans:identifiedType">					<xsd:sequence>						<xsd:element ref="beans:description"							minOccurs="0" />						<xsd:choice minOccurs="0"							maxOccurs="unbounded">							<xsd:element ref="beans:meta" />							<xsd:element ref="beans:constructor-arg" />							<xsd:element ref="beans:property" />							<xsd:element ref="beans:lookup-method" />							<xsd:element ref="beans:replaced-method" />							<xsd:element name="renderer"								type="renderer" />						</xsd:choice>					</xsd:sequence>					<xsd:attribute name="class" type="xsd:string">						<xsd:annotation>							<xsd:documentation>								<![CDATA[	The "class" attribute represents the fully qualified class name    of a concrete RenderKit implementation class.    						]]>							</xsd:documentation>						</xsd:annotation>					</xsd:attribute>					<xsd:anyAttribute namespace="##other" processContents="lax"/>				</xsd:extension>			</xsd:complexContent>		</xsd:complexType>	</xsd:element>	<xsd:complexType name="plugin">		<xsd:group ref="beans:beanElements" />		<xsd:attribute name="order" type="xsd:int">			<xsd:annotation>				<xsd:documentation					source="java:org.springframework.core.Ordered">					<![CDATA[	The instantiation order of this plugin.				]]>				</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 plugin's class, except if it pure serves as parent for child bean definitions.				]]>				</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="byType" />					<xsd:enumeration value="byName" />					<xsd:enumeration value="default" />					<xsd:enumeration value="no" />					<xsd:enumeration value="autodetect" />					<xsd:enumeration value="constructor" />				</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="all" />					<xsd:enumeration value="objects" />					<xsd:enumeration value="simple" />				</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="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 beans autowiring requirements.				]]>				</xsd:documentation>			</xsd:annotation>		</xsd:attribute>		<xsd:anyAttribute namespace="##other" processContents="lax"/>	</xsd:complexType>	<xsd:element name="action-listener" type="plugin">		<xsd:annotation>			<xsd:documentation				source="java:javax.faces.event.ActionListener">				<![CDATA[	The "action-listener" element represents the concrete ActionListener 	implementation that will be called during the Invoke Application phase 	of the request processing lifecycle.    		]]>			</xsd:documentation>		</xsd:annotation>	</xsd:element>	<xsd:element name="navigation-handler" type="plugin">		<xsd:annotation>			<xsd:documentation				source="java:javax.faces.application.NavigationHandler">				<![CDATA[	The "navigation-handler" element represents the concrete NavigationHandler 	implementation that will be called during the Invoke Application phase of 	the request processing lifecycle, if the default ActionListener (provided 	by the JSF implementation) is used.    		]]>			</xsd:documentation>		</xsd:annotation>	</xsd:element>	<xsd:element name="property-resolver" type="plugin">		<xsd:annotation>			<xsd:documentation				source="java:javax.faces.el.PropertyResolver">				<![CDATA[	The "property-resolver" element represents the concrete PropertyResolver 	implementation that will be used during the processing of value binding 	expressions.    		]]>			</xsd:documentation>		</xsd:annotation>	</xsd:element>	<xsd:element name="state-manager" type="plugin">		<xsd:annotation>			<xsd:documentation				source="java:javax.faces.application.StateManager">				<![CDATA[	The "state-manager" element represents the concrete StateManager 	implementation that will be called during the Restore View and Render 	Response phases of the request processing lifecycle.    		]]>			</xsd:documentation>