KEY and KEYREF support in Oracle XML DB

First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
I'm worling with the next schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <!-- En esta version, representaremos las relaciones usando atributos KEYs y KEYREFs
     Ademas, en esta version mapeamos el metamodelo de UML por completo-->
     <!-- En las anotaciones para XML DB usaremos el prefijo MMALL(MetaModelo Completo) -->
     <!--******************** DECLARACION DE LOS ELEMENTOS DEL METAMODELO *********************-->
     <xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
          <xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
               <xsd:sequence>
                    <xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
                    <xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
               </xsd:sequence>
          </xsd:complexType>
     <!-- Es en este punto donde definiremos las "PRIMARYKEYS"(KEYs) Y "FOREIGNKEYS"(KEYREFs) para simular relaciones -->
     <!-- ************************************************************************************************* *-->
          <!-- RELACIONES ModelElement - Dependency -->
          <xsd:key name="Dependency_PK">
               <xsd:selector xpath="Dependencies"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:key name="ModelElement_PK">
               <xsd:selector xpath="ModelElements"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:keyref name="Requirement_FK" refer="Dependency_PK">
               <xsd:selector xpath="ModelElements"/>
               <xsd:field xpath="requirement"/>
          </xsd:keyref>
          <xsd:keyref name="Provision_FK" refer="Dependency_PK">
               <xsd:selector xpath="ModelElements"/>
               <xsd:field xpath="provision"/>
          </xsd:keyref>
          <xsd:keyref name="Client_FK" refer="ModelElement_PK">
               <xsd:selector xpath="Dependencies"/>
               <xsd:field xpath="client"/>
          </xsd:keyref>
          <xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
               <xsd:selector xpath="Dependencies"/>
               <xsd:field xpath="supplier"/>
          </xsd:keyref>
          <!-- RELACIONES Generalization - GeneralizableElement -->
          <xsd:key name="Generalization_PK">
               <xsd:selector xpath="Generalization"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:key name="GeneralizableElement_PK">
               <xsd:selector xpath="GeneralizableElement"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="Generalization"/>
               <xsd:field xpath="subtype"/>
          </xsd:keyref>
          <xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="Generalization"/>
               <xsd:field xpath="type"/>
          </xsd:keyref>
          <xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="GeneralizableElement"/>
               <xsd:field xpath="generalization"/>
          </xsd:keyref>
          <xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="GeneralizableElement"/>
               <xsd:field xpath="specialization"/>
          </xsd:keyref>
          <!-- RELACIONES Classifier - AssociationEnd -->
          <xsd:key name="Classifier_PK">
               <xsd:selector xpath="Classifier"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:key name="AssociationEnd_PK">
               <xsd:selector xpath="AssociationEnd"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
               <xsd:selector xpath="Classifier"/>
               <xsd:field xpath="associationEnd"/>
          </xsd:keyref>
          <xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
               <xsd:selector xpath="Classifier"/>
               <xsd:field xpath="participant"/>
          </xsd:keyref>
          <xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
               <xsd:selector xpath="AssociationEnd"/>
               <xsd:field xpath="type"/>
          </xsd:keyref>
          <xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
               <xsd:selector xpath="AssociationEnd"/>
               <xsd:field xpath="specification"/>
          </xsd:keyref>
          <!-- RELACIONES AssociatioEnd - Attribute -->
          <xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
               <xsd:selector xpath="Attribute"/>
               <xsd:field xpath="associationEnd_member"/>
          </xsd:keyref>
          <!-- RELACIONES AssociatioEnd - Association -->
          <xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
               <xsd:selector xpath="Association"/>
               <xsd:field xpath="Association_member"/>
          </xsd:keyref>
     </xsd:element>
     <!--***************************** DEFINICION DE TIPOS SIMPLES *****************************-->
     <!-- TIPO ENUMERADO AGGREGATIONTYPE -->
     <xsd:simpleType name="AggregationType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="none"/>
               <xsd:enumeration value="aggregate"/>
               <xsd:enumeration value="composite"/>
          </xsd:restriction>
     </xsd:simpleType>
     <!-- TIPO ENUMERADO SCOPETYPE -->
     <xsd:simpleType name="ScopeType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="instance"/>
               <xsd:enumeration value="classifier"/>
          </xsd:restriction>
     </xsd:simpleType>
     <!-- TIPO ENUMERADO MULTIPLICITYTYPE -->
     <xsd:simpleType name="MultiplicityType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="0..1"/>
               <xsd:enumeration value="1..1"/>
               <xsd:enumeration value="0..N"/>
               <xsd:enumeration value="1..N"/>
          </xsd:restriction>
     </xsd:simpleType>
     <!-- TIPO ENUMERADO CHANGEABLETYPE -->
     <xsd:simpleType name="ChangeableType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="none"/>
               <xsd:enumeration value="frozen"/>
               <xsd:enumeration value="add_only"/>
          </xsd:restriction>
     </xsd:simpleType>
     <!--**************************** DEFINICION DE TIPOS COMPLEJOS **********************************************-->
     <!-- TIPO COMPLEJO MODELELEMENT -->
     <xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
          <xsd:sequence>
               <xsd:element name="nombre" type="xsd:string"/>
               <!-- Subelementos para representar sus relaciones -->
               <xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
               <xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
          </xsd:sequence>
     </xsd:complexType>
     <!-- TIPO COMPLEJO DEPENDENCY -->
     <xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
          <xsd:complexContent>
               <xsd:extension base="ModelElement">
                    <xsd:sequence>
                         <xsd:element name="description" type="xsd:string"/>
                         <!-- Subelementos para representar sus relaciones -->
                         <xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                         <xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:extension>
          </xsd:complexContent>
     </xsd:complexType>
     <!-- TIPO COMPLEJO GENERALIZATION -->
     <xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
          <xsd:complexContent>
               <xsd:extension base="ModelElement">
                    <xsd:sequence>
                         <xsd:element name="discriminator" type="xsd:string"/>
                         <!-- Subelementos para representar sus relaciones -->
                         <xsd:element name="subtype" type="xsd:string"/>
                         <xsd:element name="supertype" type="xsd:string"/>
                         <!-- Al quitar minOccurs y maxOccurs obligamos a que siempre haya un (Y SOLO UNO)
                              subelemento 'subtype' y 'supertype' -->
                    </xsd:sequence>
               </xsd:extension>
          </xsd:complexContent>
     </xsd:complexType>
     <!-- TIPO COMPLEJO NAMESPACE -->
     <xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
          <xsd:complexContent>
               <xsd:extension base="ModelElement"/>
          </xsd:complexContent>
     </xsd:complexType>
     <!-- TIPO COMPLEJO GENERALIZABLEELEMENT -->
     <xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
          <xsd:complexContent>
               <xsd:extension base="NameSpace">
                    <xsd:sequence>
                         <xsd:element name="isRoot" type="xsd:boolean"/>
                         <xsd:element name="isLeaf" type="xsd:boolean"/>
                         <xsd:element name="isAbstract" type="xsd:boolean"/>
                         <!-- Subelementos para representar sus relaciones -->
                         <xsd:element name="generalization" type="xsd:string"/>
                         <xsd:element name="specification" type="xsd:string"/>          
                    </xsd:sequence>
               </xsd:extension>
          </xsd:complexContent>
     </xsd:complexType>
     <!-- TIPO COMPLEJO: ASSOCIATIONEND -->
     <xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
     <xsd:complexContent>
          <xsd:extension base="ModelElement">
               <xsd:sequence>
                    <xsd:element name="IsNavigable" type="xsd:boolean"/>
                    <xsd:element name="IsOrdered" type="xsd:boolean"/>
                    <xsd:element name="Aggregation" type="AggregationType"/>
                    <xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
                    <xsd:element name="Changeable" type="ChangeableType"/>
                    <xsd:element name="TargetScope" type="ScopeType"/>
                    <!-- Subelementos para representar las relaciones -->
                    <xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
                    <xsd:element name="Association_member" type="xsd:string"/>
                    <xsd:element name="Type" type="xsd:string"/>
                    <xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
               </xsd:sequence>
          </xsd:extension>
     </xsd:complexContent>          
     </xsd:complexType>
     <!-- TIPO COMPLEJO CLASSIFIER -->
     <xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
          <xsd:complexContent>
               <xsd:restriction base="GeneralizableElement">
                    <xsd:sequence>
                         <!-- Subelementos para representar las relaciones -->
                         <xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                         <xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:restriction>
          </xsd:complexContent>
     </xsd:complexType>
     <!-- TIPO COMPLEJO CLASS -->
     <xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
          <xsd:complexContent>
               <xsd:extension base="Classifier"/>
          </xsd:complexContent>
     </xsd:complexType>
     <!-- TIPO COMPLEJO ATTRIBUTE -->
     <xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
          <xsd:sequence>
               <xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
          </xsd:sequence>
     </xsd:complexType>
     <!-- TIPO COMPLEJO ASSOCIATION -->
     <xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
          <xsd:complexContent>
               <xsd:restriction base="GeneralizableElement">
                    <xsd:sequence>
                         <xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:restriction>
          </xsd:complexContent>
     </xsd:complexType>
</xsd:schema>
and when I try to load it into XMLDB it fails:
SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
ml_schema/Metamodel_Schema_All.xsd"
SQL> set echo on
SQL> connect &1/&[email protected]
Conectado.
SQL> alter session set events='31098 trace name context forever';
Sesi�n modificada.
SQL> begin
2 dbms_xmlschema.registeruri(
3 '&4',
4 '&3',
5 TRUE,TRUE,FALSE,TRUE);
6 end;
7 /
antiguo 3: '&4',
nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
antiguo 4: '&3',
nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
begin
ERROR en l�nea 1:
ORA-31154: invalid XML document
ORA-19202: Se ha producido un error en el procesamiento
LPX-00217: invalid character 0 (\u0000) de XML
ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
ORA-06512: en l�nea 2
it says.
I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
Help!!!
Thanks on advance for spare your time helping us.

Please post this message at:
Forums Home » Oracle Technology Network (OTN) » Products » Database » XML DB

Similar Messages

  • KEY and KEYREFs support on XML DB

    First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
    I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
    I'm worling with the next schema:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
    <!-- En esta version, representaremos las relaciones usando atributos KEYs y KEYREFs
    Ademas, en esta version mapeamos el metamodelo de UML por completo-->
    <!-- En las anotaciones para XML DB usaremos el prefijo MMALL(MetaModelo Completo) -->
    <!--******************** DECLARACION DE LOS ELEMENTOS DEL METAMODELO *********************-->
    <xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
    <xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
    <xsd:sequence>
    <xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
    <xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- Es en este punto donde definiremos las "PRIMARYKEYS"(KEYs) Y "FOREIGNKEYS"(KEYREFs) para simular relaciones -->
    <!-- ************************************************************************************************* *-->
    <!-- RELACIONES ModelElement - Dependency -->
    <xsd:key name="Dependency_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="ModelElement_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="Requirement_FK" refer="Dependency_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="requirement"/>
    </xsd:keyref>
    <xsd:keyref name="Provision_FK" refer="Dependency_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="provision"/>
    </xsd:keyref>
    <xsd:keyref name="Client_FK" refer="ModelElement_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="client"/>
    </xsd:keyref>
    <xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="supplier"/>
    </xsd:keyref>
    <!-- RELACIONES Generalization - GeneralizableElement -->
    <xsd:key name="Generalization_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="subtype"/>
    </xsd:keyref>
    <xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="type"/>
    </xsd:keyref>
    <xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="generalization"/>
    </xsd:keyref>
    <xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="specialization"/>
    </xsd:keyref>
    <!-- RELACIONES Classifier - AssociationEnd -->
    <xsd:key name="Classifier_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="AssociationEnd_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="associationEnd"/>
    </xsd:keyref>
    <xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="participant"/>
    </xsd:keyref>
    <xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="type"/>
    </xsd:keyref>
    <xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="specification"/>
    </xsd:keyref>
    <!-- RELACIONES AssociatioEnd - Attribute -->
    <xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Attribute"/>
    <xsd:field xpath="associationEnd_member"/>
    </xsd:keyref>
    <!-- RELACIONES AssociatioEnd - Association -->
    <xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
    <xsd:selector xpath="Association"/>
    <xsd:field xpath="Association_member"/>
    </xsd:keyref>
    </xsd:element>
    <!--***************************** DEFINICION DE TIPOS SIMPLES *****************************-->
    <!-- TIPO ENUMERADO AGGREGATIONTYPE -->
    <xsd:simpleType name="AggregationType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="none"/>
    <xsd:enumeration value="aggregate"/>
    <xsd:enumeration value="composite"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO SCOPETYPE -->
    <xsd:simpleType name="ScopeType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="instance"/>
    <xsd:enumeration value="classifier"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO MULTIPLICITYTYPE -->
    <xsd:simpleType name="MultiplicityType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="0..1"/>
    <xsd:enumeration value="1..1"/>
    <xsd:enumeration value="0..N"/>
    <xsd:enumeration value="1..N"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO CHANGEABLETYPE -->
    <xsd:simpleType name="ChangeableType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="none"/>
    <xsd:enumeration value="frozen"/>
    <xsd:enumeration value="add_only"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!--**************************** DEFINICION DE TIPOS COMPLEJOS **********************************************-->
    <!-- TIPO COMPLEJO MODELELEMENT -->
    <xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
    <xsd:sequence>
    <xsd:element name="nombre" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- TIPO COMPLEJO DEPENDENCY -->
    <xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="description" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO GENERALIZATION -->
    <xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="discriminator" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="subtype" type="xsd:string"/>
    <xsd:element name="supertype" type="xsd:string"/>
    <!-- Al quitar minOccurs y maxOccurs obligamos a que siempre haya un (Y SOLO UNO)
    subelemento 'subtype' y 'supertype' -->
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO NAMESPACE -->
    <xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement"/>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO GENERALIZABLEELEMENT -->
    <xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
    <xsd:complexContent>
    <xsd:extension base="NameSpace">
    <xsd:sequence>
    <xsd:element name="isRoot" type="xsd:boolean"/>
    <xsd:element name="isLeaf" type="xsd:boolean"/>
    <xsd:element name="isAbstract" type="xsd:boolean"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="generalization" type="xsd:string"/>
    <xsd:element name="specification" type="xsd:string"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO: ASSOCIATIONEND -->
    <xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="IsNavigable" type="xsd:boolean"/>
    <xsd:element name="IsOrdered" type="xsd:boolean"/>
    <xsd:element name="Aggregation" type="AggregationType"/>
    <xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
    <xsd:element name="Changeable" type="ChangeableType"/>
    <xsd:element name="TargetScope" type="ScopeType"/>
    <!-- Subelementos para representar las relaciones -->
    <xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Association_member" type="xsd:string"/>
    <xsd:element name="Type" type="xsd:string"/>
    <xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO CLASSIFIER -->
    <xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
    <xsd:complexContent>
    <xsd:restriction base="GeneralizableElement">
    <xsd:sequence>
    <!-- Subelementos para representar las relaciones -->
    <xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:restriction>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO CLASS -->
    <xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
    <xsd:complexContent>
    <xsd:extension base="Classifier"/>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO ATTRIBUTE -->
    <xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
    <xsd:sequence>
    <xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- TIPO COMPLEJO ASSOCIATION -->
    <xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
    <xsd:complexContent>
    <xsd:restriction base="GeneralizableElement">
    <xsd:sequence>
    <xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:restriction>
    </xsd:complexContent>
    </xsd:complexType>
    </xsd:schema>
    and when I try to load it into XMLDB it fails:
    SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
    ml_schema/Metamodel_Schema_All.xsd"
    SQL> set echo on
    SQL> connect &1/&[email protected]
    Conectado.
    SQL> alter session set events='31098 trace name context forever';
    Sesi�n modificada.
    SQL> begin
    2 dbms_xmlschema.registeruri(
    3 '&4',
    4 '&3',
    5 TRUE,TRUE,FALSE,TRUE);
    6 end;
    7 /
    antiguo 3: '&4',
    nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
    antiguo 4: '&3',
    nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
    begin
    ERROR en l�nea 1:
    ORA-31154: invalid XML document
    ORA-19202: Se ha producido un error en el procesamiento
    LPX-00217: invalid character 0 (\u0000) de XML
    ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
    ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
    ORA-06512: en l�nea 2
    it says.
    I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
    Help!!!
    Thanks on advance for spare your time helping us.

    Looks like known bug 2831302 fixed in (forthcoming) 10g release. In the mean time I would simply comment the key/keyref out of the schema

  • Nls support with oracle xml parser in java

    I'm using The JAXP interface to manipulate xml with xsl. the implementation that I use is Oracle xml parser.
    My xml contains a lot of hebrew chars, and in the result stream each char translated into 5-6 chars, which makes the result to be 5-6 times bigger than it suppose to be, and harder for me to debug my application.
    The client's browser shows the results well.
    How can I make the transformator to transform the hebrew chars to hebrew char istead of longer and not readable string ?

    Oracle XML Team wrote:
    : Stephen Flinter (guest) wrote:
    : : Environment: WinNT 4.0/SP4, Apache 1.3.6, JServ 1.0, Oracle
    : 8.1.5
    : : I have downloaded the new Java v2 XML Parser (2.0.2), and
    have
    : : replaced the wrapper.classpath entry in my jserv.properties
    : file
    : : with the path to the new parser.
    : : When I rerun the "Employee Page" demo, I get the following
    : : exception message:
    : : [15/09/1999 11:02:22:974 GMT] java.lang.NoSuchMethodError:
    : : oracle.xml.parser.v2.XSLProcessor: method
    : : processXSL
    : (Loracle/xml/parser/v2/XSLStylesheet;Loracle/xml/parser
    : : /v2/XMLDocument;)Lorg/w3c/dom/DocumentFragment; not found
    : : at oracle.xml.xsql.XSLHelper.process(XSLHelper.java:34)
    : : at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java,
    : : Compiled Code)
    : : at
    : : javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
    : : at
    : : javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
    : : at
    : : org.apache.jserv.JServConnection.processRequest
    : (JServConnection.j
    : : ava)
    : : at
    : : org.apache.jserv.JServConnection.run(JServConnection.java)
    : : at java.lang.Thread.run(Thread.java:479)
    : : This demo was works fine with the parser shipped with the
    : : xsql_servlet download.
    : : Regards,
    : : Steve
    : Version 2.0.2 uses the August XSLT WD which is incompatible
    with
    : the April WD on which our previous releases including the demos
    : were based.
    : Oracle XML Team
    : http://technet.oracle.com
    : Oracle Technology Network
    Hi,
    Can someone from the Oracle XML Team point us to a fix so we can
    continue our testing???
    Steve...
    null

  • What are the API's and OS Supported by Oracle TimesTen

    1.) What are all the API supported by oracle TimesTen?
    is the below are correct and whether other than this is there any other API supports oracle TimesTen
    JDBC,
    ODBC,
    OLAP,
    ADO.net,
    C++...............
    2.) What are the Platform supports?
    is the below are correct and whether other than this is there any other OS supports oracle TimesTen
    Linux x86-32 and x86-64:
    Oracle Linux 4 and 5
    Red Hat Enterprise Linux 4 and 5
    SUSE Enterprise Server 10 and 11
    MontaVista Linux CGE 5.0 and 6.0
    Asianux 3.0
    Microsoft Windows x86-32 and x86-64:
    Windows XP, Windows Vista, Windows Server 2003, Windows Server 2003 Release 2, Windows Server 2008, Windows 7
    Solaris SPARC 64-bit:
    Oracle Solaris 10
    Solaris x86-64:
    Oracle Solaris 10
    IBM AIX 64-bit:
    AIX 6.1 and 7.1
    Solaris SPARC 32-bit (client only):
    Oracle Solaris 10
    IBM AIX 32-bit (client only):
    AIX 6.1 and 7.1
    3.) What is the latest Version in Oracle TimesTen?
    4.) Maximum number of rows in a table.     2 Power 28 = 268,435,256 for 32 Bit     / (2 power 31-1) = 2,147,483,647 for 64 Bit
    if the Row value exceeds more than the specified value what will happen ? whether we need to have multiple tables
    Say TableA reaches 268,435,256 values and if few more rows are added then the value can be kept in new table TableB and so on..... or how?
    Thanks

    Dear 933663,
    1. What are all the API supported by oracle TimesTen?
    JDBC
    ODBC
    ADO.net
    OCI
    PRO*C
    +
    PL/SQL
    SQL
    2. What are the Platform supports?
    TimesTen 11.2.2.2.0 supports - Windows (32-bit, 64-bit), Linux x86 (32-bit, 64-bit), Solaris Sparc (64-bit), Solaris x86 (64-bit), IBM AIX Power (64-bit) (http://www.oracle.com/technetwork/products/timesten/downloads/index.html)
    The detailed information I could find only in 11.2.1 documentation (http://docs.oracle.com/cd/E18283_01/timesten.112/e13063/install.htm):
    Microsoft Windows 2000, Windows XP, Windows Vista and Windows Server 2003 and 2008 for Intel IA-32 and EM64T and AMD64 CPUs.
    Asianux 2.0 and 3.0 for Intel IA-32 and EM64T and AMD64 CPUs.
    SuSE LINUX Enterprise Server 10 for Intel IA-32 and EM64T and AMD64 CPUs.
    SuSE LINUX Enterprise Server 10 for Itanium2 CPUs
    Solaris 9 and 10 for UltraSparc CPUs
    Solaris 10 for AMD64 CPUs
    Red Hat Enterprise Linux 4 and 5 for Intel Itanium2 CPUs.
    Red Hat Enterprise Linux 4 and 5 for Intel IA-32 and EM64T and AMD64 CPUs.
    Oracle Enterprise Linux 4 and 5 for Intel IA-32 and EM64T and AMD64 CPUs.
    MontaVista Linux Carrier Grade Edition Release 4.0 and 5.0 for Intel IA-32, EM64T and AMD64 CPUs.
    HP-UX 11i v2 and 11iv3 for PA-RISC
    HP-UX 11i v2 and 11iv3 for Itanium2
    AIX 5L 5.3 and 6.1 for POWER CPUs
    3.) What is the latest Version in Oracle TimesTen?
    11.2.2.2.0 (http://www.oracle.com/technetwork/products/timesten/downloads/index.html)
    4) Maximum number of rows in a table. 2 Power 28 = 268,435,256 for 32 Bit / (2 power 31-1) = 2,147,483,647 for 64 Bit
    Actually, I couldn't find any information about rows limits for TimesTen tables and I've never faced with this problem.
    Best regards,
    Gennady

  • Buy spare keys and plastic support

    Hey there
    Had an accident and ended up with a loose key ( "Y" )  and its broken plastic support. How do I go about getting a replacement key and support ?
    Appreciate your advise
    Thanks
    Rodney

    Sorry to hear about your system problems. I can't help you any but if you do not find help here try posting you question at the L.A. Final Cut Users Group at http://www.lafcpug.org/ These are the guys and gals who edit feature films and large scale videos. I have not posted there but from lurking they seem to be very willing to help and you do not have to be a member to post in their forum.
    Surely one of them has heard of this and may have a work around.
    Wish I could help more.
    Best of luck

  • FOR ORACLE XML TEAM -- XML TOOLS BUG FIXING POLICY/RESPONSE TIME/RELEASE SCHEDULE

    Hi,
    The release of Oracle XML tools and utilities by Oracle XML team is a significant milestone and is definitely appreciated. However, as part of a large organization, some factors need to be clarified before using these utilities in production softwares.
    I have noticed that XML parsers and other utilities are now coming as part of other softwares like JDeveloper etc. Following are my questions to the Oracle XML team and urgent and prompt reply will be greatly appreciated.
    1. What is the XML tools support policy. Is it only OTN? Can we buy support? Are these utilities supported if large organizations have corporate server licenses. I have read at the XML site the XDK is fully and freely supported by Oracle Word Wide support. What does this mean?
    2. What is the release schedule for the XML tools?
    3. What is the response time?
    Once again, your help and prompt reply will be appreciated.
    Thanks.

    As you noted many of the Oracle XDK components are production. This means that if your company has an Oracle Server Support contract you will get the corresponding level of support for the production XDK components.
    If you don't have one, then OTN is your support resource. We will also have standalone support agreements in the future which you can purchase through the Oracle Store. The response time would be the same as for the server.
    There is not a specific release schedule for components on OTN as they have different development schedules.
    Oracle XML Team
    null

  • Installing support for Oracle Designer Objects in an existing repository

    We have been using SCM to store Forms and other files
    for our development work.
    Now I want to use Repository Reports in the Repository
    Object Navigator, this requires me to install support
    for Oracle Designer Objects.
    Can I use the Repository Administration Utility and
    Install support for Oracle Designer Objects
    without effecting the existing repository data?
    (I've tried metalink but keep getting TCP Error
    while logging the TAR).
    Cheers
    Sam

    How can i install oracle designer and prepare the repository at first on my personal my pc

  • "Oracle xml Database" INVALID

    Hi,
    when i executed the following query:
    SELECT COMP_NAME, STATUS
    FROM DBA_SERVER_REGISTRY;
    i got all the objects status as VALID except that
    "ORACLE XML Database" was INVALID
    Can someone help me to make this "ORACLE XML Database" as VALID.
    Thanks,
    Philip.

    HI Frank,
    now what i did was i actually ran catpatch.sql and utlrp.sql after i did startup migrate.
    and when i did
    SELECT COMP_NAME, STATUS
    FROM DBA_SERVER_REGISTRY;
    i got all objects as valid, but i dont see "Oracle XML Database" anymore.
    so now i suppose i cannot reinstall, but actually do a fresh install. and the following are the steps for a fresh install in the documentation
    Installing a New Oracle XML DB Manually Without Database Configuration Assistant
    After the database installation, you must run the following SQL scripts in rdbms/admin connecting to SYS to install Oracle XML DB after creating a new tablespace for Oracle XML DB repository. Here is the syntax for this:
    catqm.sql <XDB_password> <XDB_TS_NAME> <TEMP_TS_NAME>
    #Create the tables and views needed to run XML DB
    For example:
    catqm.sql change_on_install XDB TEMP
    Reconnect to SYS again and run the following:
    catxdbj.sql #Load xdb java library
    Note:
    Make sure that the database is started with Oracle9i release 2 (9.2.0) compatibility or higher, and Java Virtual Machine (JVM) is installed.
    Postinstallation
    After the manual installation, carry out these tasks:
    1.     Add the following dispatcher entry to the init.ora file:
    dispatchers="(PROTOCOL=TCP) (SERVICE=<sid>XDB)"
    2.     Restart the database and listener to enable Oracle XML DB protocol access.
    3.     To allow for unauthenticated access to your Oracle XML DB repository data through HTTP, you must also unlock the ANONYMOUS user account.
    is this right. can u tell me what i should do please.
    Thanks,
    Philip.

  • Does Oracle XML parser support scripts?

    I've tried using scripts in my XSL which I parse with Oracle XML parser v2. If the function does not exist, I get error. But if the function exists, I get nothing at all on the output! Not even simple function that only returns a string.
    I also have the same problems with <xsl:eval>.
    Thank you for reading this,
    David.

    We fully support the XSLT 1.0 Recommendation.
    <xsl:eval> and <xsl:script>
    are not features of the XSLT standard.

  • Fatal Error and NullPointerException in Oracle XML Transformer

    Hi,
    I'm building a dom tree in memory with oracle xml parser. Then I transform the dom document into a string to send xml to the client. But I get an fatal error on calling transform.
    I don't know what could be the problem, because apache and weblogic parser works, an when I create a dom document with org.w3c.dom elements and statements then the xml document can't be invalid,
    because the document implementation would throw an exception if wrong nodes or something like this should be inserted...
    I'm using oracle xml parser 9.2.0.4 for java, bea weblogic 7.0 and win2k.
    Thanks for help.
    XSL-1900: (Fatal Error) An internal error condition occurred.
    javax.xml.transform.TransformerException: XSL-1900: (Fatal Error) An internal error condition occurred.
    at oracle.xml.jaxp.JXTransformer.reportException(JXTransformer.java:681)
    at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:309)
    java.lang.NullPointerException
    at oracle.xml.parser.v2.XSLSAXPrintDriver.printAttributes(XSLSAXPrintDriver.java:394)
    at oracle.xml.parser.v2.XSLSAXPrintDriver.startElement(XSLSAXPrintDriver.java:322)
    at oracle.xml.parser.v2.XMLElement.reportSAXEvents(XMLElement.java:993)
    at oracle.xml.parser.v2.XMLNode.reportChildSAXEvents(XMLNode.java:1014)
    at oracle.xml.parser.v2.XMLDocument.reportSAXEvents(XMLDocument.java:942)
    at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:294)

    Hi,
    I'm having that problem to:
    I'm getting the following exception
    javax.xml.transform.TransformerException: XSL-1900: (Fatal Error) An internal error condition occurred.
         at oracle.xml.jaxp.JXTransformer.reportException(JXTransformer.java:723)
         at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:340)
         at com.ac.mqif.control.Handler.handleLong(Handler.java:835)
         at com.ac.mqif.control.Handler.run(Handler.java:951)
    Caused by: java.lang.NullPointerException
         at oracle.xml.parser.v2.XPathStep.getSelectedNodes(XPathStep.java:380)
         at oracle.xml.parser.v2.PathExpr.getValue(XSLNodeSetExpr.java:483)
         at oracle.xml.parser.v2.XSLExprBase.getStringValue(XSLExprBase.java:363)
         at oracle.xml.parser.v2.XSLValueOf.processAction(XSLValueOf.java:99)
         at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:367)
         at oracle.xml.parser.v2.XSLTemplate.processAction(XSLTemplate.java:199)
         at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:214)
         at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:207)
         at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:207)
         at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:120)
         at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:367)
         at oracle.xml.parser.v2.XSLTemplate.processAction(XSLTemplate.java:199)
         at oracle.xml.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:471)
         at oracle.xml.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:448)
         at oracle.xml.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:246)
         at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:327)
         ... 2 more
    when using a stylesheet which has a template match condition of more than 1600 characters.
    The second thing is that the Oracle XML transformer is
    NOT threadsafe. I was using several threads using different templates to transform an incoming XML simultaneously but was ALWAYS getting internal XSL errors
    and Nullpointer Exceptions. I solved this by synchronizing the transformation, but I don't like it.
    I'm using the following versions on Windows XP:
    Oracle IDE: 9.0.3.10.35
    Business Components Version: 9.0.3.10.7
    SCM Support Version: 9.0.3.9.4
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
    Thanx,
    Ellcrys

  • XML Parsing in Java Stored Proc--Oracle XML Support Installation?

    I am working with a third party product that is having difficulty running a java stored proc that is parsing a supplied XML file. The proc basically looks like:
    import java.io.IOException;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.FactoryConfigurationError;
    import javax.xml.parsers.ParserConfigurationException;
    import org.w3c.dom.Document;
    import org.xml.sax.SAXException;
    InputStream is = getXMLAsInputStream(xml);
    try {
    DocumentBuilderFactory factory =
    DocumentBuilderFactory.newInstance();
    DocumentBuilder builder = factory.newDocumentBuilder();
    Document document = builder.parse( is );
    ... parse the document ....
    catch (FactoryConfigurationError e) {
    // unable to get a document builder factory
    We are running on 9.2.0.6, HP-UX 64-bit. At first, when we would attempt to run the proc, a database hang would occur; now after attempting to install using loadjava jars for xerces2.6: ORA-29532: Java call terminated by uncaught Java exception:
    javax.xml.parsers.FactoryConfigurationError: Provider
    org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found)
    The vendor says that the errors we are getting when running are not due to any dependency on xerces or jre1.4, and that we need to "install Oracle XML support", but I'm not certain what this means (I cannot find any documentation on what to install). I believe that there are jars that need to be loaded into the database to support the XML parsing, as jre1.3 does not include built-in XML support, and Oracle 9.2.0.6 uses jre1.3.
    So...does anyone have any thoughts as to how to resolve the missing references? Is there a way to "install Oracle XML support", or is it to install the necessary jars?
    Thanks,
    Candi

    Candi,
    The following resources should be of help:
    Oracle9i Database Release 2 (9.2) Documentation Library
    In particular, check out the following:
    Java Developer's Guide
    Java Stored Procedures Developer's Guide
    XML API Reference - XDK and Oracle XML DB
    XML Database Developer's Guide - Oracle XML DB
    XML Developer's Kits Guide - XDK
    If that doesn't help, then try the following:
    OracleJVM and Java Stored Procedures
    XML Technology Center
    Good Luck,
    Avi.

  • XML support in Oracle 8i

    Hi,
    I have a requirement of storing XML documents in the Oracle
    database. As Oracle claims support for XML in Oracle 8i, I would
    be thankful if the following questions could be answered.
    There will be around 15000 or more XML documents generated
    annually, each of around 200 pages . Various views of the same
    XML instance will be shown to different customers depending on
    their preferences. All views will be generated dynamically and
    the results will be sent as HTML pages to the client or XML
    instances which will then be manipulated and shown as required
    on the clients machine.
    Please bear with me in case a few questions are naive
    Questions :
    1) Does Oracle 8i propose to have XML as a new datatype
    2) Does a document descriptor mean the mapping of the XML
    elements to certain columns in an Oracle table? Does it have
    anything to do with the DTD? Will an XML instance be mapped to a
    single table only or across multiple tables in a master-detail
    relationship as the heirarchy in the instance gets too complex ?
    3) How will the ConText cartridge be able to identify XML
    documents? How will the queries be written to enable 'element-
    level' searching?
    4)What is iFS , especially in relation to XML storage?
    Regards,
    Kedar&#137;
    null

    Kedar Sadekar (guest) wrote:
    : 1) Does Oracle 8i propose to have XML as a new datatype
    Not at this time.
    : 2) Does a document descriptor mean the mapping of the XML
    : elements to certain columns in an Oracle table? Does it have
    : anything to do with the DTD? Will an XML instance be mapped to
    :a single table only or across multiple tables in a master-detail
    : relationship as the heirarchy in the instance gets too complex?
    A Document Descriptor is basicly a mapping between a DTD and the
    tables and columns in the RDBMS. More that one table can be
    mapped to.
    : 3) How will the ConText cartridge be able to identify XML
    : documents? How will the queries be written to enable 'element-
    : level' searching?
    Context, now interMedia Text, does not 'identify' XML documents
    per se, but can index colums with imbedded XML and search the
    contents between specified tags.
    : 4)What is iFS , especially in relation to XML storage?
    Check out http://www.oracle.com/xml/documents/xml_twp/ for a
    complete description.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • [svn] 3663: Dita xml and xslt support for SkinStates

    Revision: 3663
    Author: [email protected]
    Date: 2008-10-15 13:04:27 -0700 (Wed, 15 Oct 2008)
    Log Message:
    Dita xml and xslt support for SkinStates
    Bugs: SDK-17166
    QA: Yes
    Doc: No
    Tests: checkintests
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17166
    Modified Paths:
    flex/sdk/trunk/asdoc/templates/class-parts.xslt
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

    http://docs.oracle.com/javaee/1.4/tutorial/doc/JAXPXSLT6.html

  • Does Oracle XML Parser support double byte charset?

    Hi,
    Does Oracle XML Parser support double byte characters such as Korean or Chinese? If so, please tell me what version and how to construct xml/xsl files (...encoding="???")?
    Thanks for any help,
    Tuan

    Hi Raymond,
    Thank you for your help. It worked when I running in JDeveloper with your posted code. However, when I tried in my real application, it won't work.
    The problem is for localization purposes, my application using some texts display in browsers are saved in Unicode file. Later, application runs and depends on languages setting in browsers, with JavaServlet retrieves those texts and saves in formated xml StringBuffer. Then, using existed XSL Stylesheet file and OracleXMLParser to generate an output HTML.
    It has worked fine with English, France or others (single byte characters), but it can't
    for double bytes character such as Korean or Chinese. I also tried different charset in xml file.
    The following is one of returning errors:
    -- oracle.xml.parser.v2.XSLException: XSL-1004: Error while parsing input XML document (<Line 1, Column 552>: XML-0221: (Fatal Error) Invalid char in text.)
    I run this app in win2000/IIS with ServletExec3.0, JDK1.2.2 and OracleXMLParser v2.0.2.10
    Thank you for any helps,
    Tuan
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Raymond Hayes Jr ([email protected]):
    Nothing fancy 'cause I'm half asleep but I used your xml/xsl and it seemed to work. No errors anyway. This is what I put together in JDeveloper 3.2
    package demo;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    import java.net.*;
    import java.util.*;
    import oracle.xml.parser.v2.*;
    public class CuriosityKilledTheCat extends HttpServlet {
    * Initialize global variables
    public void init(ServletConfig config) throws ServletException {
    super.init(config);
    * Service the request
    public void service(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
    try
    XSLStylesheet xsl = new XSLStylesheet( new URL ("file:///c:\\temp\\input.xsl") , null );
    XSLProcessor xp = new XSLProcessor();
    XMLDocument xd = new XMLDocument ();
    XMLDocumentFragment xf = new XMLDocumentFragment();
    xf = xp.processXSL ( xsl , new URL ( "file:///c:\\temp\\input.xml") , null );
    System.out.println ( "here" );
    xd.appendChild( xf );
    xd.print ( response.getOutputStream() );
    catch ( Exception e )
    System.out.println ( e.getMessage() );
    * Get Servlet information
    * @return java.lang.String
    public String getServletInfo() {
    return "demo.CuriosityKilledTheCat Information";
    }<HR></BLOCKQUOTE>
    null

  • Does Oracle XML Parser support Content Validation

    Hi there,
    Could someone out there give me a hint on whether the Oracle XML Parser has the capability of handling Content Validation? If yes, what's the mechanism behind it?
    From my understanding of the Oracle XML Parser, even with the validating mode turned on, the parser only validates the XML data against the DTD (if any), which involves checking whether or not the attribute names and element tags are legal, whether nested elements belong to where they are, and so on. But I dont see any Content Validation. And my guess is that this feature, namely Content Validation, is simply not supported in the current version of the Oracle XML Parser. Am I right?
    Any suggestion would be greatly appreciated. Thanks.
    ---Denali
    null

    Hi there,
    Could someone out there give me a hint on whether the Oracle XML Parser has the capability of handling Content Validation? If yes, what's the mechanism behind it?
    From my understanding of the Oracle XML Parser, even with the validating mode turned on, the parser only validates the XML data against the DTD (if any), which involves checking whether or not the attribute names and element tags are legal, whether nested elements belong to where they are, and so on. But I dont see any Content Validation. And my guess is that this feature, namely Content Validation, is simply not supported in the current version of the Oracle XML Parser. Am I right?
    Any suggestion would be greatly appreciated. Thanks.
    ---Denali
    null

Maybe you are looking for

  • Will apple repair my iphone with a different housing?

    Just wondering I changed the housing on my iPhone but I still have the original housing. My phone's also out of warranty but would they still fix my phone? just wondering?

  • ITunes 11.2.1 is unable to change metadata

    After this recent update of iTunes to version 11.2.1 I'm no longer able to change metadata of any MP3 file without that the spinning ball takes an infinity spinning tour. I have to kill the iTunes process. Befor this update I changed mass of files th

  • Why does the parameter of the paintComponent method have....?

    Why does the parameter of the paintComponent method have type Graphics and not Graphics2D?

  • Ultra 5 Hangs During Boot

    My Ultra 5 hangs during boot at the following point.... setting default ipv4 interface...... I have tried resetting my router, unplugging the network cable, and nothing seems to work. John

  • Error 20003 LV 7.1

    Hi I am using a USB DAQ 6008 for continuous reading of some voltage values from a circuit. I configured an AI voltage task for 2 input channels, one of which was then filtered and the result displayed. Everything worked fine upto this point. But when