B2B is not validating payloads against uploaded schemas

Hi Ramesh,
We setup our B2B to validate the payloads
but its really not happening.
We sent some invalid payloads, B2B sent them to TP successfully.
I set Is validation to True in Business action setup
Thanks
Praveen

Hi Sumit,
We are also planning to send Custom XML Document over HTTP. Could you please let us know the detailed steps on how we can configure the same in B2B.
I tried using Custom XML Document Over AS2 but the particluar schema is not coming up in B2B WSIL Browser in JDeveloper.
Appreciate your help and co-operation.
Thanks In Advance,
Dibya

Similar Messages

Does XDB supports validating xml against multiple schemas?

The XMLType has some methods for validating an xml documents against a schema, e.g., SCHEMAVALIDATE, etc.. does XDB support validating xml against multiple schemas (Just like what JAXP or Xerces have done)? Or what's the current situation about this issue? thanks.

did you try using the import schema element instead of the include elemnt?

Issue in Store XML into Schema generated tables and Validation XML against registered schema.

Hello friends,
I am facing some problem when store xml into generated tables from registered schema.
This is my Schema
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.abc.inf.in/test" targetNamespace="http://www.abc.inf.in/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="abc.xsd"/>
<xs:element name="project" type="student">
<xs:annotation>
<xs:documentation> This is a Documentation</xs:documentation>
</xs:annotation>
</xs:element>
</xs:schema>
-- This is my xml document
<project versao="2.00" xmlns="http://www.abc.inf.in/test">
<test xmlns="http://www.abc.inf.in/test">
<intest version="2.00" Id="testabc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
<ide>
<cUF>35</cUF>
<cNF>59386422</cNF>
<natOp>this is post</natOp>
<indPag>1</indPag>
<mod>55</mod>
<serie>1</serie>
</ide>............
Not giving full because it's too long.
1. I Successfully registered Schema into database
2. Then i generate table from registered Schema
2. In my java code i validated XML document against Schema and it's successfully validate.
3. But when i stored this XML into this generated table it's give me error
Like :
INSERT INTO XMLTABLE
VALUES
(XMLTYPE(bfilename('MYDIR','testabc.xml'),NLS_CHARSET_ID('AL32UTF8')))
Error report:
SQL Error: ORA-31061: XDB error: XML event error
ORA-19202: Error occurred in XML processing
LSX-00333: literal "94032000" is not valid with respect to the pattern
And i have to store this xml into this tables so what i have to do ?

Thanks for your reply odie_63.
I got this my error solution. My XML document is not well structured based on my registered XML Schema.
Means In My XML Document there are some invalid value and that not match my schema pattern so it's gives this error
SQL Error: ORA-31061: XDB error: XML event error
ORA-19202: Error occurred in XML processing
LSX-00333: literal "94032000" is not valid with respect to the pattern
For Solution we have two ways
1. I have changed this literal "94032000" value in my xml file then save it.
2.
- We have to delete this schema then
- we have to change Schema pattern for particular element
like :--
<xs:restriction base="xs:string">
<xs:whiteSpace value="preserve"/>
<xs:pattern value="[0-9]{3}"/>
</xs:restriction>
- then store xml into database it works..
Thanks.

Error while Validating xml against a schema using jaxp

Hi All,
Following code validates xml against a schema using JAXP .It gives SAXNotRecognizedException error when you run the program.
static final String JAXP_SCHEMA_LANGUAGE = "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
static final String W3C_XML_SCHEMA = "http://www.w3.org/2001/XMLSchema";
SAXParserFactory myFactory = SAXParserFactory.newInstance();
myFactory.setNamespaceAware(true);
myFactory.setValidating(true);
javax.xml.parsers.SAXParser parser;
String filename = "C:/Note.xml";
File xmlFile = new File(filename);
try
     DefaultHandler handler = new DefaultHandler();
     parser = myFactory.newSAXParser();
     parser.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
     parser.parse(xmlFile, handler);
catch (ParserConfigurationException e)
     // TODO Auto-generated catch block
     e.printStackTrace();
catch (SAXException e)
     // TODO Auto-generated catch block
     e.printStackTrace();
catch (IOException e)
     // TODO Auto-generated catch block
     e.printStackTrace();
Error Details :
org.xml.sax.SAXNotRecognizedException: http://java.sun.com/xml/jaxp/properties/schemaLanguage
     at org.apache.xerces.framework.XMLParser.setProperty(XMLParser.java:1682)
     at org.apache.xerces.parsers.SAXParser.setProperty(SAXParser.java:770)
     at org.apache.xerces.jaxp.SAXParserImpl.setProperty(SAXParserImpl.java:183)
How do i fix the above mentioned problem ?
Thanks in Advance.
Ansh

Validate with the JAXP DOMParser instead of the JAXP SAXParser.
To validate with a SAXParser use the xerces SAXParser.
thanks,
Deepak

JDOMException thrown validating XML against a schema with Xerces2

I'm trying to validate a document with JDOM and Xerces 2.
I can validate it with XMLSpy (it works, my document is valid).
But with JDOM and xerces, this error occurs when parsing and validating my document:
org.jdom.JDOMException: Error on line 6 of document file:///E:/developpement/SitePerso/xml/xml/listeEntreprises.xml: cvc-complex-type.2.4.a: Invalid content starting with element 'item'. The content must match '(("":nom){0-1},("":item){0-UNBOUNDED})'.
My XML document:
<?xml version="1.0" encoding="UTF-8"?>


<liste xmlns="E:/developpement/SitePerso/xml/domain~1/schemaListe" ... E:\developpement\SitePerso\xml\schemas\schemaListe.xsd">
<item xsi:type="xsel:typeEntreprise">
<xsel:nom>PHOENIX I.S.I.</xsel:nom>
<xsel:groupe>Taffioles</xsel:groupe>
<xsel:adresse>2 rue du centre</xsel:adresse>
The element <nom> before <item> is not required. So what's the problem ?

...

Re: Validation Against A Schema With DOM

I tried to redeploy a properly working application using Schema not DTD. It worked perfectly before but after redeployment, I got this an error complaining of missing "AbstractDOMParser". I downloaded this jar "xercesImpl.jar" which contain "AbstractDOMParser" . The error is gone away. However, a new error popped up as following. Remember, I don't encounter any problem like this before redeployment.
Recoverable Error: Document is invalid: no grammar found. ( Check line number:2, column:7)
Recoverable Error: Document root element "rules", must match DOCTYPE root "null". ( Check line number:2, column:7)
My guess is that I downloaded the wrong Parser. I need a parser for Schema not DTD. Where can I download the parser for Schema (not DTD parser)? any other potential factors, which you all can think of ,caused this error? Any input I really appreciate.
Here is my XML:
<?xml version="1.0" encoding="UTF-8"?>
<rules xsi:noNamespaceSchemaLocation="/SUNWappserver7/domains/domain1/applications/j2ee-modules/olbr_1/WEB-INF/classes/schemas/ezgov_bre.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<rules-package name="Navigation">
<rule-script name="GetNextNavigationId">
# initialize values
navId = ""
if (NavigationControllerDataSetName_navigationControllerCurrentNavigationId != N
one):
navId = NavigationControllerDataSetName_navigationControllerCurrentNavigatio
nId.lower()
newNavId = ""
if (NavigationControllerDataSetName_navigationControllerNavigationId != None):
newNavId = NavigationControllerDataSetName_navigationControllerNavigationId.
lower()
action = ""
Thanks in advance,
Van

Set the parser as a schema validating parser.
parser.setFeature("http://xml.org/sax/features/validation",
                  true);Set the validation/schema feature to true to report validation errors against a schema.
parser.setFeature("http://apache.org/xml/features/validation/schema",
                  true);Set the validation/schema-full-checking feature to true to enable full schema, grammar-constraint checking.
parser.setFeature("http://apache.org/xml/features/validation/schema-full-checking",
                  true);

Error in validating XML against schema

Hi am getting some critical errors while Validating XML against schema
error is:
cvc-elt.1: Cannot find the declaration of element 'position' , here <position> is my root element.
my code is as follows:
package com.glemser.xmLabeling.library.component.spl;
import com.documentum.com.DfClientX;
import com.documentum.com.IDfClientX;
import com.documentum.fc.client.IDfClient;
import com.documentum.fc.client.IDfSession;
import com.documentum.fc.client.IDfSessionManager;
import com.glemser.common.helper.OperationHelper;
import org.xml.sax.*;
import org.xml.sax.helpers.DefaultHandler;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.parsers.SAXParserFactory;
import java.io.CharArrayWriter;
import java.io.IOException;
import java.io.InputStream;
public class Test {
static IDfSession m_session;
public static void main(String[] args) {
try {
new Test().validate();
} catch (Exception e) {
e.printStackTrace();
private XMLReader xmlReader;
private DefaultHandler handler; // Defines the handler for this parser
private boolean valid = true;
public void validate() {
try {
SetXML setXML = new SetXML();
OperationHelper operation = new OperationHelper();
String splObjPath = "C://Documents and Settings/dparikh/My Documents/xmLabelingStage/Test.xml";//operation.executeExportOperation(m_session, new DfId(m_objectId), true);
SAXParserFactory spf = SAXParserFactory.newInstance();
spf.setNamespaceAware(false);
spf.setValidating(true);
spf.setFeature("http://xml.org/sax/features/validation", true);
spf.setFeature("http://apache.org/xml/features/validation/schema", true);
spf.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true);
if (spf.isValidating()) {
System.out.println("The parser is validating");
javax.xml.parsers.SAXParser sp = spf.newSAXParser();
sp.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema");
sp.setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation", "file://C:/Documents and Settings/dparikh/My Documents/xmLabelingStage/Test.xsd");
System.out.println("The parser is validating1");
//Create XMLReader
xmlReader = sp.getXMLReader();
xmlReader.setFeature("http://apache.org/xml/features/validation/schema", true);
xmlReader.setEntityResolver(new SchemaLoader());
ContentHandler cHandler = new MyDefaultHandler();
ErrorHandler eHandler = new MyDefaultHandler();
xmlReader.setContentHandler(cHandler);
xmlReader.setErrorHandler(eHandler);
System.out.println("The parser is validating2");
parseDocument(splObjPath);
} catch (SAXException se) {
se.printStackTrace();
} catch (ParserConfigurationException e) {
e.printStackTrace(); //To change body of catch statement use File | Settings | File Templates.
public void parseDocument(String xmlFile) {
try {
xmlReader.parse(xmlFile);
if (valid) {
System.out.println("Document is valid!");
} catch (SAXException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
class MyDefaultHandler extends DefaultHandler {
private CharArrayWriter buff = new CharArrayWriter();
private String errMessage = "";
/* With a handler class, just override the methods you need to use
// Start Error Handler code here
public void warning(SAXParseException e) {
System.out.println("Warning Line " + e.getLineNumber() + ": " + e.getMessage() + "\n");
public void error(SAXParseException e) {
errMessage = new String("Error Line " + e.getLineNumber() + ": " + e.getMessage() + "\n");
System.out.println(errMessage);
valid = false;
public void fatalError(SAXParseException e) {
errMessage = new String("Error Line " + e.getLineNumber() + ": " + e.getMessage() + "\n");
System.out.println(errMessage);
valid = false;
public class SchemaLoader implements EntityResolver {
public static final String FILE_SCHEME = "file://";
public InputSource resolveEntity(String publicId, String systemId) throws SAXException {
if (systemId.startsWith(FILE_SCHEME)) {
String filename = systemId.substring(FILE_SCHEME.length());
InputStream stream = SchemaLoader.class.getClassLoader().getResourceAsStream(filename);
return new InputSource(stream);
} else {
return null;
My XML and XSD are as below:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="position" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="position_number" type="xsd:string"/>
<xsd:element name="position_title" type="xsd:string"/>
<xsd:element name="report_to_position" type="xsd:string"/>
<xsd:element name="incumbent" type="xsd:string"/>
<xsd:element name="operation" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<position xsi:schemaLocation="Test.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<position_number>12345</position_number>
<position_title>Sr. Engr</position_title>
<report_to_position>23456</report_to_position>
<incumbent>23456</incumbent>
<operation>INSERT</operation>
</position
Please help me out

--> Could not find cached enumeration value Custom.CI.Enum.PeripheralDevice.Printer for property Type, class BMC.Custom.CI.PeripheralDevice in enumeration cache.
You must specify either the Name or Guid of an enumeration of type Custom.CI.Enum.PeripheralDevice.Type.
Be sure that you are specifying the Name property of the enumeration value you want to set, and not the DisplayName; the Internal Name is something like "IncidentCategoryEnum.Category" for out of the box enumerations, or ENUM.210ADA2282FDABC3210ADA2282FDABC
for enumerations created in the console.
you can check this by finding the enumeration in the XML or by using the the
SMLets commandlet
Get-SCSMEnumeration | ?{$_.DisplayName –eq “Printer”}
and then checking your value with
Get-SCSMEnumeration -Name "ENUM.210ADA2282FDABC3210ADA2282FDABC"
and see if you get the right displayname back

Validating XML against an XML Schema using PL/SQL

Hello everyone,
I've a strange problem.
I'm trying to validate an XMLTYPE variable against an XSD schema using the XMLisValid function.
The XML I was trying to validate was returning false (0) when using this method.
However, when I register the XSD against a column in a table and then insert this XMLTYPE into that column, I do not get any errors. If I change the XSD to ensure failure when using this method, I do get an error, so it is registered and working.
I have then created a very basic XSD and both methods work when validating the XML against this. So obviously the more complicated XSD I want to validate against is making a difference, but I would expect them to either both fail or both pass, not one fail and one pass.
Does anyone know why they'd be returning different results?
Thanks in advance for your help.
Robin
examples of what I'm using:
XML to validate:
<centres>
<add>
<centre>
<centreName>Name 1</centreName>
<centreRef>45678</centreRef>
</centre>
</add>
</centres>
Simple 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="centres" type="centresType"/>
<xs:complexType name="addType">
<xs:sequence>
<xs:element type="xs:string" name="centreName"/>
<xs:element type="xs:short" name="centreRef"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="centresType">
<xs:sequence>
<xs:element type="addType" name="add" maxOccurs="3" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Complicated 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="centres">
<xs:complexType>
<xs:sequence>
<xs:element name="remove">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="centreRef">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="add">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="centre">
<xs:complexType>
<xs:sequence>
<xs:element name="centreName">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="centreRef">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element minOccurs="0" maxOccurs="1" name="qualifications">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="qualRef">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="modifyQualAssociations">
<xs:complexType>
<xs:sequence>
<xs:element name="remove">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="r">
<xs:complexType>
<xs:attribute name="centreRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="qualRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="add">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1000" name="a">
<xs:complexType>
<xs:attribute name="centreRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="50" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="qualRef" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1" />
<xs:maxLength value="100" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

Steps to validate XML data against a schema in Oracle:
1. Register your XSD in the database.
begin
dbms_xmlschema.registerschema(
SchemaUrl,
SchemaDoc,
local => TRUE/FALSE);
end;
2. For validating your XML document against your registered schema, here is a sample pl/sql block.
declare
v_xml xmltype;
begin
v_xml := your_xml_document;
v_xml.schemaValidate();
end;
Hope this helps :)

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

Can not validate XML against schema

Hi all,
I'm new to XML validation. I have this sample from net.
this is the schema definition:
<xs:schema targetNamespace="http://www.w3schools.com" elementFormDefault="qualified">
<xs:element name="note" type="xs:string"/>
</xs:schema>
and this is the xml file:
<?xml version="1.0"?>
<note xmlns="http://www.w3schools.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3schools.com note.xsd">
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note>
when i try to validate at http://schneegans.de/sv/, this is a validator i found searching
it gives error
The root element does not comply with the schema. (2:2)
any ideas?
i have created my own xml and schema.I registered the xsd on oracle 10g but i get the same error :(
where can i validate my xml against a schema?
thanx a lot

Validating XML Documents Against XML Schema
http://www.oracle.com/technology/pub/articles/vohra_xmlschema.html

Question about validating xml against schema

Hi,
I am new to JAXP. I try to validating a xml against a schema. I wrote following code:
SAXParserFactory spf = SAXParserFactory.newInstance();
spf.setNamespace(true);
spf.setValidating(true);
SAXParser sp = spf.newSAXParser();
sp.setProperty("http://java.sun.com/xml/properties/jaxp/schemaLanguage",
"http://www.w3.org/2001/XMLSchema");
sp.setProperty("http://java.sun.com/xml/properties/jaxp/schemaSource",
"mySchema.xsd") ;
sp.parse(<XML Document>, <ContentHandler);
but when compile, it has error: can't resolve ""http://java.sun.com/xml/properties/jaxp/schemaLanguage", and
"http://java.sun.com/xml/properties/jaxp/schemaSource".
It seems it didn't support above two property.
I saw some code in forum is:
fact.setFeature("http://xml.org/sax/features/validation", true);
fact.setFeature("http://apache.org/xml/features/validation/schema",true);
fact.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true);
SAXParser sp = fact.newSAXParser();
sp.setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation",schemas);
Why sun tutorial use property:http://java.sun.com/xml/properties/jaxp/schemaLanguage
and someone use:http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation
where to get information about setting properties for SAXParserFactory?
Thanks

In the past, ColdFusion's XML validation mechanism seems to have had issues with schemas that contain imports, e.g., http://forums.adobe.com/message/155906. Have these issues still not been resolved?
Do you not think that perhaps you're answering your own question here?
I don't see an issue about this on the bug tracker. It might be an idea if you can get a simple, stand-alone repro case together and raise an issue (and post the reference back here and against that other thread so people know to vote for it). If you post the repro case here too, it would be helpful.
Adam

ORA-19201: Datatype not supported when validating XML against an XSD

Hello.
Info: using Oracle 10.2.0.1.0, Java components are installed.
I've created an XML view using ora:view, which is validated against a registered XSD. This view is created successfully.
But when I SELECT * from this view, it gives ORA-19201 - Datatype not supported.
Can't understand why. I've matched the XML to the XSD, and the datatypes all look fine to me. I've referred to the XSD using the XMLFORMAT.CREATEFORMAT option. When I use the same option to specify "NO_SCHEMA", it returns the correct XML, but we need to validate it against the XSD.
I'm thinking one of two things has happened here:
1. I've made a mistake with either my registration, or how I've used XMLFORMAT to refer to the XSD.
2. There's a bug in Oracle.
My money's on 1. Can anyone help?
Thanks,
Ray.

Hello Geoff, I didn't want to send any code until I knew someone was willing to look at it (there's a lot of it).
Here is the XSD:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
     <xs:element name="TransInfo">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="PIE_ERROR" type="PIE_ERRORType" minOccurs="0"/>
                    <xs:element name="Transaction" type="TransactionType" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="PIE_ERRORType">
          <xs:sequence>
               <xs:element ref="ERROR_CODE"/>
               <xs:element ref="DESCRIPTION"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="ERROR_CODE">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="0001"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="DESCRIPTION">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="LEAD NUMBER 12345 IS INVALID"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="TransactionType">
          <xs:sequence>
               <xs:element ref="TRANSACTION_NUMBER"/>
               <xs:element ref="TRANSACTION_STATUS"/>
<xs:element ref="CONTACT_ID"/>
               <xs:element ref="INVOICE_NUMBER"/>
               <xs:element ref="CHANNEL"/>
               <xs:element ref="CSA"/>
               <xs:element ref="OPEN_DATETIME"/>
               <xs:element ref="CLOSED_DATETIME"/>
               <xs:element name="Orderline" type="OrderlineType" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="TRANSACTION_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="3455229"/>
                    <xs:enumeration value="3455230"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="TRANSACTION_STATUS">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="C"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CONTACT_ID">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="111"/>
                    <xs:enumeration value="222"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="INVOICE_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="123456789"/>
                    <xs:enumeration value="987654321"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CHANNEL">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Test 1"/>
                    <xs:enumeration value="Test 2"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CSA">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="SEARLEA"/>
                    <xs:enumeration value="SILVAJ"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="OPEN_DATETIME">
          <xs:simpleType>
               <xs:restriction base="xs:dateTime">
                    <xs:enumeration value="2001-10-26T20:32:52"/>
                    <xs:enumeration value="2004-12-06T10:23:25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="CLOSED_DATETIME">
          <xs:simpleType>
               <xs:restriction base="xs:dateTime">
                    <xs:enumeration value="2001-10-26T21:32:52"/>
                    <xs:enumeration value="2004-12-06T10:23:25"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="OrderlineType">
          <xs:sequence>
               <xs:element ref="ORDER_QTY"/>
               <xs:element ref="RETAIL_AMT"/>
               <xs:element ref="SALE_AMT"/>
               <xs:element ref="PRODUCT_DESCR"/>
               <xs:element ref="PART"/>
               <xs:element ref="IMEI"/>
               <xs:element name="BankDetails" type="BankDetailsType"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="ORDER_QTY">
          <xs:simpleType>
               <xs:restriction base="xs:int">
                    <xs:enumeration value="1"/>
                    <xs:enumeration value="3"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="RETAIL_AMT">
          <xs:simpleType>
               <xs:restriction base="xs:decimal">
                    <xs:enumeration value="45.67"/>
                    <xs:enumeration value="54.76"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="SALE_AMT">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="45.67"/>
                    <xs:enumeration value="54.76"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PRODUCT_DESCR">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="Product test 2"/>
                    <xs:enumeration value="Vodafone Nokia 6230 Pack"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="PART">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="6806"/>
                    <xs:enumeration value="8606"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="IMEI">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="099000000000001"/>
                    <xs:enumeration value="09900078900001"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:complexType name="BankDetailsType">
          <xs:sequence>
               <xs:element ref="BANK_NAME"/>
               <xs:element ref="ACCOUNT_NAME"/>
               <xs:element ref="ACCOUNT_NUMBER"/>
               <xs:element ref="SORT_CODE"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="BANK_NAME">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="HSBC"/>
                    <xs:enumeration value="LLOYDS"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="ACCOUNT_NAME">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="MR A SEARLE"/>
                    <xs:enumeration value="MR J SILVA"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="ACCOUNT_NUMBER">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="87698789"/>
                    <xs:enumeration value="89769082"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="SORT_CODE">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="100928"/>
                    <xs:enumeration value="123346"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
</xs:schema>
I then registered this XSD using DBMS_XMLSCHEMA.REGISTER, calling it test_1.xsd. It is visble in USER_XML_SCHEMAS.
Here are the 15 views used to drive the XML:
SQL> desc v_pie_branch
Name Null? Type
BRANCH NOT NULL NUMBER(4)
SQL> desc v_pie_branch_feature
Name Null? Type
BRANCH_FEATURE NOT NULL NUMBER(10)
BRANCH NUMBER(4)
FEATURE_TYPE VARCHAR2(10)
CHANNEL VARCHAR2(40)
SQL> desc v_pie_transaction
Name Null? Type
TRANSACTION_NUMBER NOT NULL NUMBER(10)
BRANCH NUMBER(4)
EMPLOYEE_TRANS VARCHAR2(12)
CONTACT NUMBER(8)
OPEN_DAT DATE
OPEN_TIM DATE
TRANSACTION_STATUS VARCHAR2(1)
TRANS_TYPE VARCHAR2(1)
CLOSED_DAT DATE
CLOSED_TIM DATE
INVOICE_NUMBER NUMBER(10)
INVOICE_DAT DATE
CSA VARCHAR2(12)
CREATED_ON DATE
AMENDED_BY VARCHAR2(12)
AMENDED_ON DATE
OPEN_DATETIME VARCHAR2(19)
CLOSED_DATETIME VARCHAR2(19)
SQL> desc v_pie_bank_detail
Name Null? Type
BANK_DETAIL NOT NULL NUMBER(12)
BANKCODE VARCHAR2(40)
SORTCODE VARCHAR2(40)
BANK_NAME VARCHAR2(60)
SQL> desc v_pie_account_detail
Name Null? Type
ACCOUNT_DETAIL NOT NULL NUMBER(12)
BANK_DETAIL NUMBER(12)
ACCOUNT_NUMBER VARCHAR2(40)
SORT_CODE VARCHAR2(40)
ACCOUNT_NAME VARCHAR2(40)
BANKCODE VARCHAR2(40)
SQL> desc v_pie_account_link
Name Null? Type
ACCOUNT_LINK NOT NULL NUMBER(12)
CONTACT NUMBER(12)
ACCOUNT_DETAIL NUMBER(12)
ACC_LINK_TYP NUMBER(12)
BNK_SINCE DATE
AC_DET VARCHAR2(40)
SQL> desc v_pie_compesn
Name Null? Type
COMPESN NOT NULL NUMBER(10)
CONTACT NUMBER(8)
IMEI VARCHAR2(25)
SQL> desc v_pie_contact
Name Null? Type
CONTACT_ID NOT NULL NUMBER(8)
CONTACT_TYP VARCHAR2(1)
COMPANY NUMBER(10)
BRANCH NUMBER(4)
DEAD_FLG VARCHAR2(1)
FORENAME VARCHAR2(20)
TITLE VARCHAR2(5)
MID_INITIAL VARCHAR2(1)
GENDER VARCHAR2(1)
FRAUD_FLG VARCHAR2(1)
SQL> desc v_pie_servcon
Name Null? Type
SERVCON NOT NULL NUMBER(10)
CONTRACT NUMBER(10)
CONNECTION_CURR NUMBER(10)
CONTACT NUMBER(8)
SQL> desc v_pie_tpplan_compline
Name Null? Type
TPPLAN_COMPLINE NOT NULL NUMBER(10)
SERVCON NUMBER(10)
PPLAN NUMBER(10)
SQL> desc v_pie_tpplan_comp_detail
Name Null? Type
TPPLAN_COMPLINE NOT NULL NUMBER(10)
RULE_DETAIL_NO NOT NULL VARCHAR2(5)
RULE_DETAIL_LINE NOT NULL NUMBER(2)
U_VERSION VARCHAR2(1)
OPTION VARCHAR2(40)
OPT_STRING VARCHAR2(40)
SQL> desc v_pie_tpplan
Name Null? Type
SERVCON NOT NULL NUMBER(10)
PPLAN NOT NULL NUMBER(10)
U_VERSION VARCHAR2(1)
SQL> desc v_pie_connection
Name Null? Type
CONNECTION NOT NULL NUMBER(10)
CONTACT NUMBER(8)
ADDRESSNO NUMBER(5)
TRANSACTION NUMBER(10)
TPRODLINE NUMBER(10)
CONTRACT NUMBER(10)
SERVCON NUMBER(10)
SQL> desc v_pie_tprodline
Name Null? Type
TRANSACTION NOT NULL NUMBER(10)
TPRODLINE NOT NULL NUMBER(10)
CONTACT NUMBER(8)
PRODUCT NUMBER(10)
ORDER_QTY NUMBER(12)
RETAIL_AMT NUMBER
SALE_AMT NUMBER
SQL> desc v_pie_product
Name Null? Type
PRODUCT NOT NULL NUMBER(10)
PART VARCHAR2(20)
PRODUCT_DESCR VARCHAR2(40)
This is the code to create an XML view, validating against the schema:
create OR REPLACE VIEW v_xml_validate AS
SELECT SYS_XMLAGG(XMLQuery('
<PIE_ERROR>
<ERROR_CODE>"0001"</ERROR_CODE>
<DESCRIPTION>"There was an error with this customer"</DESCRIPTION>
</PIE_ERROR>,
<Transaction>
{for $t in ora:view("V_PIE_TRANSACTION")/ROW
    ,$ct in ora:view("V_PIE_CONTACT")/ROW
    ,$b in ora:view("V_PIE_BRANCH")/ROW
    ,$bf in ora:view("V_PIE_BRANCH_FEATURE")/ROW
where $t/CONTACT = $ct/CONTACT_ID
and   $t/BRANCH = $b/BRANCH
and   $b/BRANCH = $bf/BRANCH
return ($t/TRANSACTION_NUMBER
        ,$t/TRANSACTION_STATUS
        ,$ct/CONTACT_ID
        ,$t/INVOICE_NUMBER
        ,$bf/CHANNEL
        ,$t/CSA
        ,$t/OPEN_DATETIME
        ,$t/CLOSED_DATETIME
        ,<Orderline>
              {for $tpl in ora:view("V_PIE_TPRODLINE")/ROW
                  ,$pr in ora:view("V_PIE_PRODUCT")/ROW
                  ,$cmpesn in ora:view("V_PIE_COMPESN")/ROW
               where $tpl/TRANSACTION eq $t/TRANSACTION_NUMBER
               and   $tpl/PRODUCT eq $pr/PRODUCT
               and   $ct/CONTACT_ID eq $cmpesn/CONTACT
               return ($tpl/ORDER_QTY
                      ,$tpl/RETAIL_AMT
                      ,$tpl/SALE_AMT
                      ,$pr/PRODUCT_DESCR
                      ,$pr/PART
                      ,$cmpesn/IMEI
                      ,<BankDetails>
                           {for $conn in ora:view("V_PIE_CONNECTION")/ROW
                            for $scon in ora:view("V_PIE_SERVCON")/ROW
                            for $tpp in ora:view("V_PIE_TPPLAN")/ROW
                            for $tppc in ora:view("V_PIE_TPPLAN_COMPLINE")/ROW
                            for $tppcd in ora:view("V_PIE_TPPLAN_COMP_DETAIL")/ROW
                            for $al in ora:view("V_PIE_ACCOUNT_LINK")/ROW
                            for $ad in ora:view("V_PIE_ACCOUNT_DETAIL")/ROW
                            for $bd in ora:view("V_PIE_BANK_DETAIL")/ROW
                            where $conn/CONTACT eq $ct/CONTACT_ID
                            and   $scon/CONTACT eq $conn/CONTACT
                            and   $tpp/SERVCON eq $scon/SERVCON
                            and   $tppc/SERVCON eq $tpp/SERVCON
                            and   $tppc/PPLAN eq $tpp/PPLAN
                            and   $tppcd/TPPLAN_COMPLINE eq $tppc/TPPLAN_COMPLINE
                            and   $al/AC_DET eq $tppcd/OPT_STRING
                            and   $ad/ACCOUNT_DETAIL eq $al/ACCOUNT_DETAIL
                            and   $bd/BANK_DETAIL eq $ad/BANK_DETAIL
                            return ($bd/BANK_NAME
                                   ,$ad/ACCOUNT_NAME
                                   ,$ad/ACCOUNT_NUMBER
                                   ,$ad/SORT_CODE
</BankDetails>
</Orderline>
</Transaction>'
RETURNING CONTENT),
XMLFORMAT.CREATEFORMAT('TransInfo','USE_GIVEN_SCHEMA','test_1.xsd', 'http://xmlns.cpw.co.uk/CPW/EPOS/Order/RetrieveTransaction/RetrieveTransaction', NULL, NULL)) AS xml_string FROM DUAL;
The view is created with no errors. Selecting * from it, however, gives:
ORA-19201 - Datatype not supported
Marrying the XML to the XSD shows nothing obviously wrong.
Thanks,
Ray.

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

Inbound XML validation failed against schema

Hi Experts,
we are getting mapping exception at the time of Inbound XML validation but in the trace it is not displaying
like which fields are not validating.
I have gone through the Interface mapping in that we are using 2 mapping programs one is imported archives(java mapping) for validation
and another one is for Messaging mapping.we are getting the problem at the time of validation itself,
i have navigated by double clicking on the imported archive mapping program it is taken into another page
where we will get the archive programs.we have soo many xsd files and its path, and one .java file and class file
for validatting the xsd files. up to now everything is fine.
please find the remaining question in the below post

CONTINUATION QUESTION FOR THE ABOVE
If i click on the xsd files it is displaying the complete schema structure, but in the case of 2 xsd files(those are using in one
interface where we are getting validation error)it is displaying the error like "cannot display file com/AAA/BBB/java/CCC/xi/bc/validator/xsds/<filename.xsd> unable to determine code".as per my assumption the xsd file
is not present in that perticular path, if so how can i put these xsd files into the path specified? how can i get that folders to nagvigate into that path? And also i am not able to download the xsd file from the external defination, is it work if i copy the file into note pad and by changing the extension as .xsd ?
We are using PI7.0, give me an idea how to resolve the issue
Thanks in Advance

- 0 fatal error(s), 3 error(s) ----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 ----------- ERROR: Key not valid for use in specified state. ERROR: Install MSI payload failed with error: 1603 - Fatal error durin

I keep getting this error code when trying to download
- 0 fatal error(s), 3 error(s) ----------- Payload: Adobe Photoshop Lightroom 5 5.6.0.0 Adobe_Lightroom_x64.msi_5.6 ----------- ERROR: Key not valid for use in specified state. ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation. MSI Error message: Key not valid for use in specified state. ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1603

Generally this error happens because of an encrypted folder or insufficient permissions on that folder: http://support.microsoft.com/kb/834484 (MS Explanation)
Adobe has a page here: Error 1603: A fatal error occurred during installation

B2B is not validating payloads against uploaded schemas

Similar Messages

Maybe you are looking for