JAXB Validation without a Schema

Part of the benefit of JAXB is that a schema is not required; annotating Java classes alone allows for XML serialization/deserialization. With the deprecation of the Unmarshaller.setValidating() in favor of the unmarshaller.setSchema() method, however, it seems that validation is only available when an XSD is present. Is there another way to validate XML during unmarshalling without a physical schema file?

Unmarshaller#setValidating(boolean) is deprecated as of 2.0 [1].
This method throws an UnsupportedOperationException in the UnmarshallerImpl class within sun's v2 jaxb implementation.
[1] https://jaxb.dev.java.net/nonav/jaxb20-pfd/api/javax/xml/bind/Unmarshaller.html#setValidating(boolean)

Similar Messages

JAXB Validation Error

Hi,
Iam using JAXB. I get an validation error. When i try to marshal an object to XML. The code is simple as shown below
1. Container.xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://agi.com"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://agi.com"
elementFormDefault="qualified">
<complexType name="ContainerType" abstract="true">
<sequence>
<choice>
<element name="File" type="anyType" />
<element name="Pen" type="anyType" />
</choice>
</sequence>
</complexType>
<element name="Container" type="tns:ContainerType" abstract="true" />
</schema>
2. Holder.xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://agi.com"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://agi.com"
elementFormDefault="qualified">
<include schemaLocation="Container.xsd"></include>
<complexType name="HolderType">
<complexContent>
<restriction base="tns:ContainerType">
<sequence>
<choice>
<element name="File">
<complexType>
<sequence>
<element name="FileName"
type="string">
</element>
<element name="Capacity"
type="integer">
</element>
</sequence>
</complexType>
</element>
<element name="Pen">
<complexType>
<sequence>
<element name="Make"
type="string">
</element>
</sequence>
</complexType>
</element>
</choice>
</sequence>
</restriction>
</complexContent>
</complexType>
<element name="Holder" type="tns:HolderType"></element>
</schema>
Main.java
package test.client;
import java.io.PrintWriter;
import java.io.StringWriter;
import java.math.BigInteger;
import java.util.List;
import javax.xml.bind.JAXBContext;
import javax.xml.bind.Marshaller;
import javax.xml.bind.Unmarshaller;
import javax.xml.bind.Validator;
import test.vo.AnyType;
import test.vo.Holder;
import test.vo.ObjectFactory;
import test.vo.HolderType.FileType;
import test.vo.HolderType.PenType;
import com.sun.xml.bind.StringInputStream;
public class Main {
public static void main(String s[]) throws Exception{
JAXBContext ctx = JAXBContext.newInstance("test.vo" );
ObjectFactory obj = new ObjectFactory();
Holder input = obj.createHolder();
FileType file = obj.createHolderTypeFileType();
file.setCapacity( BigInteger.valueOf(35) );
file.setFileName("Accounts");
AnyType any = obj.createAnyType();
List lst = any.getContent();
lst.add(file);
input.setFile(any);
Marshaller marsh = ctx.createMarshaller();
marsh.setProperty(Marshaller.JAXB_FORMATTED_OUTPUT,
new Boolean(true));
marsh.setProperty(Marshaller.JAXB_SCHEMA_LOCATION,
"http://agi.com");
Validator validator = ctx.createValidator();
validator.validate(input);
StringWriter sw = new StringWriter();
marsh.marshal(input, new PrintWriter(sw) );
StringBuffer sb = sw.getBuffer();
System.out.println(sb.toString() );
This throws the following exception
DefaultValidationEventHandler: [ERROR]: tag name "test.vo.AnyType" is not allowed. Possible tag names are: <test.vo.HolderType.FileType>
Location: obj: test.vo.impl.HolderImpl@1cd8669
Exception in thread "main" com.sun.xml.bind.serializer.AbortSerializationException: tag name "test.vo.AnyType" is not allowed. Possible tag names are: <test.vo.HolderType.FileType>
at test.vo.impl.runtime.ValidationContext.reportEvent(ValidationContext.java:199)
at test.vo.impl.runtime.ValidationContext.reportEvent(ValidationContext.java:166)
at test.vo.impl.runtime.MSVValidator.childAsElementBody(MSVValidator.java:336)
at test.vo.impl.runtime.MSVValidator.childAsBody(MSVValidator.java:292)
at test.vo.impl.ContainerTypeImpl.serializeBody(ContainerTypeImpl.java:52)
at test.vo.impl.HolderTypeImpl.serializeBody(HolderTypeImpl.java:30)
at test.vo.impl.HolderImpl.serializeBody(HolderImpl.java:43)
at test.vo.impl.runtime.MSVValidator._validate(MSVValidator.java:102)
at test.vo.impl.runtime.MSVValidator.validate(MSVValidator.java:77)
at test.vo.impl.runtime.ValidationContext.validate(ValidationContext.java:75)
at test.vo.impl.runtime.ValidatorImpl.validate(ValidatorImpl.java:121)
at test.vo.impl.runtime.ValidatorImpl.validate(ValidatorImpl.java:104)
at test.client.Main.main(Main.java:63)
However if i commentout the validation it works fine yeilding the
following result
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Holder xsi:schemaLocation="http://agi.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://agi.com">
<File>
<FileName>Accounts</FileName>
<Capacity>35</Capacity>
</File>
</Holder>
Which look good conforming to the schema above
It willbe helpful if someout could point out the mistake iam doing
Please help
Regards
Agilan Palani

I changed the code
marsh.setProperty(Marshaller.JAXB_SCHEMA_LOCATION,"http://agi.com Holder.xsd");
to
marsh.setProperty(Marshaller.JAXB_SCHEMA_LOCATION,"http://agi.com E:/Agilan/Holder.xsd");
But still the same error.
I have validated the generated xml using XMLObjective. It says the generated xml is valid against the schema.
I really dont know why the JAXB validation fails?
Please help

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

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);

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

Button action bypass validation without using Immediate=true

I have a Form in a page, and a "Query" button to popup a dialog for user to search some information, and help user to fill-in some fields.
I want the "Query" button to ignoral all the validations in the Form (e.g.: required fields). I tried to set the Immedate for the button, but I found I cannot set any inputText value inside ReturnListener event-handler with Immedate is true.
Is there anyway to have a button to action, and bypass all the validation without using Immediate=true?
Thanks,
Samson Fu

Hi,
if you are on JDeveloper 11g, have a look at the skipValidation property on the ADF binding and read: http://oracle.com/technology/products/jdev/tips/fnimphius/ppr_subform/index.html
You can implement a similar approach
Frank

Validating with multiple schemas

I am setting the schama attribute as follow:
String schemaSource = "C:\\Documents and Settings\\ayache\\My Documents\\C5 XML\\schema\\searhRequest.xsd";
String JAXP_SCHEMA_SOURCE = "http://java.sun.com/xml/jaxp/properties/schemaSource";
builderFactory.setAttribute(JAXP_SCHEMA_SOURCE, new File(schemaSource));searchRequest.xsd contains include statement: it referes to another schema. When i try to validate the xml document using the scheam above error is thrown stating that the elements that are defined in the second schema(BookingProfile.xsd) are not recognised or can't be resolved.
Is there a way to set multiple schemas?
Your help is much appreciated.

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

How do i check to see if a code is valid without redeeming

I have a couple movie codes and I want to see if they are still valid without redeeming them. How do I go about this?

Actually, I just found a way to verify if a code is redeemed or not without actually redeeming it. Thanks for the support though.

Validating WSDL with schema imports

Hello,
i'm trying to validate a WSDL that uses a schema import construction, like
<wsdl:types>
<xsd:schema>

<xsd:import namespace="http://foo" schemaLocation="http://localhost/foo.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="MyMessage">
<wsdl:part name="bar" type="foo:BarType"/>
</wsdl:message>
I keep getting the error :
Validating foo.wsdl
Schema type not found: QName(http://foo, BarType)
Validate WSDL: has errors.If I paste the content of foo.xsd inline in the wsdl file, it works ok.
The wsdl file validates in XMLSpy; it can even successfully generate SOAP requests from it.
Am I wrong somewhere ?
Did anyone succeed in importing an external schema inside a wsdl file with JDev ?
thx.

Does anyone know if this is working in JDeveloper 10.1.3?
Another (relared) question: we use multiple wsdl files to define our web services (according to the Venetian Blind design). Since the project uses WebLogic as AS we used their mechanism to generate the webservice. The only thing is that generating a stub via WebLogic JAX-RPC fails due to namespace errors.
When I try to generate a stub based on the JDeveloper 10.1.3 wizards using the top-level wsdl (the one importing other wsdl's) I get an invalid wsdl message and the options in the wizard are disabled. Anyone know whether multiple wsdl's are supported in JDeveloper 10.1.3?
Ronald

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 without a schema

I have a XML file and do not have a corresponding XML schema for it. Is it possible to import it into XDB without a schema.

What do you mean with "import", what database version are you working with?

JAXB Validation

Using JAXB I have generated and compiled classes for my schema and everything appears ok.
I can create new objects using the ObjectFactory and I am able to validate those objects.
If an object is invalid I know how to inspect the resultant ValidationEvent and determine why the error occurred.
However, although I am able to determine the cause of a validation failure, how can I determine - and this is the important bit for me - without prior knowledge of the schema, how to resolve this failure.
For example:
My schema allows me to create Apple objects. Each apple must have a type and that type must be either 'one ' or 'two'
Therefore:
valid - <apple><type>one<type></apple>
invalid - <apple><type>three<type></apple>
invalid:- <apple></apple>
The following bit of code will create a valid apple object:
ObjectFactory objFactory = new ObjectFactory();
AppleImpl apple = (AppleImpl)objFactory.createApple();
apple.setType("one);
However, without calling setType("one") my apple object will be invalid.
Examining that ValidationEvent returned from validating the object I can determine what is wrong with the object.
ValidationEvent event;
event.getNode() -> null
event.getLocator().getSeverity() -> 1
event.getLocator().getColumnNumber() -> 1
event.getLocator().getLineNumber() -> -1
event.getLocator().getOffset( ) -> -1
event.getLocator().getURL( ) -> null
event.getLocator().getObject( ) -> Apple@d1c65d
event.getLocator().toString( ) -> So now I know the problem is with the type field.
However, without prior knowledge of the schema and without knowing the type field must be set to 'one' or 'two' then how can I determine this? What methods are available in JAXB to determine what values I can set type to?
Or is this beyond the scope of JAXB?
(also posted in Java Technologies for Web Services -wasn't sure of best place for it)

Many thanks for your response. However, if you have any code snippets/examples relating I go from JAXB to look at DOM validation that 'd be useful. In fact, anything at all as to where I should start looking.
Hi ,
Did u find any solution,please let me know.

File Adapte picking up XML if XSD valid without verifing the XSD in adapter

hi',
I am facing one issue
I have a sample XML file which I want to read through BPEL process
for this I have configured the file adapter with the schema and reading the file adapter with the receive activity
next I have created one XSD file (which file adapter referes to) and one XML file,
File adapter reads it after the XML file gets validated with the XSD which is kept in a location *'/test/xsd/emp.xsd'*,
now the issue is that the file adapter is picking up and initiating the process without verifying the XSD mentioned in the adapter
it is only checking the XML file with the XSD mentioned in the XML,
for example if I have a xml file which is refering to some other schema it also gets read by file adapter without worring about what schema is mentioned in file adapter
please advice me is this the way File adapter works in Oracle BPEL or I am doing some thing wrong
I am using SOA suite 10.1.3.3.0 which is deployed in UNIX enviornment.
thanks
Yatan

thanks Ketan ,
as you suggested, after adding validateXML to true, the XML is getting validated to the XSD in the adapter,
the process is getting invoked and the receive activity is throwing error of 'Invalid XML', this is perfect as I expected
however now the issue is, the file which is invalid in terms of XSD present in the file adapter is still being archived to 'success dir' i.e. 'LogicalArchiveDirectory', ideally it should have moved to fail directory,
but if the XML file is not complete or having some error in terms of the XSD it is refering to 'target namespace' and 'target location'
then it will move to the fail directory and the receive activity is also showing the error,
see this is how I have configured my bpel.xml file for the file adapter.
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="Read_Tph_ProdTrans_File">
<property name=*"prod_trans_success_file" type="LogicalArchiveDirectory"*>/aaa/bb/ccc/wis/tph/bpl_inbound/adjust/success</property>
<property name=*"prod_trans_incoming_file" type="LogicalDirectory"*>/aaa/bb/ccc/wis/tph/bpl_inbound/adjust/new</property>
<property name="portType">Read_ptt</property>
<property name="rejectedMessageHandlers">file:///aaa/bb/ccc/wis/tph/bpl_inbound/adjust/fail</property>
</activationAgent>
please advice how to bring this adapter to proper behaviour.
thanks
Yatan

JAXB - validation problem with regexp bound int type

Hello everyone,
I have a simpleType defined in my schema as follows:
<xs:simpleType name="BasketRetentionType">
<xs:restriction base="xs:int">
<xs:totalDigits value="10"/>
<xs:pattern value="(0|[1-9][0-9]*)"/>
</xs:restriction>
</xs:simpleType>
'020' and '+20' values are not allowed (as I need it to be), but I've got them validated by JAXB.
I wonder if there's anyone who can confirm this or shall I add any java code I may have ignored.
I'm working with :
- OS : Microsoft Windows NT v4.0 Serv.Pack6
- java : j2sdk1.4.1_05
- jaxb : jwsdp-1.3
Thanks
L. Chiartano

Try this pattern: +\\d*|\\d*
Also take a look at:
http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html
I don't know if it's \\d or \d, trail and error.
bye ki

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)

JAXB Validation without a Schema

Similar Messages

Maybe you are looking for