Types in XML Schema

I've tried to create some XML Schema but was unable to find any information what type should I use e.g. for radiobuttonlist.
Could somebody give me some clue or link to document where it's mentioned?

Hi dex13x,
I found this document helpfull, though it is for Designer 7.0 I don't think the schema handling has changed much, http://partners.adobe.com/public/developer/en/livecycle/lc_designer_XML_schemas.pdf.
By default a RadioButtonList is an exclusive group of integer values so I would define an element of type xs:int, or something based on xs:int with the valid values. If you have a RadioButtonList with text values then you could do the same thing with but based on xs:string.
Somehow, I feel I have misunderstood your question but I hope the document helps.
Bruce

Similar Messages

Is it possible to use List Type in XML schema within the SOA Rule author?

Is it possible to use List Type in XML schema within the SOA Suite Rule author? The reason is that with the following XSD, Rule author generates XML facts of type "List" for the element "ResultSet". Basically I want to check the Input facts (Input1, Input2, Input3) for some conditions and then assign action to the element Resultset of type List (array). The output Resultset can contain multiple values based on the input facts. My problem is that I am unable to see the ResultSet in the "Assign" action type of the action block. Is it possible to use the Resultset of type List with the Rule author or is there any limitation on the rule author and any workaround for this?
<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.oracle.com/ns/TestMultipleOutputs"
elementFormDefault="qualified">
<element name="TestMultipleOutputs">
<complexType>
<sequence minOccurs="0">
<element name="Input1" type="string" minOccurs="0"/>
<element name="Input2" type="string" minOccurs="0"/>
<element name="Input3" type="string" minOccurs="0"/>
<element name="ResultSet" type="string" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</complexType>
</element>
</schema>
--Thanks a lot

Hi Richard,
I have slightly modified the xml schema you suggested and was able to import into the rule author. the following is the modified XSD. Rule Author created a List type for the "ResultSet" . I still don't see "Resultset" in the assign action, so I tried creating RL function in order to assign the output to the "Resultset", but was unsuccessful so far. can you please let me know how to populate the resultset with the output values? Thanks a lot.
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified"
xmlns:ns1="http://www.oracle.com/ns/TestComplexOutputs"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.oracle.com/ns/TestComplexOutputs"
xmlns:tns="http://www.oracle.com/ns/TestComplexOutputs"
elementFormDefault="qualified">
<xsd:element name="TestComplexOutputs">
<xsd:complexType>
<xsd:sequence minOccurs="0">
<xsd:element name="Input1" type="xsd:string" minOccurs="0"/>
<xsd:element name="Input2" type="xsd:string" minOccurs="0"/>
<xsd:element name="Input3" type="xsd:string" minOccurs="0"/>
<xsd:element name="ResultSet" type="tns:ResultSetType" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ResultSetType">
<xsd:sequence>
<xsd:element name="ResultSet" type="tns:ResultSetStructure" minOccurs="1"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ResultSetStructure">
<xsd:sequence>
<xsd:element name="ErrorReason">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Null value for int and datetime date type in xml schema

hi:
I am embarrassed by a qustion in xml schema; i defined a xml schema file like
this:
<elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:element name="test">
<xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element name="password" type="xs:string" nillable="true"/>
<xs:element name="user" type="xs:int" nillable="true"/>
<xs:element name="s_time" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
and I send this file to workflow clientrequest() node, I wanted to receive data
in this schema file.but when i send null value to the element "user" and "s_time"
in workshop test tool(test soap),and use function in xmlbean like isNilUser or
isNilStime, one error occur.
I don't kown why, I had to ask the engineer of bea in china, one told me a bug.
is that true?

Visakh16 I cant agree more with you on it, it is good but in production u cant have them change maxrows. I think
Patrick Hurst is a better option. debug the package have it running and move up
Please mark as helpful and propose as answer if you find this as correct!!! Thanks,Dia Agha .
Hmm..Why do you need to change it in production?
What I suggested was to tweak the setting in dev machine so that it interprets the Excel file datatypes correctly when doing development. Once mapping is set correctly then it will work fine when in production or in any other environment. The tweaking is
just to make sure it interprets the datatype correctly at design time and has nothing to do with production deployment
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Date type in xml schema

The date type in schema processor doesn't work. I can replace the date in the xml with any character and still get the xml validated. Same problem with year and month type.

Hi,
The behaviour I posted above has been identified as a bug by Oracle and a patch(#6053186) now exists for this problem. This patch is available for database version 10.2.0.3 and the bug would eventually be fixed only in database version 11g according to the details published for the bug.
Rgds,
Rakesh.

Exp XML Schema (.xsd) to another schema on same instance

Hello,
I hope someone on this forum can help me or point me in the correct direction. I want to export a schema which contains a table (EQUIPMENT) which has a XMLType column defined against a registered .xsd. I would then like to restored this schema to another schema on the same instance (development instance) and also onto another db instance.
I have been trying to do this with the help of "Chapter 30 Importing and Exporting XMLType Tables" from the Oracle® XML DB Developer's Guide
10g Release 2 (10.2). Unfortunately without success. At the end of this message I have encluded sample error messages that I am receiving for creation of TYPES which is causing my import to fail.
I cannot find any examples on the web on how to achieve an exp from one schema and imp in another either on the same instance or another one.
DDL for my table is :
create table EQUIPMENT
ID number(7) not null,
STATUSID number(7) not null,
ATTRIBUTEDATA xmltype
xmltype column ATTRIBUTEDATA xmlschema "EQUIPMENT.xsd" element EQUIPMENT_XML
tablespace TBS_DATA1;
Three test runs as follows:
1. Using an empty u2 schema and I register the .xsd file. Then I try to import (FROMUSER - TOUSER imp mode) my dump file which leads to the following error:
IMP-00017: following statement failed with ORACLE error 2304:
"CREATE TYPE "MTA1440_T" TIMESTAMP '2007-11-14:14:42:16' OID '3EE57B10307317"
"74E044080020C94102' AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T",""
"ATTRIBUTE_01" NUMBER(38),"ATTRIBUTE_02" VARCHAR2(4000 CHAR),"ATTRIBUTE_03" "
"VARCHAR2(4000 CHAR),"ATTRIBUTE_04" NUMBER(38),"ATTRIBUTE_05" VARCHAR2(4000 "
"CHAR))FINAL INSTANTIABLE "
IMP-00003: ORACLE error 2304 encountered
NOTE: Even though import failed, I now see a new TYPE created called "MTA1526_T".
2. If I try to create the TYPE as is from the error above I get the following error:
SQL> CREATE TYPE MTA1440_T
2 OID '3EE57B1030731774E044080020C94102'
3 AS OBJECT (SYS_XDBPD$ XDB.XDB$RAW_LIST_T,
4 ATTRIBUTE_01 NUMBER(38),
5 ATTRIBUTE_02 VARCHAR2(4000 CHAR),
6 ATTRIBUTE_03 VARCHAR2(4000 CHAR),
7 ATTRIBUTE_04 NUMBER(38),
8 ATTRIBUTE_05 VARCHAR2(4000 CHAR)) FINAL INSTANTIABLE;
9 /
CREATE TYPE MTA1440_T
ERROR at line 1:
ORA-02304: invalid object identifier literal
3. So now I create the "MTA1440_T" type without the OID value and retry the import.
IMP-00061: Warning: Object type "U2"."MTA1440_T" already exists with a different identifier
"CREATE TYPE "MTA1440_T" TIMESTAMP '2007-11-14:14:42:16' OID '3EE57B10307317"
"74E044080020C94102' AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T",""
"ATTRIBUTE_01" NUMBER(38),"ATTRIBUTE_02" VARCHAR2(4000 CHAR),"ATTRIBUTE_03" "
"VARCHAR2(4000 CHAR),"ATTRIBUTE_04" NUMBER(38),"ATTRIBUTE_05" VARCHAR2(4000 "
"CHAR))FINAL INSTANTIABLE "
Questions from me:
A. Can I export TYPES only as suggested by the online documentation ?
B. If importing onto same instance in another schema surely the OID for the TYPE will always fail - so then why can the import not create the required TYPE name itself during the import ?
C. Should I use global TYPES and Register the .XSD globally for all schema's in an instance to validate against .. would this prevent me from having errors on an import ?
I would appreciate any insight any one could provide me. Many thanks in advance.
Dom

Hi Guys,
Thank you all for the replies. I am dissappointed to hear that in 10g does not support exp/imp of schema's structured XML. However I am a little confused or should I say mislead by the "" documentation I
Here is an extract from chapter "30 - Importing and Exporting XMLType Tables" from the Oracle XML DB 10g Developers Guide documentation:
"..... Oracle Database supports the import and export of XML schema-based XMLType tables. An XMLType table depends on the XML schema used to define it. Similarly the XML schema has dependencies on the SQL object types created or specified for it. Thus, exporting a user with XML schema-based XMLType tables, consists of the following steps:
1. Exporting SQL Types During XML Schema Registration. As a part of the XML
schema registration process .....
2. Exporting XML Schemas. After all the types are exported, XML schemas are
exported as XML text .....
3. Exporting XML Tables. The next step is to export the tables. Export of each table consists of two steps:
A. The table definition is exported as a part of the CREATE TABLE statement....
B. The data in the table is exported as XML text. Note that data for out-of-line
tables is.....
From this documentation I was under the impression that the exp/imp of XML Schema-Based XMLType Tables was supported.
Regarding the backup mechanism/strategy for database schema's containing tables with Schema-Based XMLTypes what would you recommend the best online backup method to use - tablespace backups ?
What I need to be able to do in day-to-day work is to have the ability to be able to take a copy of a customers UAT or production database schema and apply it to a dev or test db instance here for bug testing etc. Do you have any advice on best to achieve this without the use of an exp/imp when the schema will contain Schema-Based XMLType tables.
Thank you all for your assistance so far.

Any function module/program to write-xml schema of a idoctype

Hi experts,
I need to write the xml format into an internal table.
input---idoc type.
output--xml schema file in an internal table/or in some file.
Through we60 we can get the xml schema.but through some program i want to get it .how to go for it.
Any function module do you suggest which fits to this requirement and do the work for me.
For ex: idoc type--orders05
Message was edited by:
dasr r

Hello Dasr
There are several function modules available. Please check yourself if any of them matches your demands.
EDIN                           IDoc: Eingangsverarbeitung
IDOC_INBOUND_XML_VIA_HTTP      eingang über http
IDOC_XML_FROM_FILE             IDoc: Eingangsverarbeitung vom XML über Dateischnittstelle
IDOC_ADAPTER_MB                Message Broker IDoc Adapter
IDX_IDOC_TO_XML                Konvertierung IDoc nach IDoc XML im XMB
IDOC_XML1                      erweiterte Tabellenpflege (generiert)
IDOC_XML_DISPLAY               Anzeigen eines IDocs in XML-Format mit XSL
IDOC_XML_TRANSFORM             Anzeigen eines IDocs in XML-Format mit XSL
Regards
Uwe

XML Schema Component Naming Convention

Is there a naming convention when you create an XML Schema? For example,
When you create a Type component, then the first letter of its name should be upper case ie. BMW, Honda, AutombileEngine ...etc.
When you create an Element component, then the first letter of its name is lowercase ie. engine, car, guestCar ..etc.
Do we have such naming convention for XML Schema?
Thanks

I am giving this from my document which i prepared for one of my customer
2     General Guidelines for design of XML schema documents
The representation of data in an XML format will be a key component of development within SOA. Therefore, the design and development of XML schemas should be as rigorous an activity as designing and developing code or designing database schemas. As such, when creating an XML schema you should be working within a development process and working to a set of design guidelines and coding standards (when writing the XML schema file). XML schemas should be reviewed for accuracy and compliance with guidelines and standards. Each of the requirements in the list below is a general requirement for all XML schemas to be deployed in the SOA environment.
•     Understandable: XML schemas should be clear, consistent and unambiguous. They should contain human readable documentation and, where appropriate, links to requirements or design documents.
•     Semantically Complete: An XML schema should define, for one or more target XML documents, each and every element and attribute that is understood by your solution when processing target documents.
•     Constraining: XML schemas are used as contracts between both publisher and consumer. As such, they must be able to be validated as concisely as possible. When designing an XML schema constraints should be identified for the values for all the elements and attributes that the application uses and relies on to the set of values that the application can handle. A valid document should imply valid data within the limits of what can be specified by the XML Schema language.
•     Uniquely identifiable: XML schemas should import and include other XML schema files rather than duplicating types and elements locally.
•     Reusable: XML schemas should be specified in such a way that types and other XML schemas can leverage elements. Every type defined in an XML schema that is the content type of an attribute or an element should be defined globally (i.e., at the top level in the Schema). Types that are defined globally can be reused in other XML schemas. Schemas should be separated into logical sections which can be included into the main schema file.
•     Extensible: Schemas should be designed to be extensible—that is, new elements and attributes can be inserted throughout the document.
Every schema should use at least two namespaces – the targetNamespace and the XML Schema (http://www.w3.org/2001/XMLSchema) namespace.
Create typed elements that can be referred to by object elements:
Example:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.soa.com"
xmlns="http://www.soai.com"
elementFormDefault="qualified">
<xsd:complexType name="PersonType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="SSN" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.company.org"
xmlns="http://www.company.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="Person.xsd"/>
<xsd:include schemaLocation="Product.xsd"/>
<xsd:element name="Company">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
<xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
•     Recognize that with XML Schemas you will not be able to express all your business rules.
o     Express those business rules using XSLT.
•     Use type definitions
Elements vs Attributes
•     Use attributes for metadata about the parent element.
•     Use attributes for data that is semantically tied to the enclosing element.
•     Use elements for data that have a meaning separate from the enclosing element.
•     Use attributes when the value will be frequently present in order to improve the human readable form of an XML instance document or reduce its size.
•     If you don't know which to use, then use the element form (which is more extensible).
2.1.1     Element, Types and attribute names
Create a descriptive name without it being excessively long (no more than 32 characters).
Elements and Types should be named in Upper Camel Case. Upper Camel Case capitalizes the first character of each word and compounds the name (remove all whitespace).
Attributes should be named in Lower Camel Case. Lower Camel Case capitalizes the first character of each word except the first word and compounds the name.
Simple and Complex type names
XML Schema has separate symbol space for elements and types so they may have the same name. The best practice is to append the word "Type" to all simple and complex type names to aid in human readability and comprehension.
Element, attribute and type names MUST be in a singular form unless the concept itself is plural.
2.1.1.1     XML Schema versioning
Use major and minor version tracking:
Major—completely different structure and semantics, most likely not backward compatible
Minor—backward compatible changes which introduce new features without removing or changing the semantics of existing structures
2.1.1.2     Indication of version in the namespace URI
Specify a namespace URI as follows
http://$domain/$groupSpecifier/$namespaceTitle/$version
The groupSpecifier can include several levels, e.g., /www.soa.com/SOA/USA/.
An example namespace could be:
http://www.soa.com/SOA/order/2

Not able to pass cyclic XML schema type to a webservice method

I have a webservice method called getData(GetDataDocument
gDoc).
I constructed a request with object (which exactly satisfy
the XML schema def) to call up the getData(). [From my java client
also I did the same; but the java classes have been generated using
apache's xmlBeans; this works fine with the same kind of request].
But the soap request constructed from flex does not get
generated with all the values that I set in the request object.
On further observation, I found out that if the schema
involves cyclic elements, the soap request is not getting
constructed as desired.
My schema def:
<complexType name="PredicateBagType">
<sequence>
<choice>
<element maxOccurs="unbounded" minOccurs="0"
name="PredicateBag" type="tns:PredicateBagType"/>
<element maxOccurs="unbounded" minOccurs="0"
name="BinaryPredicate" type="tns:BinaryPredicateType"/>
<element maxOccurs="unbounded" minOccurs="0"
name="UnaryPredicate" type="tns:UnaryPredicateType"/>
</choice>
</sequence>
<attribute name="contextNode"
type="tns:contextNodeIDType"/>
<attribute default="false" name="negate"
type="boolean"/>
<attribute name="type"
type="tns:PredicateBagTypeType"/>
</complexType>
Note that the PredicateBagType may contain another
PredicateBagType.
I have constructed my request with objects in my flex
application . Though I have set the BinaryPredicate object in my
PredicateBag object, the soap request constructed looks like this
which is not desired
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<tns:get_Data maxPrograms="0" personalInfoUse="false"
xmlns:tns="urn:tva:transport:2005">
<tns:QueryConstraints>
<tns:PredicateBag contextNode="1" negate="false"
type="AND"/>
</tns:QueryConstraints>
<tns:RequestedTables>
<tns:Table type="ProgramInformationTable"/>
</tns:RequestedTables>
</tns:get_Data>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>.
If I comment out the PredicateBagType choice in my xsd, the
flex application constructs the soap request looks like this.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<tns:get_Data maxPrograms="0" personalInfoUse="false"
xmlns:tns="urn:tva:transport:2005">
<tns:QueryConstraints>
<tns:PredicateBag contextNode="ProgramInformation"
negate="false" type="AND">
<tns:BinaryPredicate fieldID="Genre" fieldValue="Fiction"
test="contains"/>
</tns:PredicateBag>
</tns:QueryConstraints>
<tns:RequestedTables>
<tns:Table type="ProgramInformationTable"/>
</tns:RequestedTables>
</tns:get_Data>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
This request holds good. But I cannot comment out the
PredicateBagType from my choice. Is this an issue with soap request
construction issue in Flex..?

Yes, <choice> is just "partial" supported in Flex 2 .
read this
link
for partial and not supported tags
Partially supported XML Schema structures
The following XML Schema structures or structure attributes
are only partially implemented in this release:
<choice>
<all>
<union>
regards
kcell

XML Schemas and "Type"

I'm having a brutal time working with this program, it doesn't even seem like it should be this hard. I won't get in to the situation yet, I keep tripping across other problems as I go. Here's the next one:
According to Eclipse, I'm not allowed to put an element with a type if it also has a restriction, because the restriction seems to (as far as I can tell) automatially attach an "anonymous type" to the element. That is to say:
<element name="foo" type="string">
    <simpleType>
        <restriction base="string">
            [restriction tags]
        </restriction>
    </simpleType>
</element>doesn't work. It also doesn't work if I don't have a "base='x'" line, but that makes a bit more sense. On the other hand:
<element name="foo">
    <simpleType>
        <restriction base="string">
            [restriction tags]
        </restriction>
    </simpleType>
</element>
does work, but causes a number of problems because "foo" no longer has a type to call its own. I'm sure I'm missing something here but I can't work out what.
Here's the exact error from Eclipse's XML Schema Validator, which places an error on foo's declaration line:
"Multiple Annotations found on this line:
- src-element.3: Element 'foo' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element.
- Element type "element" must either be followed by attribute types, '>' or '/>'."
Any help would be appreciated, thanks. :)

As the message below indicates you are defining a new simple type but in line with the element definition (enclosed by element tags). As it is in-line it is classed as an anonymous type i.e. has no name. You therefore cannot give an element a type and then specify its type in line.
Athough essentially it is a string (hence requires base type) it is nontheless a new type i.e a string with restrictions. The other way to do this, which will allow you to reuse the type is is as follows
    <xsd:element name="foo" type="myRestrictedString"/>
    <xsd:element name="foo2" type="myRestrictedString"/>
    <xsd:simpleType name="myRestrictedString">
        <xsd:restriction base="xsd:string">
            <xsd:pattern value="[0-9]{3}"/>
        </xsd:restriction>
    </xsd:simpleType>
>
"Multiple Annotations found on this line:
- src-element.3: Element 'foo' has both a 'type'
attribute and a 'anonymous type' child. Only one of
these is allowed for an element.
- Element type "element" must either be followed by
attribute types, '>' or '/>'."

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

[JAXB 2.x] Defining the XML Schema Type for XmlElementDecl

How can an XML Schema Type (XmlSchemaType) be defined for an XmlElementDecl/Ref?
The classes are as follows:
    @XmlRegistry
    class ObjectFactory {
        // XmlSchemaType is desired, but cannot be used with XmlElementDecl/Ref: @XmlSchemaType(name = "unsignedShort")
        @XmlElementDecl(namespace = "urn:com:test:namespace", name = "char", scope = com.test.Arguments.class)
        @XmlJavaTypeAdapter(com.test.CharacterAdapter.class )
        public JAXBElement<Character> createArgumentsChar(Character value) {
            return new JAXBElement<Character>(_ArgumentsChar_QNAME, Character.class, com.test.Arguments.class, value);
    @XmlAccessorType(XmlAccessType.FIELD)
    @XmlType(name = "", propOrder = { "arguments" })
    class Arguments {
        @XmlElementRefs( {
                @XmlElementRef(name = "char", namespace = "urn:com:test:namespace", type = JAXBElement.class),
        protected List<JAXBElement<?>> arguments;
    }The desired schema is as follows:
    <xs:element name="arguments" minOccurs="0">
        <xs:complexType>
            <xs:sequence>
                <xs:choice minOccurs="0" maxOccurs="unbounded">
                    <xs:element name="char" type="xs:unsignedShort" />
                </xs:choice>
            </xs:sequence>
        </xs:complexType>
    </xs:element>However, when generating the schema from these classes (schemagen), the resulting "char" element type is "xs:string," not "xs:unsignedShort" as desired. What annotation can be used to indicate that the type should be xs:unsignedShort? If the addition of an annotation is not possible, are there any other ways to accomplish this?
Message was edited by: Shelley (Indicated "JAXB 2")

There are mappings between XSD type and Java type table on the Sun website.

Unable to disply type created by registering XML schema

Hello,
I have tried to register my XML schema.
The process returns with success and I can see new object types created by:
select * from user_types;
However, if I perform a DESC on the object type it says:
ORA-0403: object <MyType> does not exist.
Has anybody seen the problem before ?
Thanks,
Bryan

Hi,
Thanks a lot for the reply.
I have tried out and it seems to me that the SQLType specified in my schema must be in Capital letters. Otherwise DESC won't work.
Quoting it doesn't seem to work as well.
Bryan

XML SCHEMA registration for XML TYPE (storing XML files in Oracle 10g)

I have created the XML Schema for the XML file stored in Oracle 10g and also added this Schema into the database. I have related that schema with the column in the table which contains the XML file. When i execute the query to fetch the data from the stored file i am getting a blank resultset. Is registering the XML Schema is necessary, if yes then please let me know the process of doing it. I have tried following steps to register Schema, but it is not working
Step1:
DECLARE
v_return BOOLEAN;
BEGIN
v_return := dbms_xdb.createFolder('/home/');
v_return := dbms_xdb.createFolder('/home/DEV/');
v_return := dbms_xdb.createFolder('/home/DEV/xsd/');
v_return := dbms_xdb.createFolder('/home/DEV/messages/');
v_return := dbms_xdb.createFolder('/home/DEV/employees/');
COMMIT;
END;
STEP 2:
Connecting To XML DB
Step3:
Register XML schema
I am failing to execute step number 2 and hence not able to register the schema also.

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by sudeepk:
If a java exception is thrown probably during ur install u might have forgotten
grant javauserpriv to scott;
grant javasyspriv to scott;
Thanks
[email protected]
<HR></BLOCKQUOTE>
Thank you!!!

Urgent: Help required for fetching CHILDNODE from an XML schema.

Hi All,
Good Morning to all, i have problem in extracting the child node name. I have created a xml schema say "emrxmlsample3.xsd" based on this schema i have created a xmltype table and inserted a value to the table. I have a problem in fetching the "CHILDNODE" name. Kindly help me in solving this problem. Here by i am posting all the workings i have done...
I am using the following client:
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jan 31 11:44:59 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
////////////////////////////////// XML Schema ///////////////////////
begin
dbms_xmlschema.registerSchema(
'http://www.oradev.com/emrxmlsample3.xsd',
'<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.oradev.com/emrxmlsample3.xsd"
xmlns:samp="http://www.oradev.com/emrxmlsample3.xsd"
version="1.0">
     <element name="HISTORY">
          <complexType>
               <sequence>
                    <element name="HPI">
                         <complexType>
                              <sequence>
                                   <element name = "PAIN">
                                        <complexType>
                                             <sequence>
                                                  <element name = "SET">
                                                       <complexType>
                                                            <sequence>
                                                                 <element name = "LOCATION">
                                                                      <complexType>
                                                                           <sequence>
                                                                                <element name = "HEAD" type = "string"/>
                                                                                <element name = "NECK" type = "string"/>
                                                                                <element name = "BACK" type = "string"/>
                                                                                <element name = "CHEST" type = "string"/>
                                                                                <element name = "ABDOMEN" type = "string"/>
                                                                                <element name = "JOINTS" type = "string"/>
                                                                                <element name = "OTHERS" type = "string"/>
                                                                           </sequence>
                                                                      </complexType>
                                                                 </element>
                                                                 <element name = "SEVERITY">
                                                                      <complexType>
                                                                           <sequence>
                                                                                <element name = "MILD" type = "string"/>
                                                                                <element name = "MODERATE" type = "string"/>
                                                                                <element name = "SEVERE" type = "string"/>
                                                                                <element name = "VERYSEVERE" type = "string"/>
                                                                           </sequence>
                                                                      </complexType>
                                                                 </element>
                                                                 <element name = "CHARACTER">
                                                                      <complexType>
                                                                           <sequence>
                                                                                <element name = "DIFFUSE" type = "string"/>
                                                                                <element name = "PRICKING" type = "string"/>
                                                                                <element name = "CUTTING" type = "string"/>
                                                                                <element name = "PIERCING" type = "string"/>
                                                                           </sequence>
                                                                      </complexType>
                                                                 </element>
                                                            </sequence>
                                                       </complexType>
                                                  </element>
                                             </sequence>
                                        </complexType>
                                   </element>
                              </sequence>
                         </complexType>
                    </element>
               </sequence>
          </complexType>
     </element>
     </schema>',
TRUE, TRUE, FALSE, FALSE);
end;
////////////////////////// Table which has multiple Column //////////////////////////
CREATE TABLE chipsemr3 (
id number, CHIPSEMR XmlType)
XMLTYPE CHIPSEMR STORE AS OBJECT RELATIONAL
XMLSCHEMA "http://www.oradev.com/emrxmlsample3.xsd"
ELEMENT "HISTORY";
///////////////////////////////// Insert Query in chipsxmltable //////////////////////////
INSERT INTO chipsemr3 VALUES(1,
xmltype.createxml('<?xml version="1.0"?>
<samp:HISTORY xmlns:samp="http://www.oradev.com/emrxmlsample3.xsd" >
          <HPI>
               <PAIN>
                    <SET>
                         <LOCATION>
                              <HEAD> YES </HEAD>
                              <NECK> NO </NECK>
                              <BACK> N </BACK>
                              <CHEST> N </CHEST>
                              <ABDOMEN> N </ABDOMEN>
                              <JOINTS> N </JOINTS>
                              <OTHERS> N </OTHERS>
                         </LOCATION>
                         <SEVERITY>
                              <MILD> N </MILD>
                              <MODERATE> N </MODERATE>
                              <SEVERE> N </SEVERE>
                              <VERYSEVERE> N </VERYSEVERE>
                         </SEVERITY>
                         <CHARACTER>
                              <DIFFUSE> N </DIFFUSE>
                              <PRICKING> N </PRICKING>
                              <CUTTING> N </CUTTING>
                              <PIERCING> N </PIERCING>
                         </CHARACTER>
                    </SET>
               </PAIN>
          </HPI>
</samp:HISTORY>'));
To show the Root Node Name:
1. Query
select x.CHIPSEMR.getrootelement() CHIPSNODES from chipsemr3 x, table(xmlsequence(x.CHIPSEMR.extract('//node()'))) x
Apologies if the description is not clear. Kindly let me know if further details are needed. Many thanks for your help.
Very best regards,
Godwin Jebakumar C.V.

Hi,
I'm not sure what you want actually.
You can get all elements names with :
SELECT value(x).getRootElement() chipsnodes
FROM chipsemr3 t,
     TABLE(
       XMLSequence(
         Extract(t.chipsemr, '//*')
     ) x
;or, starting with 10.2 :
SELECT x.*
FROM chipsemr3 t,
     XMLTable(
      'for $i in //* return local-name($i)'
      passing t.chipsemr
      columns chipsnode varchar2(30) path '.'
     ) x
;

XML Schema validator fails to load XML Schema from URL

I'm trying to validate an XML document against a set of XML Schemas and the parser seems to freak out: even though all the schemas are referred to in the XML and are properly recognized by Schemas field in XML document properties, I get warnings (multiple
instances):
Request for the permission of type 'System.Net.WebPermission, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed
Cannot resolve the 'schemaLocation' attribute
The schema referenced from this location in your document contains errors
The warning locations are also seemingly random - errors in schema locations are reported on closing tags inside XML or on whitespaces, and so on.
The first warning (System.Net.WebPermission) suggests it has something to do with access to remote schemas, but all the necessary remote schemas are visible in XML Schema Set editor for the document. I also enabled downloading of XML schemas in XML text
editor options.

Hi Tomasz,
Thank you for posting in MSDN forum.
Since this issue is related to the XML Schemas, so we will move this case to the XML forum:https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=xmlandnetfx
, you will get better support.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Types in XML Schema

Similar Messages

Maybe you are looking for