Problem validating an XML document with a schema containing xs:include

I have a problem using an include statement in xsd. I try to include another
schema by using the include statement:
<xsd:include schemaLocation="../../XXX.xsd"/>
and get the xjc error:
s4s-att-invalid-value: Invalid attribute value for 'schemaLocation' in element 'include': cvc-datatype-valid.1.2.1.
Can anybody give me a hint what goes wrong here? THANKS!!!!
ayache

Your schemaLocation value is not a URI? To me, it looks like the value should conform to this:
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI
I will let you read all those specs to see whether that is your problem.

Similar Messages

Validating an XML document to a schema using ColdFusion

This is something I have never tried before. We created an XML Schema to define XML documents we expect to receive from various entities.   When we receive the document, we would like to validate it before processing it. I think ColdFusion is up to this from reading the documentation, but we have not got anything working yet.
When we try and xmlParse() our test XML file against the XML schema we get the following error. When we use a web based XML validation tool and feed it the same XML file and schema it validates just fine.
An error occured while parsing an XML document.
[Error] :2:6: cvc-elt.1: Cannot find the declaration of element 'pur'.
The error occurred in D:\playground\warren\ppur_file_import.cfm: line 57
55 :
56 :
57 : <cfset xmldoc = XmlParse(ExpandPath(filepath), true, ExpandPath(validator)) />
58 : <cfdump var="#xmldoc#">
59 : <cfabort>
Searching for the error has not provided me any useful hints. Can anybody here?

XML SCHEMA
<?xml version="1.0" encoding="iso-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     
     <xs:simpleType name="RECORD_ID">
          <xs:restriction base="xs:string">
               <xs:pattern value="[AaBbCc]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="REPORT_MONTH">
          <xs:restriction base="xs:integer">
               <xs:pattern value="(0[1-9]|1[0-2])"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="REPORT_YEAR">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{2}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="MFG_FIRMNO">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{7}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="LABEL_SEQ_NO">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{5}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="REVISION_NO">
          <xs:restriction base="xs:string">
               <xs:pattern value="[A-Za-z]{2}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="REG_FIRMNO">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{7}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="GROWER_ID">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{11}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="CEDTS_IND">
          <xs:restriction base="xs:string">
               <xs:pattern value="[Ee]|[ ]"/>
               
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="APPLIC_DT">
          <xs:restriction base="xs:integer">
               <xs:pattern value="(0[1-9]|1[0-2])(0[1-9]|[1-2][0-9]|3[0-1])([0-9]{2})"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="SITE_CODE">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{6}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="QUALIFY_CD">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{2}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="PLANTING_SEQ">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ACRE_TREATED">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{8}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="UNIT_TREATED">
          <xs:restriction base="xs:string">
               <xs:pattern value="[ATSCKUPatsckup]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="AMT_PRD_USED">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{10}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="UNIT_OF_MEAS">
          <xs:restriction base="xs:string">
               <xs:pattern value="LB|OZ|GA|QT|PT|KG|GR|LI|ML"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="DOCUMENT_NO">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{8}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="LINE_ITEM">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{4}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="PROCESS_DT">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{4}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="BATCH_NO">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-5][0-9][0-9][0-9]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="COUNTY_CD">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-5][0-9]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="SECTION">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{2}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="TOWNSHIP">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{2}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="TSHIP_DIR">
          <xs:restriction base="xs:string">
               <xs:pattern value="[NSns]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="RANGE">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{2}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="RANGE_DIR">
          <xs:restriction base="xs:string">
               <xs:pattern value="[EWew]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="BASE_LN_MER">
          <xs:restriction base="xs:string">
               <xs:pattern value="[HMShms]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="AER_GND_IND">
          <xs:restriction base="xs:string">
               <xs:pattern value="[AFGOafgo]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="SITE_LOC_ID">
          <xs:restriction base="xs:string">
               <xs:pattern value="[-0-9 ]+"/>
               
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ACRE_PLANTED">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{8}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="UNIT_PLANTED">
          <xs:restriction base="xs:string">
               <xs:pattern value="[ATSCKUPatsckup]"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="APPLIC_TM">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{4}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="APPLIC_CNT">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{6}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="FUME_CD">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[0-9]{4}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="LICENSE_NO">
          <xs:restriction base="xs:integer">
               <xs:pattern value="[-0-9A-Za-z]{13}"/>
          </xs:restriction>
     </xs:simpleType>
     
     
     <xs:complexType name="application_data_abs" abstract="true">
          <xs:sequence>
               <xs:element name="GROWER_ID" type="GROWER_ID" />
               <xs:element name="CEDTS_IND" type="CEDTS_IND" />
               <xs:element name="APPLIC_DT" type="APPLIC_DT" />
               <xs:element name="SITE_CODE" type="SITE_CODE" />
               <xs:element name="QUALIFY_CD" type="QUALIFY_CD" />
               <xs:element name="PLANTING_SEQ" type="PLANTING_SEQ" />
               <xs:element name="ACRE_TREATED" type="ACRE_TREATED" />
               <xs:element name="UNIT_TREATED" type="UNIT_TREATED" />
               <xs:element name="AMT_PRD_USED" type="AMT_PRD_USED" />
               <xs:element name="UNIT_OF_MEAS" type="UNIT_OF_MEAS" />
               <xs:element name="DOCUMENT_NO" type="DOCUMENT_NO" />
               <xs:element name="LINE_ITEM" type="LINE_ITEM" />
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="application_abs" abstract="true">
          <xs:sequence>
               <xs:element name="key_data" type="key_data" />
               <xs:element name="product_data" type="product_data" />
          </xs:sequence>
     </xs:complexType>
     
     
     <xs:complexType name="product_data">
          <xs:sequence>
               <xs:element name="MFG_FIRMNO" type="MFG_FIRMNO" />
               <xs:element name="LABEL_SEQ_NO" type="LABEL_SEQ_NO"/>
               <xs:element name="REVISION_NO" type="REVISION_NO" />
               <xs:element name="REG_FIRMNO" type="REG_FIRMNO" />
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="key_data">
          <xs:sequence>
               <xs:element name="RECORD_ID" type="RECORD_ID" />
               <xs:element name="COUNTY_KEY">
                    
               </xs:element>
               <xs:element name="REPORT_MONTH" type="REPORT_MONTH" />
               <xs:element name="REPORT_YEAR" type="REPORT_YEAR" />
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="fileInfo">
          <xs:sequence>
               <xs:element name="PROCESS_DT" type="PROCESS_DT" />
               <xs:element name="BATCH_NO" type="BATCH_NO" />
               <xs:element name="COUNTY_CD" type="COUNTY_CD" />
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="mtrs_data">
          <xs:sequence>
               <xs:element name="SECTION" type="SECTION" />
               <xs:element name="TOWNSHIP" type="TOWNSHIP" />
               <xs:element name="TSHIP_DIR" type="TSHIP_DIR" />
               <xs:element name="RANGE" type="RANGE" />
               <xs:element name="RANGE_DIR" type="RANGE_DIR" />
               <xs:element name="BASE_LN_MER" type="BASE_LN_MER" />
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="ag_application_data">
          <xs:complexContent>
               <xs:extension base="application_data_abs">
                    <xs:sequence>
                         <xs:element name="AER_GND_IND" type="AER_GND_IND" />
                         <xs:element name="SITE_LOC_ID" type="SITE_LOC_ID" />
                         <xs:element name="ACRE_PLANTED" type="ACRE_PLANTED" />
                         <xs:element name="UNIT_PLANTED" type="UNIT_PLANTED" />
                         <xs:element name="APPLIC_TM" type="APPLIC_TM" />
                         <xs:element name="FUME_CD" type="FUME_CD" />
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="nonag_application_data">
          <xs:complexContent>
               <xs:extension base="application_data_abs">
                    <xs:sequence>
                         <xs:element name="APPLIC_CNT" type="APPLIC_CNT" />
                         <xs:element name="LICENSE_NO" type="LICENSE_NO" />
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:complexType name="ag_application">
          <xs:complexContent>
               <xs:extension base="application_abs">
                    <xs:sequence>
                         <xs:element name="mtrs_data" type="mtrs_data" />
                         <xs:element name="application_data" type="ag_application_data" />
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:complexType name="nonag_application">
          <xs:complexContent>
               <xs:extension base="application_abs">
                    <xs:sequence>
                         <xs:element name="application_data" type="nonag_application_data" />
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="data_lines">
          <xs:sequence>
               <xs:element name="Non_Ag" type="nonag_application" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element name="Ag" type="ag_application" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="pur">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="County" minOccurs="0" maxOccurs="1">
                         
                    </xs:element>
                    
                    <xs:element name="File" type="fileInfo" minOccurs="1" maxOccurs="1"/>
                    
                    <xs:element name="Data" type="data_lines" minOccurs="1" maxOccurs="1"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>

Has anybody tried creating and validating a XML doc with XML Schema?

Hi,
Has anybody tried creating and validating a XML doc with XML Schema?

With XMLBeans, an XML document may be created from and validated with an XML schema.

Vivado 2013.4 ERROR: [IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order

Hello,
I just downloaded and installed Vivado 2013.4 on my Xubuntu 12.04 machine. But when I try to add IP from the IP catalog, as in the ug937 Lab1 step2, it fails with obscure error messages (see below).
Here's basically what I did:
-In the Flow Navigator, i select the IP Catalog button.
-In the search field of the IP Catalog, I type DDS.
-then I double-click the DDS Compiler and my error occure.
Please Help,
Jerome.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
Analysis Results[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
set_property target_language Verilog [current_project]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
sources_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
update_compile_order -fileset sim_1
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-2313] Loaded Vivado IP repository '/opt/Xilinx/Vivado/2013.4/data/ip'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-1704] No user IP repositories specified
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
Vivado Commands[Project 1-11] Changing the constrs_type of fileset 'constrs_1' to 'XDC'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
sim_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-234] Refreshing IP repositories
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
set_property constrs_type XDC [current_fileset -constrset]

We had the same problem when switching to Ubuntu 14.04, and there actually is a solution for it: make sure your locales are set to English.
$> env | grep LC_*
should only show english (or C) locales, all others are known to cause parsing errors in some numbers, usually caused by wrong string-to-float conversions (e.g. 18,29 in german is 18.29 in english). You can change the locales in the file /etc/default/localesThis is not the first time we had problems with the locale settings, Xilinx does not seem to test their software with anything else than en_US, causing obscure bugs like this one.
HTH
Philipp

Catch all error information while validating xml content with xsd schema

Hi experts,
I created a java mapping to validating the input xml content with xsd schema (schema validation). What I want is to catch all error message to the xml not just the first error. I used SAXParser in sapxmltoolkit.jar to do the schema validation. The below is a part of my java mapping.
XMLReader parser = XMLReaderFactory.createXMLReader("com.sap.engine.lib.xml.parser.SAXParser");
parser.setFeature( "http://xml.org/sax/features/validation" , true);
parser.setFeature( "http://apache.org/xml/features/validation/schema" , true);
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",this.getClass().getClassLoader().getResourceAsStream(schema)); // schema is my schema name
parser.setErrorHandler(new ParseErrorHandler()); // ParseErrorHandler is my own ErrorHandler which extends DefaultHandler
parser.parse(new InputSource(new ByteArrayInputStream(sinput.getBytes())));
// In error handler, I comment all code so as not to throw any exception
public class ParseErrorHandler extends DefaultHandler
     public void error(SAXParseException e) throws SAXException
          // sSystem.out.println("Error" + e.getMessage());
          // throw e;
     public void fatalError(SAXParseException e)
          // throw e;
          // System.out.println("SAP Fatal Error" + e.getMessage());
Unfortunately the program always stopped while catching the first error. Check the below log.
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
ERRORS :
cvc-simple-type : information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is not valid, because it's value does not satisfy the constraints of facet 'minLength' with value '1'.
cvc-data : information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is is not valid with respoct to the corresponding simple type definition.
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' is associated with invalid data.
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]/:To[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]/:Header[1]' is not valid with respect to it's complex type definition..
cvc-element : element information item '/:ShipNotice[1]' is not valid with respect to it's complex type definition..
-> com.sap.engine.lib.xml.parser.ParserException:
I tried using Xerces and JAXP to do validation, the same error happened. I have no idea on this. Does xi has its own error handler logic? Is there any body can make me get out of this?
Thanks.

<h6>Hi experts,
<h6>
<h6>I created a java mapping to validating the input xml content with xsd schema (schema validation). What I want is to catch all <h6>error message to the xml not just the first error. I used SAXParser in sapxmltoolkit.jar to do the schema validation. The below <h6>is a part of my java mapping.
<h6>XMLReader parser = XMLReaderFactory.createXMLReader("com.sap.engine.lib.xml.parser.SAXParser");
<h6>parser.setFeature( "http://xml.org/sax/features/validation" , true);
<h6>parser.setFeature( "http://apache.org/xml/features/validation/schema" , true);
<h6>parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");          <h6>parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource",this.getClass().getClassLoader().getResourceAsStream(schema)); <h6>// schema is my schema name
<h6>parser.setErrorHandler(new ParseErrorHandler()); // ParseErrorHandler is my own ErrorHandler which extends Default Handler
<h6>parser.parse(new InputSource(new ByteArrayInputStream(sinput.getBytes())));
<h6>
<h6>// In error handler, I comment all code so as not to throw any exception
<h6>public class ParseErrorHandler extends DefaultHandler
<h6>{
<h6>     public void error(SAXParseException e) throws SAXException
<h6>     {
<h6>          // sSystem.out.println("Error" + e.getMessage());
<h6>          // throw e;
<h6>     }
<h6>
<h6>     public void fatalError(SAXParseException e)
<h6>     {
<h6>          // throw e;
<h6>          // System.out.println("SAP Fatal Error" + e.getMessage());
<h6>
<h6>     }
<h6>
<h6>}
<h6>
<h6>Unfortunately the program always stopped while catching the first error. Check the below log.
<h6>
<h6>com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
<h6>ERRORS :
<h6>cvc-simple-type : information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is not valid, because it's value does not satisfy the constraints of facet 'minLength' with value '1'.
<h6>cvc-data : information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is is not valid with respoct to the corresponding simple type definition.
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]/:CityName[1]' <h6>is associated with invalid data.
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]/:AddressInformation[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]/:PartnerInformation[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]/:To[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item <h6>'/:ShipNotice[1]/:Header[1]' <h6>is not valid with respect to it's complex type definition..
<h6>cvc-element : element information item '/:ShipNotice[1]' is not valid with <h6>respect to it's complex type definition..
<h6> -> com.sap.engine.lib.xml.parser.ParserException:
<h6>
<h6>
<h6>I tried using Xerces and JAXP to do validation, the same error happened. I have no idea on this. Does xi has its own error <h6>handler logic? Is there any body can make me get out of this?
<h6>Thanks.

How to validate an XML file with XSD Schema on JDK 1.4

Hi
I'm looking for samples how to validate xml files with xsd schema using jsdk 1.4
Thank you.

This is how.
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.dom.DOMResult;
import javax.xml.transform.dom.DOMSource;
import javax.xml.validation.Schema;
import javax.xml.validation.SchemaFactory;
import javax.xml.validation.Validator;
DocumentBuilderFactory dbfac = DocumentBuilderFactory.newInstance();
dbfac.setNamespaceAware(true);
SchemaFactory factory1 = SchemaFactory
.newInstance("http://www.w3.org/2001/XMLSchema");
Schema schema = factory1.newSchema(new File("person.xsd"));
dbfac.setSchema(schema);
DocumentBuilder dbparser1 = dbfac.newDocumentBuilder();
Document doc1 = dbparser1.parse(new File("person.xml"));
Validator validator1 = schema.newValidator();
DOMSource dm1 = new DOMSource(doc1);
DOMResult domresult1 = new DOMResult();
validator1.validate(dm1, domresult1);

Using java to fill in the blanks in an xml document via a schema

Hi all
What im trying to do is basically take an xml document and run it through a xml schema validator and then if the xsd has any default values to basically populate the original xml document with these default values
e.g.
<root>
<name>dave</name>
<name></name>
</root>
the schema would be something like
<xs:element name="name" default="bobby">
after schema validation i would want the document to be
<root>
<name>dave</name>
<name>bobby</name>
</root>
is that something possible to do in java with any specific xml frameworks out there? if so can any one give me any pointers in the right direction?

i assume by the lack of response this cannot be done then :(

Transforming signed XML document with namespace invalidates signature

I am running into a problem signing an XML document. Well, signing the document isn't the problem, as I can sign it and then verify the signature with the public key successfully. The problem comes when I transform the document to a string. It all appears to be OK, but when I transform it back, the hash no longer verifies. After more testing, it appears that the issue is related to namespaces. When I remove namespaces from the document, the signing and transformations work just fine. Does anyone have any insight on this?
Here is how I am transforming the document to an XML string that I and back.
    try
      signSAML( doc, assertionElement );
      xmlSource = new DOMSource( doc );
      baos = new ByteArrayOutputStream();
      outputTarget = new StreamResult( baos );
      xmlString = new String( new ByteArrayInputStream( baos.toByteArray() ) );
      transformerFactory = TransformerFactory.newInstance();
      transformer = transformerFactory.newTransformer();
      transformer.transform( xmlSource, outputTarget );
      boolean verified = verify( doc );
      if ( verified )
        System.out.println( "Verified" );
      else
        System.out.println( "UNVerified" );
    catch ( Exception e )
      // TODO Auto-generated catch block
      e.printStackTrace();
    }

jtahlborn wrote:
i'm not talking about the transform, i'm talking about this line:
xmlString = new String( new ByteArrayInputStream( baos.toByteArray() ) );which is a great way to break xml data.Yes. That's not the only kind of data it's good at breaking, either.
To the OP: just have your transform output to a StringWriter in the first place. Don't muck about converting between chars and bytes unless you know the correct encoding and use it. Which you don't know it and you didn't use it.

Open XML document with proper layout

Hi,
I created my own XML form and I have problem when accessing the document within "KM Content".
Indeed, when I click on the XML file generated by the XML Form it doesn't render it with the "Show" form but rather displays it as an usual XML document (with all its tags).
Hint:
I linked my iView to a custom CM repository. But, if I link my iView containing the XML Form to the out-of-the-box CM repository "/documents", it works fine.
What should I do to make this work?
Thanks in advance,
Eric

Hi Eric,
in the Configuration under 'System Administration' -> 'System Configuration' -> 'Knowledge Management' -> 'Content Management' -> 'Repository Filters' you can find a filter named 'xmlforms_filter'. Some repositories are registered for this filter (in the standard e.g. documents). You should add your repositoriy here. After that the files in your repository should use the Show-form when being displayed.
Hope this helps
Karin

Binding Xml file with Xsd Schema

Hello
everybody there.
I am trying to make an application where word files are converted into xml.
For that i have used org.exolab.castor and org.apache.poi.hwpf.
Now the problem is that i was able to generate the xml file from word, but when i am binding it with XMLSchema.xsd following error is coming.
java.lang.IllegalArgumentException: getSimpleType: the simple type 'formChoice' is not a built-in type as defined in XML Schema specification.
     at org.exolab.castor.xml.schema.Schema.getSimpleType(Schema.java:1289)
     at org.exolab.castor.xml.schema.Schema.addSimpleType(Schema.java:583)
     at org.exolab.castor.xml.schema.reader.SchemaUnmarshaller.endElement(SchemaUnmarshaller.java:643)
     at org.exolab.castor.xml.schema.reader.Sax2ComponentReader.endElement(Sax2ComponentReader.java:198)
     at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1392)
     at org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1550)
     at org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1149)
     at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
     at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
     at org.exolab.castor.builder.SourceGenerator.generateSource(SourceGenerator.java:430)
     at org.exolab.castor.builder.SourceGenerator.generateSource(SourceGenerator.java:485)
     at TempHwpf.<init>(TempHwpf.java:35)
     at TempHwpf.main(TempHwpf.java:44)the code for binding my xml file with xsd schema is as under:-
SourceGenerator sourcegen = new SourceGenerator();
sourcegen.getVersion();
System.out.println(sourcegen.getVersion());
sourcegen.generateSource("XMLSchema.xsd","packagename");I have checked XMLSchema.xsd file, in that formChoice is already defined, than also error is coming.
can anyone help me out. first i thought that XMLSchema.xsd which i have is not proper, but i downloaded it again from w3c.org,
than also same error is shown.
please help me out.
waiting for reply.
milind

Please do not double-post. http://forum.java.sun.com/thread.jspa?threadID=5134447&tstart=0
Then use Stax (Woodstock) or Saxon.
- Saish

ORA-00600 problem when create XMLType table with registerd schema

Hi,
I am using Oracle9i Enterprise Edition Release 9.2.0.4.0 on RedHat Linux 7.2
I found a problem when I create table with registered schema with follow content:
     <xs:element name="body">
          <xs:complexType>
               <xs:sequence>
               </xs:sequence>
               <xs:attribute name="id" type="xs:ID"/>
               <xs:attribute name="class" type="xs:NMTOKENS"/>
               <xs:attribute name="style" type="xs:string"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="body.content">
          <xs:complexType>
               <xs:choice minOccurs="0" maxOccurs="unbounded">
                    <xs:element ref="p"/>
                    <xs:element ref="hl2"/>
                    <xs:element ref="nitf-table"/>
                    <xs:element ref="ol"/>
               </xs:choice>
               <xs:attribute name="id" type="xs:ID"/>
          </xs:complexType>
     </xs:element>
Does Oracle not support element reference to other element with dot?
For instance, body -> body.content
Thanks for your attention.

Sorry, amendment on the schema
     <xs:element name="body">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="body.head" minOccurs="0"/>
                    <xs:element ref="body.content" minOccurs="0" maxOccurs="unbounded"/>
                    <xs:element ref="body.end" minOccurs="0"/>
               </xs:sequence>
               <xs:attribute name="id" type="xs:ID"/>
               <xs:attribute name="class" type="xs:NMTOKENS"/>
               <xs:attribute name="style" type="xs:string"/>
          </xs:complexType>
     </xs:element>

How to validate xml file with XSD schema ?? in JDK1.4.2

How to validate xml file with XSD schema ?? in JDK1.4.2
i dont want to use new Xerec Jar ...
Suggest option ...

Please do not double-post. http://forum.java.sun.com/thread.jspa?threadID=5134447&tstart=0
Then use Stax (Woodstock) or Saxon.
- Saish

Please help; how to write XML document with JSP?

I try to write XML document with JSP...
But I got wrong results everytime.
The result is not XML file displayed in the browser,
but HTML file.
I even tried to use HTML special code for <, >, "
but still display as HTML file not XML file.
How to do this?
Thanks in advance. I put my codes below.
Sincerely,
Ted.
================
Here is code for the JSP (called stk.jsp):
<%@ page contentType="text/xml" %>
<%@ page import="bean.Stock" %>
<jsp:useBean id="portfolio" class="bean.Portfolio" />
<% java.util.Iterator pfolio = portfolio.getPortfolio();
Stock stock = null; %>
<?xml version="1.0" encoding="UTF-8"?>
<portfolio>
<% while (pfolio.hasNext())
stock = (Stock) pfolio.next(); %>
<stock>
<symbol>
<%=stock.getSymbol() %>
</symbol>
<name><%=stock.getName() %> </name>
<price><%=stock.getPrice() %> </price>
</stock>
<% } %>
</portfolio>
=================
Here is the code for bean.Stock:
package bean;
public class Stock implements java.io.Serializable
String symbol, name;
float price;
public Stock(String symbol, String name, float price)
this.symbol = symbol;
this.name = name;
this.price = price;
public String getSymbol()
return symbol;
public String getName()
return name;
public float getPrice()
return price;
===============
And here is bean.Portfolio:
package bean;
import java.util.Iterator;
import java.util.Vector;
public class Portfolio implements java.io.Serializable
private Vector portfolio = new Vector();
public Portfolio()
portfolio.addElement(new Stock("SUNW", "Sun Microsystem", 34.5f));
portfolio.addElement(new Stock("HWP", "Hewlett Packard", 15.15f));
portfolio.addElement(new Stock("AMCC", "Applied Micro Circuit Corp.", 101.35f));
public Iterator getPortfolio()
return portfolio.iterator();
}

Hi
I'm not sure whta your query is but I tested your code as it is has been pasted and it seems to work fine. There is an XML output that I'm getting.
Keep me posted.
Good Luck!
Eshwar Rao
Developer Technical Support
Sun microsystems
http://www.sun.com/developers/support

Problem when trying to load an XML document with DTD or XML SCHEMA

Hello
I have tried to load an XML document in Data Services, and I created the xsd file and Dtd file. (With altova xml spy software automatically) to import into SAP Data Services 3.2. .
In Data Services I created the dtd import file DTD and then called the XML file from the DTD (the xml file is validated vs the dtd file), and I could not read the xml correctly because it tells me that an ELEMENT called <item> expected joiners who did not come in the structure of import (dtd), but if the xml.
I understand that the document root is the label: CUSTOMER_FULL_2014, the data flow is as follows:CARGA_XML_CUSTOMER |
Turns out the joiners element is used to separate the xml elements are repeated, but is used at different levels. My idea is that the design will dtd second, or something I'm missing or is incorrectly stated.
Thank you.
xml
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
<?xml version="1.0" encoding="utf-8"?>
<CUSTOMER_FULL_2014>
<item>
<CUST_NO>202222</CUST_NO>
<ADDRESS>
<item>
<SHIP_TO>202222</SHIP_TO>
<NAME1>Henley.</NAME1>
<STREET>Vitacura #40</STREET>
<CITY>LIMA</CITY>
</item>
</ADDRESS>
<EQUIPMENT>
<item>
<EQUI_NO>81623</EQUI_NO>
</item>
<item>
<EQUI_NO>81633</EQUI_NO>
</item>
<item>
<EQUI_NO>81993</EQUI_NO>
</item>
<item>
<EQUI_NO>82003</EQUI_NO>
</item>
<item>
<EQUI_NO>82013</EQUI_NO>
</item>
<item>
<EQUI_NO>82103</EQUI_NO>
</item>
<item>
<EQUI_NO>82113</EQUI_NO>
</item>
<item>
<EQUI_NO>581203</EQUI_NO>
</item>
<item>
<EQUI_NO>900003-EMER</EQUI_NO>
</item>
<item>
<EQUI_NO>9000033-STOCK</EQUI_NO>
</item>
</EQUIPMENT>
<STORAGE_LOC>
<item>
<STOR_LOC_NO>0001</STOR_LOC_NO>
<DESCRIPTION>01 Parts Center</DESCRIPTION>
</item>
<item>
<STOR_LOC_NO>0056</STOR_LOC_NO>
<DESCRIPTION>56 henley</DESCRIPTION>
</item>
</STORAGE_LOC>
</item>
<item>
<CUST_NO>2007933434343</CUST_NO>
<ADDRESS>
<item>
<SHIP_TO>2007933434343</SHIP_TO>
<NAME1>Campos de Almacenaje SA</NAME1>
<STREET>Calacoto2, Calle 1</STREET>
<HOUSE_NO>Piso 1</HOUSE_NO>
<CITY>La Paz</CITY>
</item>
</ADDRESS>
<EQUIPMENT>
<item>
<EQUI_NO>90000-EMER</EQUI_NO>
</item>
<item>
<EQUI_NO>90000333-STOCK</EQUI_NO>
</item>
</EQUIPMENT>
<STORAGE_LOC>
<item>
<STOR_LOC_NO>00012</STOR_LOC_NO>
<DESCRIPTION>01 Parts Center</DESCRIPTION>
</item>
<item>
<STOR_LOC_NO>0056</STOR_LOC_NO>
<DESCRIPTION>56 henley</DESCRIPTION>
</item>
</STORAGE_LOC>
</item>
<item>
<CUST_NO>200801333</CUST_NO>
<ADDRESS>
<item>
<SHIP_TO>200801333</SHIP_TO>
<NAME1>CONSTRUCTORA SA.</NAME1>
<STREET>Ruta Panamericana Km 100</STREET>
<CITY>San Antonio 23</CITY>
</item>
</ADDRESS>
<EQUIPMENT>
<item>
<EQUI_NO>1507933</EQUI_NO>
</item>
<item>
<EQUI_NO>1509733</EQUI_NO>
</item>
<item>
<EQUI_NO>90000-EMER</EQUI_NO>
</item>
<item>
<EQUI_NO>90000333-STOCK</EQUI_NO>
</item>
</EQUIPMENT>
<STORAGE_LOC>
<item>
<STOR_LOC_NO>0001</STOR_LOC_NO>
<DESCRIPTION>01 Parts Center</DESCRIPTION>
</item>
<item>
<STOR_LOC_NO>0056</STOR_LOC_NO>
<DESCRIPTION>56 henley</DESCRIPTION>
</item>
</STORAGE_LOC>
</item>
</CUSTOMER_FULL_2014>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ARCHIVO DTD CREADO (automáticamente con xml spy)
<?xml version="1.0" encoding="UTF-8"?>

<!ELEMENT CITY (#PCDATA)>
<!ELEMENT item ((SHIP_TO, NAME1, STREET, HOUSE_NO?, CITY) | (CUST_NO, ADDRESS, EQUIPMENT, STORAGE_LOC) | (STOR_LOC_NO, DESCRIPTION) | EQUI_NO)>
<!ELEMENT NAME1 (#PCDATA)>
<!ELEMENT STREET (#PCDATA)>
<!ELEMENT ADDRESS (item)>
<!ELEMENT CUST_NO (#PCDATA)>
<!ELEMENT EQUI_NO (#PCDATA)>
<!ELEMENT SHIP_TO (#PCDATA)>
<!ELEMENT HOUSE_NO (#PCDATA)>
<!ELEMENT EQUIPMENT (item+)>
<!ELEMENT DESCRIPTION (#PCDATA)>
<!ELEMENT STORAGE_LOC (item+)>
<!ELEMENT STOR_LOC_NO (#PCDATA)>
<!ELEMENT CUSTOMER_FULL_2014 (item+)>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The error of MONITOR Data Services
11676
5184
XML-240108
11-04-2014 17:34:16
|Data flow CARGA_XML_CUSTOMER|Reader READ MESSAGE customer OUTPUT(customer)
11676
5184
XML-240108
11-04-2014 17:34:16
An element named <item> present in the XML data input does not exist in the XML format used to set up this XML source in data
11676
5184
XML-240108
11-04-2014 17:34:16
flow <CARGA_XML_CUSTOMER>. Please validate your XML data.
11676
5184
XML-240307
11-04-2014 17:34:16
|Data flow CARGA_XML_CUSTOMER|Reader READ MESSAGE customer OUTPUT(customer)
11676
5184
XML-240307
11-04-2014 17:34:16
XML parser failed: See previously displayed error message.
The Error from Monitor
The metadata DTD
Thanks
Juan

Hi Juan Juan,
I generated a new XSD file using MS Visual Studio based on your XML file.
The empty spaces in the source is replaced with <Null> in the target table.
Here is the XSD:
<?xml version="1.0" encoding="utf-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:element name="CUSTOMER_FULL_20140207_033015_001">
        <xs:complexType>
            <xs:sequence>
                <xs:choice maxOccurs="unbounded">
                    <xs:element name="CUST_NO" type="xs:unsignedInt" />
                    <xs:element name="ADDRESS">
                        <xs:complexType>
                            <xs:sequence>
                                <xs:element name="SHIP_TO" type="xs:unsignedInt" />
                                <xs:element name="NAME1" type="xs:string" />
                                <xs:element name="STREET" type="xs:string" />
                                <xs:element minOccurs="0" name="HOUSE_NO" type="xs:string" />
                                <xs:element name="CITY" type="xs:string" />
                            </xs:sequence>
                        </xs:complexType>
                    </xs:element>
                    <xs:element name="EQUIPMENT">
                        <xs:complexType>
                            <xs:sequence>
                                <xs:element maxOccurs="unbounded" name="EQUI_NO" type="xs:string" />
                            </xs:sequence>
                        </xs:complexType>
                    </xs:element>
                    <xs:element name="STORAGE_LOC">
                        <xs:complexType>
                            <xs:sequence>
                                <xs:choice maxOccurs="unbounded">
                                    <xs:element name="STOR_LOC_NO" type="xs:unsignedByte" />
                                    <xs:element name="DESCRIPTION" type="xs:string" />
                                </xs:choice>
                            </xs:sequence>
                        </xs:complexType>
                    </xs:element>
                </xs:choice>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
</xs:schema>
For Source XML
<?xml version="1.0" encoding="utf-8"?>
<CUSTOMER_FULL_20140207_033015_001>
<CUST_NO>200530</CUST_NO>
<ADDRESS>
<SHIP_TO>903533</SHIP_TO>
<NAME1>HENLEY - PART MAQUINARIAS S.A.</NAME1>
<STREET>Dean Camilo # 148, San Carlos</STREET>
<CITY>LIMA</CITY>
</ADDRESS>
<EQUIPMENT>
<EQUI_NO>4442</EQUI_NO>
<EQUI_NO>8163</EQUI_NO>
<EQUI_NO>8199</EQUI_NO>
<EQUI_NO>8200</EQUI_NO>
<EQUI_NO>8201</EQUI_NO>
<EQUI_NO>8210</EQUI_NO>
<EQUI_NO>8211</EQUI_NO>
<EQUI_NO>58120</EQUI_NO>
<EQUI_NO>90000-EMERGENCY</EQUI_NO>
<EQUI_NO>90000-STOCK</EQUI_NO>
</EQUIPMENT>
<STORAGE_LOC>
<STOR_LOC_NO>0001</STOR_LOC_NO>
<DESCRIPTION>01 Parts Center</DESCRIPTION>
<STOR_LOC_NO>0056</STOR_LOC_NO>
<DESCRIPTION>56 HEN</DESCRIPTION>
</STORAGE_LOC>
<CUST_NO>200793</CUST_NO>
<ADDRESS>
<SHIP_TO>200793</SHIP_TO>
<NAME1>Minera San Cristobal S.A.</NAME1>
<STREET>Calacoto, Calle 90, Torre 2</STREET>
<HOUSE_NO>Piso 5</HOUSE_NO>
<CITY>La Paz</CITY>
</ADDRESS>
<EQUIPMENT>
<EQUI_NO>90000-EMERGENCY</EQUI_NO>
<EQUI_NO>90000-STOCK</EQUI_NO>
</EQUIPMENT>
<STORAGE_LOC>
<STOR_LOC_NO>0001</STOR_LOC_NO>
<DESCRIPTION>01 Parts Center</DESCRIPTION>
<STOR_LOC_NO>0056</STOR_LOC_NO>
<DESCRIPTION>56 HEN</DESCRIPTION>
</STORAGE_LOC>
<CUST_NO>200801</CUST_NO>
<ADDRESS>
<SHIP_TO>200801</SHIP_TO>
<NAME1>ISEMAR S.A.</NAME1>
<STREET>Ruta Km 28.45</STREET>
<CITY>Don Torcuato Paraguay</CITY>
</ADDRESS>
<EQUIPMENT>
<EQUI_NO>15079</EQUI_NO>
<EQUI_NO>15097</EQUI_NO>
<EQUI_NO>90000-EMERGENCY</EQUI_NO>
<EQUI_NO>90000-STOCK</EQUI_NO>
</EQUIPMENT>
<STORAGE_LOC>
<STOR_LOC_NO>0001</STOR_LOC_NO>
<DESCRIPTION>01 Parts Center</DESCRIPTION>
<STOR_LOC_NO>0056</STOR_LOC_NO>
<DESCRIPTION>56 HEN</DESCRIPTION>
</STORAGE_LOC>
</CUSTOMER_FULL_20140207_033015_001>
Output:
Regards,
Akhileshkiran.

Problem validating XML file with external schema file

Hi All
I am having trouble at the moment trying to validate an xml file using an external xsd file that sits on my server. I have followed the basic option but at the moment to no avail. I am using a DOMParser and am setting all the features and properties correctly ... well I think I am anyway.....below is a fragment of the code
DOMParser parser = new DOMParser ();
// Setting the validation on for the parser.
parser.setFeature ( "http://xml.org/sax/features/validation", true );
parser.setFeature ( "http://apache.org/xml/features/validation/schema", true);
parser.setProperty ( "http://apache.org/xml/properties/schema/externalnoNamespaceSchemaLocation", "c://testing.xsd" );
parser.setErrorHandler ( this );
I am getting an error telling me that the root element cannot be found.....see below
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'mainhome'.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNamespaceBinder.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at com.cibenix.aps.util.MenuXMLParser.process(MenuXMLParser.java:163)
at com.cibenix.aps.actions.MenuAddAction.execute(MenuAddAction.java:80)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
Any help would be greatly appreciated
thanks

In the schema root element xs:schema add namespace declaration.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
In the XML document root element add xmlns:xsi and xsi:noNamespaceSchemaLocation attributes.
<root_element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="file://c:/testing.xsd">

Problem validating an XML document with a schema containing xs:include

Similar Messages

Maybe you are looking for