精华内容
下载资源
问答
  • 如何用xsd文件验证xml
    2021-04-08 10:02:33

    这篇文章主要介绍了C#使用xsd文件验证XML格式是否正确的实现方法,结合实例形式分析了C#针对xml文件的创建、验证相关操作技巧,需要的朋友可以参考下

    本文实例讲述了C#使用xsd文件验证XML格式是否正确的实现方法。分享给大家供大家参考,具体如下://创建xmlDocument

    XmlDocument doc = new XmlDocument();

    //创建声明段 如<?xml version="1.0" encoding="utf-8" ?>

    doc.AppendChild(doc.CreateXmlDeclaration("1.0", "utf-8", null));

    //创建一个根节点 KYTResults

    XmlElement results = doc.CreateElement("KYTResults");

    //创建 ResultsStatus

    XmlNode resultsStatus = doc.CreateElement("ResultsStatus");

    //创建Level

    XmlElement element = doc.CreateElement("Level");

    element.InnerText = status ? "0" : "1";

    resultsStatus.AppendChild(element);

    //创建Description

    element = doc.CreateElement("Description");

    element.InnerText = msg;

    resultsStatus.AppendChild(element);

    //创建PassKey 如果用户登录失败 将加载空字符

    element = doc.CreateElement("PassKey");

    element.InnerText = key;

    resultsStatus.AppendChild(element);

    results.AppendChild(resultsStatus);

    //END 创建 ResultsStatus

    //创建 DataList 数据集合

    if (status)

    {

    results.AppendChild(dataList);

    }

    //END 创建一个根节点 KYTResults

    doc.AppendChild(results);

    string path = Server.MapPath("/ws/xsd/ReceiveReturn.xsd");

    //验证xml格式是否正确 通过xsd验证

    string error = "";

    //声明XmlSchema

    XmlSchemaSet schemas = new XmlSchemaSet();

    schemas.Add("", XmlReader.Create(path));

    //声明事件处理方法

    ValidationEventHandler eventHandler = new ValidationEventHandler(delegate(object sender, ValidationEventArgs e) {

    switch (e.Severity)

    {

    case XmlSeverityType.Error:

    error += e.Message;

    break;

    case XmlSeverityType.Warning:

    break;

    }

    });

    doc.Schemas = schemas;

    //验证xml

    doc.Validate(eventHandler);

    //检查是否有异常 如果格式不正确就抛出来

    if (!"".Equals(error))

    {

    throw new Exception(error);

    }

    更多相关内容
  • 主要介绍了C#使用xsd文件验证XML格式是否正确的实现方法,结合实例形式分析了C#针对xml文件的创建、验证相关操作技巧,需要的朋友可以参考下
  • 使用xsd文件验证xml

    万次阅读 2016-01-19 17:50:34
    项目中遇到了需要对xml数据进行入库的需求,但是在入库之前需要利用xsd文件xml的合法性进行验证。 在网上找代码,找到了 leizhimin 的BLOG ,将其整理。感谢博主分享代码。 代码: import java.io.File; ...

    项目中遇到了需要对xml数据进行入库的需求,但是在入库之前需要利用xsd文件对xml的合法性进行验证。

    在网上找代码,找到了 leizhimin 的BLOG ,将其整理。感谢博主分享代码。


    代码:

    import java.io.File;
    
    import javax.xml.parsers.SAXParser;
    import javax.xml.parsers.SAXParserFactory;
    
    import org.dom4j.Document;
    import org.dom4j.io.OutputFormat;
    import org.dom4j.io.SAXReader;
    import org.dom4j.io.SAXValidator;
    import org.dom4j.io.XMLWriter;
    import org.dom4j.util.XMLErrorHandler;
    import org.junit.Test;
    
    
    
    public class XmlValidator {
    	String XMLPath = "E:\\tmp\\spring.xml";
    	String xsdPath = "E:\\tmp\\valid-spring.xsd";
    	@Test
    	public void parser() throws Exception {
    		validateXMLByXSD(XMLPath,xsdPath);
    	}
    	/** 
         * 通过XSD(XML Schema)校验XML 
         */ 
        public static void validateXMLByXSD(String xmlFileName,String xsdFileName) { 
            try { 
                //创建默认的XML错误处理器 
                XMLErrorHandler errorHandler = new XMLErrorHandler(); 
                //获取基于 SAX 的解析器的实例 
                SAXParserFactory factory = SAXParserFactory.newInstance(); 
                //解析器在解析时验证 XML 内容。 
                factory.setValidating(true); 
                //指定由此代码生成的解析器将提供对 XML 名称空间的支持。 
                factory.setNamespaceAware(true); 
                //使用当前配置的工厂参数创建 SAXParser 的一个新实例。 
                SAXParser parser = factory.newSAXParser(); 
                //创建一个读取工具 
                SAXReader xmlReader = new SAXReader(); 
                //获取要校验xml文档实例 
                Document xmlDocument = (Document) xmlReader.read(new File(xmlFileName)); 
                //设置 XMLReader 的基础实现中的特定属性。核心功能和属性列表可以在 [url]http://sax.sourceforge.net/?selected=get-set[/url] 中找到。 
                parser.setProperty( 
                        "http://java.sun.com/xml/jaxp/properties/schemaLanguage", 
                        "http://www.w3.org/2001/XMLSchema"); 
                parser.setProperty( 
                        "http://java.sun.com/xml/jaxp/properties/schemaSource", 
                        "file:" + xsdFileName); 
                //创建一个SAXValidator校验工具,并设置校验工具的属性 
                SAXValidator validator = new SAXValidator(parser.getXMLReader()); 
                //设置校验工具的错误处理器,当发生错误时,可以从处理器对象中得到错误信息。 
                validator.setErrorHandler(errorHandler); 
                //校验 
                validator.validate(xmlDocument); 
    
                XMLWriter writer = new XMLWriter(OutputFormat.createPrettyPrint()); 
                //如果错误信息不为空,说明校验失败,打印错误信息 
                if (errorHandler.getErrors().hasContent()) { 
                    System.out.println("XML文件通过XSD文件校验失败!"); 
                    writer.write(errorHandler.getErrors()); 
                } else { 
                    System.out.println("Good! XML文件通过XSD文件校验成功!"); 
                } 
            } catch (Exception ex) { 
                System.out.println("XML文件: " + xmlFileName + " 通过XSD文件:" + xsdFileName + "检验失败。\n原因: " + ex.getMessage()); 
                ex.printStackTrace(); 
            } 
        } 
    }
    


    spring.xml: 使用spring的配置文件进行验证:

    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context"
    	xsi:schemaLocation="http://www.springframework.org/schema/beans 
        http://www.springframework.org/schema/beans/spring-beans-3.0.xsd">
    	
    	
    	<bean
    		class="org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter"></bean>
    	
    	<bean id="viewResolver"
    		class="org.springframework.web.servlet.view.InternalResourceViewResolver">
    		<property name="prefix" value="/" />
    		<property name="suffix" value=".jsp" />
    		<property name="viewClass"
    			value="org.springframework.web.servlet.view.JstlView" />
    	</bean>
    	
    	 
        <bean id="exceptionResolver" class="org.springframework.web.servlet.handler.SimpleMappingExceptionResolver">  
        </bean>
    </beans>


    valid-spring.xml : 其实就是http://www.springframework.org/schema/beans/spring-beans-3.0.xsd 下载下来改的名称。

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    
    <xsd:schema xmlns="http://www.springframework.org/schema/beans"
    		xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    		targetNamespace="http://www.springframework.org/schema/beans">
    
    	<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>
    
    	<xsd:annotation>
    		<xsd:documentation><![CDATA[
    	Spring XML Beans Schema, version 3.0
    	Authors: Juergen Hoeller, Rob Harrop, Mark Fisher
    
    	This defines a simple and consistent way of creating a namespace
    	of JavaBeans objects, managed by a Spring BeanFactory, read by
    	XmlBeanDefinitionReader (with DefaultBeanDefinitionDocumentReader).
    
    	This document type is used by most Spring functionality, including
    	web application contexts, which are based on bean factories.
    
    	Each "bean" element in this document defines a JavaBean.
    	Typically the bean class is specified, along with JavaBean properties
    	and/or constructor arguments.
    
    	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.
    
    	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).
    
    	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.
    
    	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[
    	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 -->
    	<xsd:element name="beans">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	The top level (typically root) element. Allows the definition
    	of default values for all nested bean definitions.
    			]]></xsd:documentation>
    		</xsd:annotation>
    		<xsd:complexType>
    			<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>
    			<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-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:restriction>
    				</xsd:simpleType>
    			</xsd:attribute>
    			<xsd:attribute name="default-autowire-candidates" type="xsd:string">
    				<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".
    	See the documentation for the 'autowire-candidate' attribute of the
    	'<bean/>' element for the semantic details of autowire candidate beans.
    					]]></xsd:documentation>
    				</xsd:annotation>
    			</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:anyAttribute namespace="##other" processContents="lax"/>
    		</xsd:complexType>
    	</xsd:element>
    
    	<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>
    
    	<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>
    
    	<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>
    
    	<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="qualifier"/>
    				<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>
    
    	<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 serves only
    	as a parent definition 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, 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).
    
    	By default, a bean will be a singleton, unless the bean has a parent
    	bean definition in which case it will inherit the parent's scope.
    
    	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).
    
    	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 4 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.
    
    	Note that this default mode also allows for annotation-driven autowiring,
    	if activated. "no" refers to externally driven autowiring only, not
    	affecting any autowiring demands that the bean class itself expresses.
    
    	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.
    
    	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.
    
    	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.
    
    	Note that explicit dependencies, i.e. "property" and "constructor-arg"
    	elements, always override autowiring.
    
    	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: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" default="default" type="defaultable-boolean">
    			<xsd:annotation>
    				<xsd:documentation><![CDATA[
    	Indicates whether or not this bean should be considered when looking
    	for matching candidates to satisfy another bean's autowiring requirements.
    	Note that this does not affect explicit references by name, which will get
    	resolved even if the specified bean is not marked as an autowire candidate.
    				]]></xsd:documentation>
    			</xsd:annotation>
    		</xsd:attribute>
    		<xsd:attribute name="primary" type="xsd:boolean">
    			<xsd:annotation>
    				<xsd:documentation><![CDATA[
    	Specifies that this bean should be given preference when multiple
    	candidates are qualified to autowire a single-valued dependency.
    	If exactly one 'primary' bean exists among the candidates, it
    	will be the autowired value.
    				]]></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:anyAttribute namespace="##other" processContents="lax"/>
    	</xsd:attributeGroup>
    
    	<xsd:element name="meta" type="metaType">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	Arbitrary metadata attached to a bean definition.
    			]]></xsd:documentation>
    		</xsd:annotation>
    	</xsd:element>
    
    	<xsd:complexType name="metaType">
    		<xsd:attribute name="key" type="xsd:string" use="required">
    			<xsd:annotation>
    				<xsd:documentation><![CDATA[
    	The key name of the metadata attribute 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 attribute being defined (as a simple String).
    				]]></xsd:documentation>
    			</xsd:annotation>
    		</xsd:attribute>
    	</xsd:complexType>
    
    	<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>
    
    	<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="array"/>
    					<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 the 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="name" type="xsd:string">
    				<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
    	the exact same type. Note: This requires debug symbols to be
    	stored in the class file in order to introspect argument names!
    					]]></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>
    
    	<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>
    
    	<xsd:element name="qualifier">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	Bean definitions can provide qualifiers to match against annotations
    	on a field or parameter for fine-grained autowire candidate resolution.
    			]]></xsd:documentation>
    		</xsd:annotation>
    		<xsd:complexType>
    			<xsd:sequence>
    				<xsd:element ref="attribute" minOccurs="0" maxOccurs="unbounded"/>
    			</xsd:sequence>
    			<xsd:attribute name="type" type="xsd:string" default="org.springframework.beans.factory.annotation.Qualifier"/>
    			<xsd:attribute name="value" type="xsd:string"/>
    		</xsd:complexType>
    	</xsd:element>
    
    	<xsd:element name="attribute" type="metaType">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	A qualifier element may contain attribute child elements as key-value
    	pairs. These will be available for matching against attributes of a
    	qualifier annotation on an autowired field or parameter if present.
    			]]></xsd:documentation>
    		</xsd:annotation>
    	</xsd:element>
    
    	<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>
    
    	<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>
    
    	<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>
    
    	<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. This is therefore the preferred technique 
    	for referencing beans 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>
    
    	<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. This is therefore the preferred technique 
    	for referencing beans within the same bean factory XML file.
    							]]></xsd:documentation>
    						</xsd:annotation>
    					</xsd:attribute>
    				</xsd:restriction>
    			</xsd:complexContent>
    		</xsd:complexType>
    	</xsd:element>
    
    	<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>
    
    	<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>
    
    	<!-- Collection Elements -->
    	<xsd:group name="collectionElements">
    		<xsd:sequence>
    			<xsd:element ref="description" minOccurs="0"/>
    			<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="array"/>
    				<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>
    
    	<xsd:element name="array">
    		<xsd:annotation>
    			<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.
    			]]></xsd:documentation>
    		</xsd:annotation>
    		<xsd:complexType>
    			<xsd:complexContent>
    				<xsd:extension base="listOrSetType">
    					<xsd:attribute name="merge" default="default" 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:extension>
    			</xsd:complexContent>
    		</xsd:complexType>
    	</xsd:element>
    
    	<xsd:element name="list">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	A list can contain multiple inner bean, ref, collection, or value elements.
    	A list can also map to an array type; the necessary conversion is performed
    	automatically.
    			]]></xsd:documentation>
    		</xsd:annotation>
    		<xsd:complexType>
    			<xsd:complexContent>
    				<xsd:extension base="listOrSetType">
    					<xsd:attribute name="merge" default="default" 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:extension>
    			</xsd:complexContent>
    		</xsd:complexType>
    	</xsd:element>
    
    	<xsd:element name="set">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	A set can contain multiple inner bean, ref, collection, or value elements.
    			]]></xsd:documentation>
    		</xsd:annotation>
    		<xsd:complexType>
    			<xsd:complexContent>
    				<xsd:extension base="listOrSetType">
    					<xsd:attribute name="merge" default="default" 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:extension>
    			</xsd:complexContent>
    		</xsd:complexType>
    	</xsd:element>
    
    	<xsd:element name="map">
    		<xsd:annotation>
    			<xsd:documentation><![CDATA[
    	A mapping from a key to an object. Maps may be empty.
    			]]></xsd:documentation>
    		</xsd:annotation>
    		<xsd:complexType>
    			<xsd:complexContent>
    				<xsd:extension base="mapType">
    					<xsd:attribute name="merge" default="default" 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:extension>
    			</xsd:complexContent>
    		</xsd:complexType>
    	</xsd:element>
    
    	<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>
    
    	<xsd:element name="props">
    		<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:complexType>
    			<xsd:complexContent>
    				<xsd:extension base="propsType">
    					<xsd:attribute name="merge" default="default" 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:extension>
    			</xsd:complexContent>
    		</xsd:complexType>
    	</xsd:element>
    
    	<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>
    
    	<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>
    
    	<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="array"/>
    				<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>
    
    	<!-- Collection Types -->
    
    	<!-- base type for collections that have (possibly) typed nested values -->
    	<xsd:complexType name="collectionType">
    		<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:complexType>
    
    	<!-- 'list' and 'set' collection type -->
    	<xsd:complexType name="listOrSetType">
    		<xsd:complexContent>
    			<xsd:extension base="collectionType">
    				<xsd:group ref="collectionElements"/>
    			</xsd:extension>
    		</xsd:complexContent>
    	</xsd:complexType>
    
    	<!-- 'map' element type -->
    	<xsd:complexType name="mapType">
    		<xsd:complexContent>
    			<xsd:extension base="collectionType">
    				<xsd:sequence>
    					<xsd:element ref="description" minOccurs="0"/>
    					<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>
    
    	<!-- '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>
    
    	<!-- 'props' collection type -->
    	<xsd:complexType name="propsType">
    		<xsd:complexContent>
    			<xsd:extension base="collectionType">
    				<xsd:sequence>
    					<xsd:choice minOccurs="0" maxOccurs="unbounded">
    						<xsd:element ref="prop"/>
    					</xsd:choice>
    				</xsd:sequence>
    			</xsd:extension>
    		</xsd:complexContent>
    	</xsd:complexType>
    
    	<!-- 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>
    
    </xsd:schema>
    


    运行结果:

    Good! XML文件通过XSD文件校验成功!

    展开全文
  • 根据XML模式(xsd文件)快速轻松地验证XML文件。 需要安装Java。 在Mac和Linux上的用法: ./xsdv.sh test.xsd test.xml Windows命令提示符下的用法: xsdv test.xsd test.xml 如果您发现它有用并且想要在系统...
  • 基本的linter(XML +部分XSD验证) 基于XSD的快速自动完成功能(利用来自XSD的评论) 格式化XML(选定范围或完整文档) 自动关闭和自动重命名当前编辑的标签(仅适用于给定行中的单个标签) xml节点/属性的鼠标...
  • 可以一个指定的XML Schema来验证某个XML文档,以检查该XML文档是否符合其要求。文档设计者可以通过XML Schema指定一个XML文档所允许的 结构和内容,并可据此检查一个XML文档是否是有效的。XM...

    Xsd

    结构定义( XML Schemas Definition )

    XML Schema是DTD的替代品。XML Schema语言也就是XSD。XML Schema描述了XML文档的结构。可以用一个指定的XML Schema来验证某个XML文档,以检查该XML文档是否符合其要求。

    文档设计者可以通过XML Schema指定一个XML文档所允许的 结构和内容,并可据此检查一个XML文档是否是有效的。XML Schema本身是一个XML文档,它符合XML语法结构。

    可以用通用的XML解析器解析它。一个XML Schema会定义:文档中出现的元素、文档中出现的属性、子元素、子元素的数量、子元素的顺序、元素是否为空、元素和属性的数据类型、元素或属性的默认和固定值。

    XSD文件的后缀名为.xsd。

    在下面的代码示例中,上面的架构添加到 XmlReaderSettings 对象的 XmlSchemaSetSchemas 属性中。 XmlReaderSettings 对象作为参数传递给验证上述 XML 文档的 XmlReader 对象的 Create 方法。XmlReaderSettings 对象的 ValidationType 属性设置为 Schema,强制通过 XmlReader 对象的 Create 方法验证 XML 文档。将 ValidationEventHandler 添加到 XmlReaderSettings 对象以处理 XML 文档和架构验证过程中发现的错误所引发的任何 Warning 或 Error 事件。

    下面是一个例子:using System;

    using System.Xml;

    using System.Xml.Schema;

    using System.IO;

    using System.Xml.Serialization;

    using System.Text;

    public class XmlSchemaSetExample

    {

    static void Main()

    {

    XmlReaderSettings booksSettings = new XmlReaderSettings();

    booksSettings.Schemas.Add("http://www.contoso.com/books", "contosoBooks.xsd");

    booksSettings.ValidationType = ValidationType.Schema;

    booksSettings.ValidationEventHandler += new ValidationEventHandler(booksSettingsValidationEventHandler);

    MemoryStream ms = new MemoryStream();//定义一个数据流对象

    XmlDocument doc = new XmlDocument();

    doc.Load("contosoBooks.xml");

    doc.Save(ms);

    ms.Position = 0; //修改指针的位置

    XmlReader books = XmlReader.Create(ms,booksSettings);

    while (books.Read())

    { }

    }

    static void booksSettingsValidationEventHandler(object sender, ValidationEventArgs e)

    {

    if (e.Severity == XmlSeverityType.Warning)

    {

    Console.Write("WARNING: ");

    Console.WriteLine(e.Message);

    Console.Read();

    }

    else if (e.Severity == XmlSeverityType.Error)

    {

    Console.Write("ERROR: ");

    Console.WriteLine(e.Message);

    Console.Read();

    }

    }

    }

    contosoBooks.xsd<?xml version="1.0" encoding="utf-8"?>

    For

    mDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.contoso.com/books" xmlns:xs="http://www.w3.org/2

    001

    /XMLSchema">

    contosoBooks.xml<?xml version="1.0" encoding="utf-8" ?>

    The Autobiography of Benjamin Franklin

    Benjamin

    Franklin

    8.99

    The Confidence Man

    Herman

    Melville

    11.99

    The Gorgias

    Plato

    9.99

    备注:关于Xsd的其他的一些类或者实例

    StreamWriter ,StreamReader,XmlSchema,XmlSchemaSet

    Stream stream = new MemoryStream(); //当一个类的对象无法初始化时,可以考虑用它的继承类。

    FileStream fs = File.Open("117.xml",FileMode.OpenOrCreate,FileAccess.ReadWrite);

    TextReader tr1=new StreamReader("123.xml");

    TextReader tr2= new StringReader("asdfsadfsdf");

    展开全文
  • XML验证器(XSD验证XML)

    热门讨论 2011-10-11 15:41:03
    XML验证器(XSD验证XML)附Delphi7源码 http://blog.csdn.net/akof1314/article/details/6860264 有介绍
  • java - 根据XSD文件验证XML文件的最佳方法是什么?我正在生成一些需要符合给我的xsd文件的xml文件。 什么是验证它们符合要求的最佳方法?13个解决方案307 votesJava运行时库支持验证。 上次我检查过这是封面上的...

    java - 根据XSD文件验证XML文件的最佳方法是什么?

    我正在生成一些需要符合给我的xsd文件的xml文件。 什么是验证它们符合要求的最佳方法?

    13个解决方案

    307 votes

    Java运行时库支持验证。 上次我检查过这是封面上的Apache Xerces解析器。 您应该使用javax.xml.validation.Validator。

    import javax.xml.XMLConstants;

    import javax.xml.transform.Source;

    import javax.xml.transform.stream.StreamSource;

    import javax.xml.validation.*;

    import java.net.URL;

    import org.xml.sax.SAXException;

    //import java.io.File; // if you use File

    import java.io.IOException;

    ...

    URL schemaFile = new URL("http://host:port/filename.xsd");

    // webapp example xsd:

    // URL schemaFile = new URL("http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd");

    // local file example:

    // File schemaFile = new File("/location/to/localfile.xsd"); // etc.

    Source xmlFile = new StreamSource(new File("web.xml"));

    SchemaFactory schemaFactory = SchemaFactory

    .newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

    try {

    Schema schema = schemaFactory.newSchema(schemaFile);

    Validator validator = schema.newValidator();

    validator.validate(xmlFile);

    System.out.println(xmlFile.getSystemId() + " is valid");

    } catch (SAXException e) {

    System.out.println(xmlFile.getSystemId() + " is NOT valid reason:" + e);

    } catch (IOException e) {}

    模式工厂常量是字符串http://www.w3.org/2001/XMLSchema,它定义了XSD。 上面的代码根据URL http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd验证WAR部署描述符,但您可以轻松地对本地文件进行验证。

    您不应该使用DOMParser来验证文档(除非您的目标是创建文档对象模型)。 这将在解析文档时开始创建DOM对象 - 如果您不打算使用它们会浪费。

    McDowell answered 2019-03-02T10:09:42Z

    25 votes

    以下是使用Xerces2的方法。 这里有一个教程,这里(需要注册)。

    原始归属:从这里公然复制:

    import org.apache.xerces.parsers.DOMParser;

    import java.io.File;

    import org.w3c.dom.Document;

    public class SchemaTest {

    public static void main (String args[]) {

    File docFile = new File("memory.xml");

    try {

    DOMParser parser = new DOMParser();

    parser.setFeature("http://xml.org/sax/features/validation", true);

    parser.setProperty(

    "http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation",

    "memory.xsd");

    ErrorChecker errors = new ErrorChecker();

    parser.setErrorHandler(errors);

    parser.parse("memory.xml");

    } catch (Exception e) {

    System.out.print("Problem parsing the file.");

    }

    }

    }

    SCdF answered 2019-03-02T10:10:14Z

    19 votes

    我们使用ant构建项目,因此我们可以使用schemavalidate任务来检查我们的配置文件:

    现在顽皮的配置文件将失败我们的构建!

    [http://ant.apache.org/manual/Tasks/schemavalidate.html]

    chickeninabiscuit answered 2019-03-02T10:10:54Z

    10 votes

    我发现这个网站也很有帮助。

    [http://www.ibm.com/developerworks/xml/library/x-javaxmlvalidapi.html]

    这是一个真正为我工作的人,只需要少量的烦恼。

    Michael Campbell answered 2019-03-02T10:11:33Z

    9 votes

    由于这是一个受欢迎的问题,我还想指出java可以针对“引用”xsd进行验证,例如,如果.xml文件本身指定XSD,则使用xmlsns:xsi或xsi:noNamespaceSchemaLocation(或特定名称空间的xsi) 这里说:

    xsi:noNamespaceSchemaLocation="http://www.example.com/document.xsd">

    ...

    或SchemaLocation(始终是xsd映射的命名空间列表)

    xsi:SchemaLocation="http://www.example.com/document http://www.example.com/document.xsd">

    ...

    “如果您创建了一个模式而没有指定URL,文件或源,那么Java语言会创建一个查找正在验证的文档中的模式,以查找它应该使用的模式。例如:”

    SchemaFactory factory = SchemaFactory.newInstance("http://www.w3.org/2001/XMLSchema");

    Schema schema = factory.newSchema();

    这适用于多个名称空间等。这种方法的问题在于xmlsns:xsi可能是一个网络位置,因此它会在每次验证时都出现并点击网络,而不是最佳。

    下面是一个示例,它针对它引用的任何XSD验证XML文件(即使它必须从网络中提取它们):

    public static void verifyValidatesInternalXsd(String filename) throws Exception {

    InputStream xmlStream = new new FileInputStream(filename);

    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();

    factory.setValidating(true);

    factory.setNamespaceAware(true);

    factory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaLanguage",

    "http://www.w3.org/2001/XMLSchema");

    DocumentBuilder builder = factory.newDocumentBuilder();

    builder.setErrorHandler(new RaiseOnErrorHandler());

    builder.parse(new InputSource(xmlStream));

    xmlStream.close();

    }

    public static class RaiseOnErrorHandler implements ErrorHandler {

    public void warning(SAXParseException e) throws SAXException {

    throw new RuntimeException(e);

    }

    public void error(SAXParseException e) throws SAXException {

    throw new RuntimeException(e);

    }

    public void fatalError(SAXParseException e) throws SAXException {

    throw new RuntimeException(e);

    }

    }

    即使xml文件引用了url,也可以通过手动指定xsd(请参阅此处的其他答案)或使用“XML目录”样式解析程序,避免从网络中引用引用的XSD。 Spring显然也可以拦截URL请求以提供本地文件进行验证。 或者您可以通过setResourceResolver设置自己的,例如:

    Source xmlFile = new StreamSource(xmlFileLocation);

    SchemaFactory schemaFactory = SchemaFactory

    .newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

    Schema schema = schemaFactory.newSchema();

    Validator validator = schema.newValidator();

    validator.setResourceResolver(new LSResourceResolver() {

    @Override

    public LSInput resolveResource(String type, String namespaceURI,

    String publicId, String systemId, String baseURI) {

    InputSource is = new InputSource(

    getClass().getResourceAsStream(

    "some_local_file_in_the_jar.xsd"));

    // or lookup by URI, etc...

    return new Input(is); // for class Input see

    // https://stackoverflow.com/a/2342859/32453

    }

    });

    validator.validate(xmlFile);

    另见这里的另一个教程。

    rogerdpack answered 2019-03-02T10:12:42Z

    4 votes

    使用Java 7,您可以按照包描述中提供的文档进行操作。

    // parse an XML document into a DOM tree

    DocumentBuilder parser = DocumentBuilderFactory.newInstance().newDocumentBuilder();

    Document document = parser.parse(new File("instance.xml"));

    // create a SchemaFactory capable of understanding WXS schemas

    SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

    // load a WXS schema, represented by a Schema instance

    Source schemaFile = new StreamSource(new File("mySchema.xsd"));

    Schema schema = factory.newSchema(schemaFile);

    // create a Validator instance, which can be used to validate an instance document

    Validator validator = schema.newValidator();

    // validate the DOM tree

    try {

    validator.validate(new DOMSource(document));

    } catch (SAXException e) {

    // instance document is invalid!

    }

    Paulo Fidalgo answered 2019-03-02T10:13:15Z

    3 votes

    如果您有Linux机器,则可以使用免费的命令行工具SAXCount。 我发现这非常有用。

    SAXCount -f -s -n my.xml

    它验证了dtd和xsd。50s文件的5s。

    在debian squeeze中,它位于包“libxerces-c-samples”中。

    dtd和xsd的定义必须在xml中! 您无法单独配置它们。

    jens answered 2019-03-02T10:14:02Z

    3 votes

    还有一个答案:既然你说你需要验证你正在生成的文件(写作),你可能想要在写作时验证内容,而不是先写,然后回读进行验证。 如果您使用基于SAX的编写器,您可以使用JDK API进行Xml验证:如果是这样,只需通过调用'Validator.validate(source,result)'来链接验证器,其中source来自您的编写器,结果是 输出需要去哪里。

    或者,如果您使用Stax编写内容(或使用或可以使用stax的库),Woodstox也可以在使用XMLStreamWriter时直接支持验证。 这是一篇博客文章,展示了如何完成:

    StaxMan answered 2019-03-02T10:14:36Z

    2 votes

    如果以编程方式生成XML文件,则可能需要查看XMLBeans库。 使用命令行工具,XMLBeans将基于XSD自动生成和打包一组Java对象。 然后,您可以使用这些对象基于此模式构建XML文档。

    它内置了对模式验证的支持,可以将Java对象转换为XML文档,反之亦然。

    Castor和JAXB是其他Java库,它们与XMLBeans具有类似的用途。

    Todd answered 2019-03-02T10:15:17Z

    0 votes

    您在寻找工具或图书馆吗?

    就库而言,几乎事实上的标准是Xerces2,它同时具有C ++和Java版本。

    不过要事先警告,这是一个重量级的解决方案。 但话说回来,针对XSD文件验证XML是一个相当沉重的权重问题。

    至于为你做这个的工具,XMLFox似乎是一个不错的免费软件解决方案,但没有亲自使用它我不能肯定地说。

    Adam answered 2019-03-02T10:16:06Z

    0 votes

    使用JAXB,您可以使用以下代码:

    @Test

    public void testCheckXmlIsValidAgainstSchema() {

    logger.info("Validating an XML file against the latest schema...");

    MyValidationEventCollector vec = new MyValidationEventCollector();

    validateXmlAgainstSchema(vec, inputXmlFileName, inputXmlSchemaName, inputXmlRootClass);

    assertThat(vec.getValidationErrors().isEmpty(), is(expectedValidationResult));

    }

    private void validateXmlAgainstSchema(final MyValidationEventCollector vec, final String xmlFileName, final String xsdSchemaName, final Class> rootClass) {

    try (InputStream xmlFileIs = Thread.currentThread().getContextClassLoader().getResourceAsStream(xmlFileName);) {

    final JAXBContext jContext = JAXBContext.newInstance(rootClass);

    // Unmarshal the data from InputStream

    final Unmarshaller unmarshaller = jContext.createUnmarshaller();

    final SchemaFactory sf = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

    final InputStream schemaAsStream = Thread.currentThread().getContextClassLoader().getResourceAsStream(xsdSchemaName);

    unmarshaller.setSchema(sf.newSchema(new StreamSource(schemaAsStream)));

    unmarshaller.setEventHandler(vec);

    unmarshaller.unmarshal(new StreamSource(xmlFileIs), rootClass).getValue(); // The Document class is the root object in the XML file you want to validate

    for (String validationError : vec.getValidationErrors()) {

    logger.trace(validationError);

    }

    } catch (final Exception e) {

    logger.error("The validation of the XML file " + xmlFileName + " failed: ", e);

    }

    }

    class MyValidationEventCollector implements ValidationEventHandler {

    private final List validationErrors;

    public MyValidationEventCollector() {

    validationErrors = new ArrayList<>();

    }

    public List getValidationErrors() {

    return Collections.unmodifiableList(validationErrors);

    }

    @Override

    public boolean handleEvent(final ValidationEvent event) {

    String pattern = "line {0}, column {1}, error message {2}";

    String errorMessage = MessageFormat.format(pattern, event.getLocator().getLineNumber(), event.getLocator().getColumnNumber(),

    event.getMessage());

    if (event.getSeverity() == ValidationEvent.FATAL_ERROR) {

    validationErrors.add(errorMessage);

    }

    return true; // you collect the validation errors in a List and handle them later

    }

    }

    razvanone answered 2019-03-02T10:16:34Z

    0 votes

    验证在线模式

    Source xmlFile = new StreamSource(Thread.currentThread().getContextClassLoader().getResourceAsStream("your.xml"));

    SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

    Schema schema = factory.newSchema(Thread.currentThread().getContextClassLoader().getResource("your.xsd"));

    Validator validator = schema.newValidator();

    validator.validate(xmlFile);

    验证本地模式

    使用Java进行脱机XML验证

    jschnasse answered 2019-03-02T10:17:20Z

    -3 votes

    我只需要一次针对XSD验证XML,所以我尝试了XMLFox。 我发现它非常令人困惑和奇怪。 帮助说明似乎与界面不匹配。

    我最终使用了LiquidXML Studio 2008(v6),它更易于使用且更加直接熟悉(UI与我经常使用的Visual Basic 2008 Express非常相似)。 缺点:验证功能不是免费版本,因此我不得不使用30天试用版。

    KnomDeGuerre answered 2019-03-02T10:17:55Z

    展开全文
  • NULL 博文链接:https://nickfover.iteye.com/blog/2155663
  • Java运行时库支持验证。...您可能应该使用javax.xml.validation.Validator.importjavax.xml.XMLConstants;importjavax.xml.transform.Source;importjavax.xml.transform.stream.StreamSource;importjav...
  • xml 文件与xsd文件的转化以及xsd验证xml的合法性
  • xsdxml 文件放在工程 bin路径下即可。package xmlValidate;import java.io.ByteArrayInputStream;import java.io.FileNotFoundException;import java.io.IOException;import javax.xml.XMLConsta...
  • 使用XSD验证xml

    千次阅读 2016-08-26 19:33:44
    使用XSD验证XML本文简单介绍如何使用XSD验证自己的xml。项目中我们经常使用xml作为配置或者数据交互的文件格式,在解析XML前最好验证一下或者在生成xml文件后验证一下生成的文件格式是正确,这样可以避免解析时出现...
  • 通过xsd校验xml

    2022-09-07 14:38:45
    } } /** * 验证xml文档是否符合xsd校验 * @param xsdInputStream * @param xmlInputStream * @return true 通过校验, false xml有语法错误或未通过校验 * @throws SAXException 校验过程出错 * @throws ...
  • C# 使用xsd文件验证XML 格式是否正确     核心示例代码: //创建xmlDocument XmlDocument doc = new XmlDocument(); //创建声明段 如&lt;?xml version="1.0" encoding="utf-8" ...
  • 写一个Java程序引用xsd文件验证xml文件的有效性,若是xml文件格式有效返回true,否则返回false。
  • XML 文件(a.xml): &lt;?xml version="1.0" encoding="utf-8" ?&gt; &lt;PROFILE&gt; &lt;PROFILEID&gt;0001&lt;/PROFILEID&gt; ...
  • 使用架构(XSD)验证XML文件假使说XML是一个数据库,那么XSD就是这个数据库的结构。由此可见,XSD是如此重要,如果没有它,我们如何声明以及验证我们需要的XML数据文件的格式和合法性呢?那是不可能完成的任务,如果你...
  • java xsd校验xml文件

    2022-02-09 15:21:37
    saxParser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource","file:"+"xsd文件路径"); SAXValidator validator = new SAXValidator(saxParser.getXMLReader()); validator.setErrorHandler...
  • XML Schema 语言也称作 XML Schema 定义(XML Schema Definition,XSD),作用是定义 XML 文档的合法构建模块,类似 DTD,但更加强大。作用有: ①定义可出现在文档中的元素 ②定义可出现在文档中的属性 ③定义哪个...
  • xsd文件 有许多工具可用于根据XSD验证XML文档。 其中包括操作系统脚本和工具,例如xmllint ,XML编辑器和IDE,甚至是在线验证器。 由于前面提到的方法的局限性或问题,我发现拥有自己的易于使用的XML验证工具很有用...
  • 验证过程将验证XML文档是指定的XML模式文件或XSD文件的实例。在此示例中,我们将验证records.xml下面的文件是否在records.xsd架构实例中。首先,我们将创建以下XML文件和应遵循的XSD文件。XML文件:...
  • 小编典典Java运行时库支持验证。...你可能应该使用javax.xml.validation.Validator。import javax.xml.XMLConstants;import javax.xml.transform.Source;import javax.xml.transform.stream.StreamSource;import ...
  • person.xml:(不带命名空间) 张三 120 李四 20 person.xsd: 本文档定义Persons.xml的格式
  • 可以一个指定的XML Schema来验证某个XML文档,以检查该XML文档是否符合其要求。文档设计者可以通过XML Schema指定一个XML...简而言之,XSD文件用来定义Xml的格式的文件,而XML是按照一定的Xsd格式生成的数据文档。
  • 通过XSD文件XML文件进行格式验证

    千次阅读 2017-03-03 09:16:17
    import java.io.ByteArrayInputStream; import java.io.File; import java.io.FileInputStream; import java.io.FileNotFoundException;...import java.io.IOException;...import javax.xml.XMLConstants
  • conf.xsd--------------------------------- <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.w3school.com.cn" xmlns=...
  • 验证xml文件xsd是否匹配

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 43,129
精华内容 17,251
热门标签
关键字:

如何用xsd文件验证xml