Error of Validation of XML Schema in BEA WorkSpace Studio

When I validate my XML Schemas throught the BEA WorkSpace Studio Version: 1.1 Build id: 1090602 the follow error happens:
Referenced file contains errors (file:/MyPath/MyXMLSchema1.xsd).
For more information, right click on the message and select "Show Details..."
Show Details:
The errors below were detected when validating the file "MyXMLSchema1.xsd" via the file "MyXMLSchema2.xsd".
In most cases these errors can be detected by validating "MyXMLSchema1.xsd" directly.
However it is possible that errors will only occur when MyXMLSchema1.xsd is validated in the context of MyXMLSchema2.xsd.
src-resolve: Cannot resolve the name 'srv:Services' to a(n) 'type definition' component
When I validate my XML Schemas throught the oepe_11gR1PS4 (Eclipse Platform Version: 3.6.2 Build id: M20110210-1200) no errors were found.
My project is an OSB Project (ALSB Project).
What's happen?

BEA WorkSpace Studio Version: 1.1 Build id: 1090602 use xerces bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org.apache.xerces_2.8.0.v200606131651
oepe_11gR1PS4 (Eclipse Platform Version: 3.6.2 Build id: M20110210-1200) use xerces Oracle\Middleware_10.3.5\oepe_11gR1PS4\plugins\org.apache.xerces_2.9.0.v201005080400.jar
If you replace the follow files:
bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org.apache.xerces_2.8.0.v200606131651\resolver.jar
bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org.apache.xerces_2.8.0.v200606131651\xercesImpl.jar
bea\alsb3.0\tools\eclipse_pkgs\1.1\eclipse_3.2.2\eclipse\plugins\org.apache.xerces_2.8.0.v200606131651\xml-apis.jar
for:
Oracle\Middleware_10.3.5\oepe_11gR1PS4\plugins\org.apache.xerces_2.9.0.v201005080400.jar
BEA WorkSpace Studio Version: 1.1 Build id: 1090602 will validate without errors (the same oepe_11gR1PS4 behaviour)

Similar Messages

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

Problem in developing jasper report in BEA workspace studio version 1.1 with weblogic server 10.0

Hi! all,
Myself developing a jasperReport in BEA workspace studio 1.1 and always getting the below mentioned exception, though i have run the same code in NetBeans successfully with the same jar file.
Even i have added weblogic.jar, wllog4j.jar, classes12.jar, commons-beanutils-1.8.0.jar, commons-collections-2.1.1.jar, commons-digester-1.7.jar, commons-javaflow-20060411.jar, commons-logging-1.0.4.jar, iText-2.1.7.jar, jasperreports-3.7.1.jar, jasperreports.jar, jasper-jdt-6.0.13.jar, jasper-compiler-jdt.jar, jasper-compiler.jar, jasper-runtime.jar, jasperreports-3.5.1.jar, jasperreports-2.0.5.jar in the WEB-INF/lib directory as well as build path. please help me.Thanks in advance.
==============================================================
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/logging/WLLogRecord : weblogic/logging/LogEntry
     at java.lang.ClassLoader.findBootstrapClass(Native Method)
     at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:301)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at weblogic.logging.commons.LogFactoryImpl.getInstance(LogFactoryImpl.java:21)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
     at org.apache.commons.digester.Digester.<init>(Digester.java:304)
     at net.sf.jasperreports.engine.xml.JRXmlDigester.<init>(JRXmlDigester.java:62)
     at net.sf.jasperreports.engine.xml.JRXmlDigesterFactory.createDigester(JRXmlDigesterFactory.java:980)
     at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:203)
     at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
     at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
     at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:150)
     at com.generateJasperReport.test.GasperReportNew.main(GasperReportNew.java:38)
==============================================================================
My Code is..........................
============================
package com.generateJasperReport.test;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.util.HashMap;
import java.util.Map;
//import weblogic.logging.LogEntry;
import net.sf.jasperreports.engine.JRException;
import net.sf.jasperreports.engine.JRResultSetDataSource;
import net.sf.jasperreports.engine.JasperCompileManager;
import net.sf.jasperreports.engine.JasperExportManager;
import net.sf.jasperreports.engine.JasperFillManager;
import net.sf.jasperreports.engine.JasperPrint;
import net.sf.jasperreports.engine.JasperReport;
import net.sf.jasperreports.view.JasperViewer;
public class GenerateJasperReport {
     static JRResultSetDataSource jrds = null;
     static ResultSet rs = null;
     public static Connection connectDB() {
          Connection jdbcConnection = null;
          try {
               Class.forName("oracle.jdbc.driver.OracleDriver");
               jdbcConnection = DriverManager.getConnection(
                         "jdbc:oracle:thin:@192.161.5.35:1521:abc",
                         "xyz", "pqr");
          } catch (Exception ex) {
               String connectMsg = "Could not connect to the database: "
                         + ex.getMessage() + " " + ex.getLocalizedMessage();
               System.out.println(connectMsg);
          return jdbcConnection;
     public static void main(String[] args) throws JRException {
          Connection con = connectDB();
          JasperReport jasperReport=null;
          System.out.println("666666666666666666");
          String reportSource = "E:\\Pintu\\Project\\Bea Project\\workspace\\GenerateJasperReport\\src\\com\\generateJasperReport\\jrxmlFile\\JasperReportGeneration.jrxml";
          String reportDest = "E:\\Pintu\\Project\\Bea Project\\workspace\\GenerateJasperReport\\src\\com\\generateJasperReport\\output\\JasperReportGeneration.pdf";
          System.out.println("555555555555555");
          Map <String,String>parammap = new HashMap<String,String>();
          parammap.put("ReportTitle", "PDF JasperReport");
          System.out.println("444444444444444");
          try {
               try{
                    jasperReport = JasperCompileManager
                         .compileReport(reportSource);
               }catch(JRException e){e.printStackTrace();}
               System.out.println("ssssssssssssss");
               JasperPrint jasperPrint = JasperFillManager.fillReport(
                         jasperReport, parammap, con);
               System.out.println("vvvvvvvvvvvvvvv");
               JasperExportManager.exportReportToPdfFile(jasperPrint, reportDest);
               System.out.println("kkkkkkkkkkkkkkkkkkk");
               JasperViewer.viewReport(jasperPrint);
               System.out.println("gfrfrrrertfewrw");
          } catch (Exception ex) {
               ex.printStackTrace();
===========================================================

Thanks for the information. It makes so much more sense to do the configuration from within PFR instead of WLS but the engineer insisted I could just do everything from within the WLS config wizard. I'm very relieved that someone has had success with this.
Am I supposed to do the configuration wizard in WLS before doing the Configure Classic Interface from PFR?
Since we're only going to be using the PC for the developer, I wasn't sure how much of the Web Logic Server needed to be configured.
The Oracle engineer said to choose 'Oracle Ent. Mgr' and 'Oracle Classic 11g' from the WLS Config Wizard which I did - but now I have a choice on the 'Optional Configuration' page to choose 'Administration Server', 'Managed Servers', 'Deployments and Services' and 'RDMBS Security Store'. I'm not sure if I'm supposed to choose any of these. I want to be able to talk to the Solaris server that is going to be my application server via WLS and I'm not sure if I need any of these.
In your environment, are you developing 11g forms on a PC but hosting on another platform? I have a Windows 7 64 bit machine but was told I had to set up a 32bit XP VM on my Win7 machine to use Forms and Reports for development.

Error in xml file validating to xml schema

Hey,
I am getting the following error while validating xml file to its schema:
The error is:
SAMPLEITEMDLFILE.xml:2,139: no declaration found for element 'WMWROOT'
The XML document SAMPLEITEMDLFILE.xml is NOT valid (1 errors)
schema file:
<?xml version="1.0" encoding="utf-8" ?>
<xs:schema id="ItemDownload" targetNamespace="http://www.manh.com/ILSNET/Interface" elementFormDefault="qualified"
xmlns="http://www.manh.com/ILSNET/Interface" xmlns:xs="http://www.w3.org/2001/XMLSchema" version ="2007">
<xs:include schemaLocation="Item.xsd" />
<xs:element name="WMWROOT" nillable="true" type="WMWROOT" />
<xs:complexType name="WMWROOT">
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="WMWDATA" type="WMWDATA" />
</xs:sequence>
</xs:complexType>
<xs:element name="WMWDATA" nillable="true" type="WMWDATA"/>
<xs:complexType name="WMWDATA">
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="Items" type="ItemList" />
</xs:sequence>
</xs:complexType>
<xs:element name="Items" nillable="false" type="ItemList" />
<xs:complexType name="ItemList">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="unbounded" name="Item" nillable="true" type="Item" />
</xs:sequence>
</xs:complexType>
</xs:schema>
This is the part of PL/SQL code thru which I am generating the xml:
UTL_FILE.put_line (l_out_file, '<?xml version="1.0" ?>');
UTL_FILE.put_line (l_out_file, '<WMWROOT');
UTL_FILE.put_line (l_out_file, 'xmlns="http://www.manh.com/ILSNET/Interface"> ');
UTL_FILE.put_line (l_out_file, '<WMWDATA>');
UTL_FILE.put_line (l_out_file, '<Items>');
I am validating it in stylus studio tool.
Can any1 tell me where I am goin wrong?

Hi,
I am using databse version 10.2.0.03. I am getting the output of xml file like tis:
<?xml version="1.0" ?>
<WMWROOT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.manh.com/ILSNET/Interface ItemDownload.xsd">
WMWDATA>
<Items>
<Item>
<action>Save</action><UserDef8>10074</UserDef8><active>Y</active><availableonweb>N</availableonweb><cost>285.93</cost><desc>HP DESKJET PRINTER (EMBLA)</desc><HarmCode><Identifier>9019.20.0000</Identifier></HarmCode><Item>R145-794</Item><InventoryTracking>Y</InventoryTracking><LongDesc>HP DESKJET PRINTER (EMBLA)</LongDesc><LotControlled>Y</LotControlled><SerialNumTrackInbound>Y</SerialNumTrackInbound><SerialNumTrackInventory>Y</SerialNumTrackInventory><SerialNumTrackOutbound>Y</SerialNumTrackOutbound><StorageTemplate><Template>Each</Template></StorageTemplate><XRefs><XRef></XRef></XRefs>
</Item>
</Items>
</WMWDATA>
</WMWROOT>
My plsql code is like tis:
SELECT /*rule*/
XMLELEMENT (
"Item",
XMLFOREST (action AS "action",
Userdef8 AS "UserDef8",
active AS "active",
availableonweb AS "availableonweb",
cost AS "cost",
description AS "desc"),
XMLELEMENT ("HarmCode",
XMLFOREST (Identifier AS "Identifier")),
XMLFOREST (
Item AS "Item",
inventorytracking AS "InventoryTracking",
Longdesc AS "LongDesc",
lotcontrolled AS "LotControlled",
serialnumtrackinbound AS "SerialNumTrackInbound",
serialnumtrackinventory AS "SerialNumTrackInventory",
serialnumtrackoutbound AS "SerialNumTrackOutbound"),
XMLELEMENT ("StorageTemplate",
XMLFOREST (Template AS "Template")),
XMLELEMENT (
"XRefs",
XMLELEMENT ("XRef", XMLFOREST (XRefItem AS "XRefitem")))).
getclobval ()
----------------------------------------writing to utl file-------------
l_out_file :=
UTL_FILE.fopen (lv_path,
-- lv_out_file,
'testingitemsdl.xml',
'W',
32767);
UTL_FILE.put_line (l_out_file, '<?xml version="1.0" ?>');
UTL_FILE.put_line (l_out_file, '<WMWROOT');
UTL_FILE.put_line (l_out_file, 'xmlns="http://www.manh.com/ILSNET/Interface"> ');
UTL_FILE.put_line (l_out_file, '<WMWDATA>');
UTL_FILE.put_line (l_out_file, '<Items>');
FOR i IN lc_item_info
LOOP
UTL_FILE.put_line (l_out_file, i.item);
END LOOP;
UTL_FILE.put_line (l_out_file, '</Items>');
UTL_FILE.put_line (l_out_file, '</WMWDATA>');
UTL_FILE.put_line (l_out_file, '</WMWROOT>');
UTL_FILE.fclose (l_out_file);

Validating a xml schema (xsd file)

Hi,
I was wondering - my program should accept schema files and before doing whatever it does with them I want to put them through a validation and present errors if any.
I wasn't sure what is the right way to go about this - I know how to set up a validating parser with my own ErrorHandler and retrieve error info for simple xml files and xml schema instances, but how do I set up the parser to validate a schema definition?
My first idea was to validate it like I would validate any schema instance, since xsd files also have their own schema definition, but that seems kind of funny, since obviously the parser already knows what a schema definition should look like.
Has anyone done this?
Thanks,
Uri.

Try something like this??
DocumentBuilderFactory DBF = null;
try
DBF = DocumentBuilderFactory.newInstance();
catch (Exception fce)
// Set various configuration options
DBF.setValidating(true);
DBF.setNamespaceAware(true);
DBF.setIgnoringComments(true);
DBF.setIgnoringElementContentWhitespace(true);
DBF.setCoalescing(true);
DBF.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaSource", new File(Filename));
DBF = DBF.newDocumentBuilder();
DBF.setErrorHandler(this);
DBF.setEntityResolver(this);
catch (Exception pce)
blah blah blah blah....
I hope this is what you were looking/asking for... I could be way off base here 8-))

Validating with XML Schemas

Has anyone been successful at validating xml with a Schema running weblogic 6.1
sp2?
Here is a snippet of code...
SAXParserFactory objFactory = SAXParserFactory.newInstance();
objFactory.setValidating("true");
objFactory.setNamespaceAware("true");
objFactory.setFeature("http://apache.org/xml/features/validation/schema", "true");
objXMLInputParser.parse(new InputSource(new StringReader(XMLDocument)), A_HANDLER);
When my xml code runs through the parser I get an error for each element saying
the element type is not declared in the dtd or schema.
Since weblogic 6.1 runs with 1.3.1 Xerces parser. Does it support xml validation
with a Schema. From what I've read it seems that it does.
Any help or insight would be appreciated.
Thanks
Karen

I figured out my problem in case anyone else is having trouble..
In the xml document that you need to refer to:
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema-instance that is the namespace
supported by xerces 1.3.1.
Whew!
"Karen Schaper" <[email protected]> wrote:
>
Has anyone been successful at validating xml with a Schema running weblogic
6.1
sp2?
Here is a snippet of code...
SAXParserFactory objFactory = SAXParserFactory.newInstance();
objFactory.setValidating("true");
objFactory.setNamespaceAware("true");
objFactory.setFeature("http://apache.org/xml/features/validation/schema",
"true");
objXMLInputParser.parse(new InputSource(new StringReader(XMLDocument)),
A_HANDLER);
When my xml code runs through the parser I get an error for each element
saying
the element type is not declared in the dtd or schema.
Since weblogic 6.1 runs with 1.3.1 Xerces parser. Does it support xml
validation
with a Schema. From what I've read it seems that it does.
Any help or insight would be appreciated.
Thanks
Karen

XML instance validation against XML schema

How can I get a reference on the error node object after
validation against an XML schema ?
Ex. :
DOMParser domP = new DOMParser();
domP.setXMLSchema(schemaDoc); // schemaDoc = ref. on an XMLSchema
domP.setValidationMode(XMLParser.SCHEMA_VALIDATION);
domP.parse(reader); // reader contains the XML instance data
If an error occurred, I only get a message string. What I need is to get a reference on the node object which contains the error in order to retrieve its properties to the schema.
I could then alert the user with a message such as :
"Data xxx is not valid ; it must be comprised between yy and zz...".
Did somebody solve this problem ? May I use the XMLError class to do this ?
Thank you

Hi Ray,
Were you able to resolve this issue? I am encountering a very similar problem where I am not connected to the internet and it fails during the newSchema method on javax.xml.validation.SchemaFactory. I have attempted to implement the suggestions of ExtremeGardener and vidyut with no luck.
Per ExtremeGardener's suggestion of replacing xmlns:xs="http://www.w3.org/2001/XMLSchema" with xmlns:xs="XMLSchema.xsd" and storing it locally, it gave me an error for trying to set the "xs" or "xsd" prefixes to anything other than "http://www.w3.org/2001/XMLSchema." I forget the exact error. I also tried to use my own prefix and it did not like that either.
Per vidyut's suggestion of using a catalog resolver, I believe that I have tried that too (if I understand correctly). I created an LSResourceResolver and tied it to the SchemaFactory. I can invoke it for a namespace but that did not resolve the issue because it only invokes the resolver on an import, include, or redefine. I believe that it is trying to reach the internet due to the xmlns:xs="http://www.w3.org/2001/XMLSchema" attribute within the top-level schema element in the XSD and I know of no way to invoke it for that.
I also created an ErrorHandler and tied it to the SchemaFactory. That shows me the errors and they are all related to the standard XML data types defined in XMLSchema.xsd. The errors that I am seeing are all of this form: "UndeclaredPrefix: Cannot resolve 'xs:string' as a QName: the prefix 'xs' is not declared."
I am currently using the SchemaFactory in Java 1.5, but I am thinking about trying the Xerces SchemaFactory since they are not exactly the same implementation.
Does anyone have any other suggestions? Any help you can provide would be greatly appreciated!
Thanks,
betzro1

WE60 - Error while generating the xml schema

Hi
Using the transaction WE60 I am trying to generate an XML schema for the BASIC type : DEBMDM06, Segment release - 7 and record type version - 3. Following error message is displayed. "Structure of segment E1T023W is unknown". Kindly let me know how to generate an XML schema successfully and what is the reason for this error to come up
Regards
Aruna

Hi Aruna,
It seems a dictionary error but it doesn't occurs to me. I can download the XML schema without problems in SAP ECC 6.0.
If you let me know your email I can send it zipped to you.
Reward points if helps.
Roger

Error publishing plsql webservice (xml schema mapping and/or serializer)

Hi guys,
I'm with a problem when publishing plsql webservices from JDeveloper 11.
The scenario is something like this:
1) I have a connection with a database 9i, and the objects (packages, object types, etc) are all in there.
2) In this case, i can publish the package spec using the option "Publish as JAX-RPC Web Service" normally.
3) A database 11g was created, and i compiled the objects in this environment.
4) Then i've created a new connection with a database 11g.
5) In this case, when i'll publish the webservice, the error occurs: "The following types used by the program unit do not have an XML Schema mapping and/or serializer specified: REC_DMP_REMESSA"
I have no idea in how to solve this case. Someone can help?
Thank in advance.
Best Regards,
Gustavo

Duplicate of https://forums.oracle.com/thread/2610823
Timo

Validation of XML-Schema

I have a question, if in the XDK there is a
possibility to check a .xsd file, if it belongs to the XML Schema Definition http://www.w3.org/2000/10/XMLSchema
Thanks for your help
Greetings, Merry Christmas and Happy new Year
Andreas

Simply use the self-same XML Schema Processor to validate your *.xsd schema against the schema for XML Schema itself. That is, the XML Schema spec "ships" with a normative XML Schema which describes the valid elements that a schema author can use to write a schema. If you have a particular XML schema definition in hand, it is in particular an instance of a document that should be valid by the XML schema for XML Schema, if you've done it correctly.

Validation with XML Schema

With the Xerces parser, you can validate an XML document against an XML schema. But what I wanted to do is something different.
I want to validate data before they are put in XML. Like this:
1) I have a set of class/classes that act as helper class(es) that creates an XML document that conforms to a specific XML Schema. The class(es) would have, of course, setXXXX() methods in it. The XML document is not created until someone call create().
2) With each setXXXXX() method call, I know that the setXXXXX() would eventually map to a specific attribute in a specific element in the XML document that will be created.
3) Therefore, I would want to be able to throw an Exception if a developer call setXXXX() with the correct Java data type, but with an incorrect value based on the XML Schema .... instead of throwing the error when the XML is being serialized / created by the XML parser in the create() method.
Any ideas on how to do this?
Regards,
John

The only way that I could think to do this is to have
a lot of XSDs, one for each element essentially.
In this case you'd have to build your mini-XMLs, parse
each one with an XSD, and then report the error.
Why do you want to do it this way? Is it because you
want to know exactly which one gave an error without
having to parse through the sometimes cryptic error
messages?
PaulYes. that's one.
The other is, if you think of a form that is being filled by a user, you would want the user to be informed of which field in the form has the incorrect value, instead of just showing a generic message .... after which the user may get fed up and do his business elsewhere. Not good for business, isn't it?

Xml validation with xml schema

Hi
I want to do the validation of a xml file against the XML schema.How can i do that.
As per jaxp we can do the validation of an xml file against DTD ,CAN we do the validation against XMLschema in a same way.
Please help its urgent.
regards
prateek

if you're using the Xerces parser, you def. can.
if u look at the SAXCount example, you'll see a certain amount of attributes are set to true/false.
one of these is Schema validation. set it to true, run the SAXCount.java example, and your XML is validated against it's XML Schema,

Validating against XML Schema

Hi,
does someone know how to validate a XML file against
a XSD File (XML Schema) in ABAP. Iam using the IXML Package.
Thanks.
Jim

I've originally been using Xerces1_4_0, but you're right - it's xerces-2_0_0_beta4 that does the job.
Thanks for the hint!
Luca

XML: VALIDATING WITH XML SCHEMA: SAXNotRecognizedException

Hi,
1. From The Java� Web Services Tutorial for SAX
If the parser is not 1.2 compliant, and therefore does not support XML Schema,it could throw a SAXNotRecognizedException .
SAXParser saxParser =factory.newSAXParser();
try {
saxParser.setProperty(JAXP_SCHEMA_LANGUAGE,W3C_XML_SCHEMA);
catch (SAXNotRecognizedException x){
//Happens if the parser does not support JAXP 1.2
2. How do we know if the parser is not 1.2 compliant or not? 1M Thanks.

If you have an older xerces.jar in your class path your parser will not be JAXP 1.2 compliant.
Try replacing xerces.jar with both xercesImpl.jar and xml-apis.jar.

Create a XML Schema (C#) using Visual Studio Express 2012

How do I add an XML schema to my xml file?
Here is my code:
private void WriteXmlToFile(DataSet dsDataSet)
if (dsDataSet == null) { return; }
// Create a file name to write to - creates a string
string xmlfilename = @"C:\Users\fenwky\XmlDoc.xml";
// Create the FileStream to write with.
System.IO.FileStream stream = new System.IO.FileStream
(xmlfilename, System.IO.FileMode.Create);
// Create an XmlTextWriter with the fileStream.
System.Xml.XmlTextWriter xmlWriter =
new System.Xml.XmlTextWriter(stream,
System.Text.Encoding.Unicode);
// Write dsDataSet to the file with the WriteXml method.
dsDataSet.WriteXml(xmlWriter);
xmlWriter.Close();
And here is my xml:
<NewDataSet>
<Table1>
<Item_Code>A0001</Item_Code>
<Item_Description>Wheels, Horse on</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0002</Item_Code>
<Item_Description>Wheels, Elephant on</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0003</Item_Code>
<Item_Description>Wheels, Dog on</Item_Description>
<Current_Count>0</Current_Count>
<On_Order>Yes</On_Order>
</Table1>

Open the XML with NOTEPAD to see if you are getting the correct results. Something may be wrong with you CSV file. Get original CSV that teacher gave out. Here is my results and C# code. The styling is the 2nd line and simply
requires changing the one line in the C# that outputs the line.
<?xml version="1.0" encoding="UTF-8"?>
<?xsl:stylesheet type='text/xsl' href='book.xsl'?>
<NewDataSet>
<xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:UseCurrentLocale="true">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="Table1">
<xs:complexType>
<xs:sequence>
<xs:element name="Item_Code" type="xs:string" minOccurs="0" />
<xs:element name="Item_Description" type="xs:string" minOccurs="0" />
<xs:element name="Current_Count" type="xs:int" minOccurs="0" />
<xs:element name="On_Order" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
<Table1>
<Item_Code>A0001</Item_Code>
<Item_Description>Horse on Wheels</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0002</Item_Code>
<Item_Description>Elephant on Wheels</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0003</Item_Code>
<Item_Description>Dog on Wheels</Item_Description>
<Current_Count>0</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0004</Item_Code>
<Item_Description>Seal on Wheels</Item_Description>
<Current_Count>3</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0005</Item_Code>
<Item_Description>Bear on Wheels</Item_Description>
<Current_Count>7</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0006</Item_Code>
<Item_Description>Teddy Bear</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0007</Item_Code>
<Item_Description>Clown</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0008</Item_Code>
<Item_Description>Puppy(crouch)</Item_Description>
<Current_Count>3</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0009</Item_Code>
<Item_Description>Puppy(stand)</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0010</Item_Code>
<Item_Description>Puppy(jump)</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0011</Item_Code>
<Item_Description>Pupp(lying)</Item_Description>
<Current_Count>1</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0012</Item_Code>
<Item_Description>Cart with Blocks (50)</Item_Description>
<Current_Count>0</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0013</Item_Code>
<Item_Description>Cart with Blocks (100)</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0014</Item_Code>
<Item_Description>Cart with Blocks (200)</Item_Description>
<Current_Count>4</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0015</Item_Code>
<Item_Description>Train with 0 Carriage</Item_Description>
<Current_Count>12</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0016</Item_Code>
<Item_Description>Train with 1 Carriage</Item_Description>
<Current_Count>10</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0017</Item_Code>
<Item_Description>Train with 2 Carriage</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0018</Item_Code>
<Item_Description>Train with 3 Carriage</Item_Description>
<Current_Count>4</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0019</Item_Code>
<Item_Description>Train with 4 Carriage</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0020</Item_Code>
<Item_Description>Train with 5 Carriage</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0021</Item_Code>
<Item_Description>Building Blocks (20)</Item_Description>
<Current_Count>15</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0022</Item_Code>
<Item_Description>Building Blocks (30)</Item_Description>
<Current_Count>13</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0023</Item_Code>
<Item_Description>Building Blocks (40)</Item_Description>
<Current_Count>16</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0024</Item_Code>
<Item_Description>Building Blocks (50)</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0025</Item_Code>
<Item_Description>Building Blocks (100)</Item_Description>
<Current_Count>2</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0026</Item_Code>
<Item_Description>Building Blocks (200)</Item_Description>
<Current_Count>8</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0027</Item_Code>
<Item_Description>Windmill</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0028</Item_Code>
<Item_Description>Farmhouse</Item_Description>
<Current_Count>6</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0029</Item_Code>
<Item_Description>Fencing</Item_Description>
<Current_Count>22</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0030</Item_Code>
<Item_Description>Barn</Item_Description>
<Current_Count>12</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0031</Item_Code>
<Item_Description>Tractor</Item_Description>
<Current_Count>6</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0032</Item_Code>
<Item_Description>Animals</Item_Description>
<Current_Count>3</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0033</Item_Code>
<Item_Description>House</Item_Description>
<Current_Count>9</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0034</Item_Code>
<Item_Description>Car</Item_Description>
<Current_Count>12</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0035</Item_Code>
<Item_Description>Building (small)</Item_Description>
<Current_Count>4</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0036</Item_Code>
<Item_Description>Building (medium)</Item_Description>
<Current_Count>3</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0037</Item_Code>
<Item_Description>Building (tall)</Item_Description>
<Current_Count>4</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0038</Item_Code>
<Item_Description>Shop</Item_Description>
<Current_Count>7</Current_Count>
<On_Order>No</On_Order>
</Table1>
<Table1>
<Item_Code>A0039</Item_Code>
<Item_Description>Traffic Lights</Item_Description>
<Current_Count>5</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
<Table1>
<Item_Code>A0040</Item_Code>
<Item_Description>Petrol Station</Item_Description>
<Current_Count>4</Current_Count>
<On_Order>Yes</On_Order>
</Table1>
</NewDataSet>
C#
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.IO;
using System.Data.OleDb;
using System.Xml;
using System.Xml.Xsl;
namespace CSVImporter
public partial class CSVImporter : Form
//const string xmlfilename = @"C:\Users\fenwky\XmlDoc.xml";
const string xmlfilename = @"C:\temp\test.xml";
DataSet ds = null;
public CSVImporter()
InitializeComponent();
WriteXML();
public void WriteXML()
// Create a Open File Dialog Object.
openFileDialog1.Filter = "csv files (*.csv)|*.csv|All files (*.*)|*.*";
openFileDialog1.ShowDialog();
string fileName = openFileDialog1.FileName;
//doc.InsertBefore(xDeclare, root);
// Create a CSV Reader object.
CSVReader reader = new CSVReader();
ds = reader.ReadCSVFile(fileName, true);
dataGridView1.DataSource = ds.Tables["Table1"];
StringWriter stringWriter = new StringWriter();
ds.WriteXml(new XmlTextWriter(stringWriter), XmlWriteMode.WriteSchema);
string xmlStr = stringWriter.ToString();
XmlDocument doc = new XmlDocument();
doc.LoadXml(xmlStr);
XmlDeclaration xDeclare = doc.CreateXmlDeclaration("1.0", "UTF-8", null);
XmlNode docNode = doc.CreateXmlDeclaration("1.0", "UTF-8", null);
doc.InsertBefore(xDeclare, doc.FirstChild);
// Create a procesing instruction.
XmlProcessingInstruction newPI;
String PItext = "type='text/xsl' href='book.xsl'";
newPI = doc.CreateProcessingInstruction("xsl:stylesheet", PItext);
doc.InsertAfter(newPI, doc.FirstChild);
doc.Save(xmlfilename);
XslCompiledTransform myXslTrans = new XslCompiledTransform();
myXslTrans.Load(xmlfilename);
string directoryPath = Path.GetDirectoryName(xmlfilename);
myXslTrans.Transform(xmlfilename, directoryPath + "result.html");
webBrowser1.Navigate(directoryPath + "result.html");
public class CSVReader
public DataSet ReadCSVFile(string fullPath, bool headerRow)
string path = fullPath.Substring(0, fullPath.LastIndexOf("\\") + 1);
string filename = fullPath.Substring(fullPath.LastIndexOf("\\") + 1);
DataSet ds = new DataSet();
try
if (File.Exists(fullPath))
string ConStr = string.Format("Provider=Microsoft.Jet.OLEDB.4.0;Data Source={0}" + ";Extended Properties=\"Text;HDR={1};FMT=Delimited\\\"", path, headerRow ? "Yes" : "No");
string SQL = string.Format("SELECT * FROM {0}", filename);
OleDbDataAdapter adapter = new OleDbDataAdapter(SQL, ConStr);
adapter.Fill(ds, "TextFile");
ds.Tables[0].TableName = "Table1";
foreach (DataColumn col in ds.Tables["Table1"].Columns)
col.ColumnName = col.ColumnName.Replace(" ", "_");
catch (Exception ex)
MessageBox.Show(ex.Message);
return ds;
jdweng

Error of Validation of XML Schema in BEA WorkSpace Studio

Similar Messages

Maybe you are looking for