SchemaLocation for a XSD file within a JAR

Hello,
What kind of shemaLocation should I use in my XML files to reference XSD files located in a JAR so that JDeveloper find it and thus enable code assist feature?
Note: The JAR in question is in the project library (not necessarily in WEB-INF/lib at the time of development)
Regards,
Simon Lessard

hi Simon Lessard
If you select "Tools" > "Preferences..." > "XML Schemas", using JDeveloper 10.1.3.2, several "JDeveloper Schemas for XML Editing" have been defined, some inside JAR or ZIP files.
For example for the ".wsdl" extension like this:
jar:file:/D:/oracle/jdevstudio10132/jdev/lib/jdev.jar!/oracle/jdevimpl/webservices/wsdl/wsdl.xsd
Maybe you can define something similar in "User Schemas for XML Editing" in the same dialog.
Is this what you are looking for?
success
Jan Vervecken

Similar Messages

  • Run a jar-File and modify a file within this jar-File

    I am running the jar-File, which contains my compiled java files etc.
    The program has a config part, which is saved in xml file.
    This xml file is in the same directory like the class files.
    All theses files are zipped as jar-File.
    Well, I am running the jar file.
    - But how do I open and save the xml file ?
    - Is that possible ?
    - How difficult ist that ?

    I tried to do this some time ago and found out the hard way that you can't, just as DrClap just told you. I would have taken his work for it anyway, but for what it's worth, I thought I'd mention that you're not alone. In my case I wanted to be cute and keep my properties all together within the .jar; thought it'd be cleaner that way. Ended up just creating the more typical class_name-props file in my home directory. Is this what you had in mind?
    ~Bill

  • Access a data file within a jar package

    hello, everyone
    I got a problem in locating a data file packaged in jar file.
    For example, in foo.jar there is a data file with the directory path "d1/d2/data.log". In the command line, I want to access that data file by making it as an input to the Main class which will load data.log at runtime. However, it reported exception of "no such file or directory". In the command line, I input:
    java -classpath foo.jar d1.d2.Main d1/d2/data.log
    any suggestion?
    Thanks
    Chinyi

    I don't understand what you're trying to do by including d1/d2/data.log in the commandline? It appears to be extraneous and invalid.
    Assuming:
    that the class you want to execute is Main.class in foo.jar, and that its path in the jar is di/d2, and
    that Main uses d1.d2.data.log when it access this file, it should work.

  • Shortcut for selecting multiple files within folders

    I'm archiving a load of work on to CD and deleting the files off of my server but keeping the folders on there for reference.
    Currently, I am having to SHIFT + click / COMMAND + click &drag to select these files and it is taking me forever.
    Is there a keyboard shortcut that allows me to select all files within folders rather than just a select all which will select the folders aswell?

    I would switch to list view, then click on the "Kind" column which will group the folders together.  Now you can click and drag to select a large range of files, excluding the folders, or you can click on the first file, the Shift click on the last file to select a large range of files.  At most you would need to do this twice.  Once for files listed above folders, and once for files listed below folders.
    If you want to use the Terminal, there are powerful Unix commands that can do this, however, that same power when misused can wipe out your disk :-)

  • Accessing a Jar file within my jar...

    Hi,
    I've got a JDBC Jar file that I wish to include in my Jar package, but I'm unsure how to do this...
    I'm using ant to compile my code & package it up into the Jar, & I can get it to compile fine, and package everything up fine (including the JDBC jar), but when I go to run the app I get an error
    (No suitable driver).
    My app works fine without being Jar'ed up.
    I'm guessing that I need to set the classpath to reference the JDBC jar file in my jar... but I'm unsure how to do this.
    Any help would be greatly appreciated.

    package what you thirdpart jar file and your jar file to one jar file..
    it will run ok.
    maybe the below tool can help you.
    a tool named JavaJar(written by java) can compress and decompress jar,war, ear and.zip...
    may download from http://www.qwerks.com/download/4114/JavaJar.zip
    the tool is very verygood tool.
    but the homepage(www.pivotonic.com) of JavaJar cannot be accessed.
    it is funny.
    good lucky.

  • Accessing Files within a jar - Problems.

    So i have the following code in my program and when i goto run the jar file i get NPE's:
    URL fileURL = getClass().getResource("resources/cfg/portlist");
                    BufferedReader portFileBuff = new BufferedReader(new InputStreamReader(fileURL.openStream()));Now my jar file has resources/cfg/portlist in it and i cannot figure out why this isnt working for me when it works just fine in another program i have. I feel im missing out on some framing issue. Any Suggestions?

    Hello,
    I have the same problem when trying to log "log4j" from a jar....
    Here is my code that generate the error:
    static{
              DOMConfigurator.configure("config"+File.separator+"log4j.xml");
    Obviously, the file log4j is in my jar in the directory config.
    This code works well outside the jar.
    It semms that I got also the same problem on library that are in my jar under the directory "lib"....
    Any idea..?

  • Problem opening a zip file within a jar file

    Hi,
    I have a jar file in a tomcat web server. The jar file includes a zip file which I've been trying to open with the following sentences:
    SpellDictionary dict = null;
    File f = new File(getClass().getResource*("us_US.zip"*).getFile());
    dict = new OpenOfficeSpellDictionary( new ZipFile( f ) );
    I'm getting this exception:
    2007-09-13 15:31:38 java.util.zip.ZipException: No such file or directory
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.<init>(ZipFile.java:203)
    at java.util.zip.ZipFile.<init>(ZipFile.java:84)
    at com.iir.newsAdministration.textEditor.TextEditorSpellChecker.<init>(TextEditorSpellChecker.java:62)
    If I run the application with the builded classes instead of the jar file, it works fine.
    Any ideas about how can I make it work with the jar file?
    Thanks in advance
    Natalie

    File f = new File(getClass().getResource*("us_US.zip"*).getFile());
    This is not going to work.
    What you need to do is create a Jar/ZipFile from your jar, then extract the ZipFile, put that in a temporary location, then open that with another ZipFile object

  • Best practice for how to access a set of wsdl and xsd files

    I've recently beeing poking around with the Oracle ESB, which requires a bunch of wsdl and xsd files from HOME/bpel/system/xmllib. What is the best practice for including these files in a BPEL project? It seems like a bad idea to copy all these files into every project that uses the ESB, especially if there are quite a few consumers of the bus. Is there a way I can reference this directory from the project so that the files can just stay in a common place for all the projects that use them?
    Bret

    Hi,
    I created a project (JDeveloper) with local xsd-files and tried to delete and recreate them in the structure pane with references to a version on the application server. After reopening the project I deployed it successfully to the bpel server. The process is working fine, but in the structure pane there is no information about any of the xsds anymore and the payload in the variables there is an exception (problem building schema).
    How does bpel know where to look for the xsd-files and how does the mapping still work?
    This cannot be the way to do it correctly. Do I have a chance to rework an existing project or do I have to rebuild it from scratch in order to have all the references right?
    Thanks for any clue.
    Bette

  • How do I import any extension file within project in netbeans ?

    Can anybody tell that how can I add any text file or any extension file in netbeans project as I can import image within project and I can use that image when I run jar file..I do not have to move that image where I run my jar file..It will automatically take that image file from jar file...I want this thing same for files...In which I can read and write within project....(I m using netbeans 6.0 and jdk 1.6)
    Thanks...

    Thank you for yr prompt reply.
    May i try to explain once again.. I want a way to store a file (*.txt) in a package called "files" within my project. Now after compiling and making an executable jar of this project i wish to read and write to this *.txt file lying within files package. Though I m able to read this *.txt file ( with the help of getClass().getResourceAsStream() ) but i m unable to make any changes to this file within xxx.jar.
    ex:
    FileWriter fw = new FileWriter("c:/xxx.jar!/files/xyz.txt");
    Do u have ny idea? how can i do this ?
    can u plz suggest the correct forum for netbeans. Thanks once again.

  • Is there a general way to find any type of file IN a JAR ?

    Hi I've written an application that I want to distribute in an executable JAR format. The application runs find when I double click the Jar but ONLY when the config file is outside the Jar, however I want to distribute every thing in the Jar, because I want my program to be self contained.
    I've read a lot of threads, read the Sun tutorial for JARs, but I haven't found a general way to find files within the Jar. Pehaps I should set the Class-Path in the manifest, but from what I've read in Sun Tutorial that seems that it only works for Classes.
    So my question is:
    Is there a general way to find any kind file ( *.txt, *.dat, *.for ) that is not a *.class, within the Jar ? Is that done on the manifest or when creating the Jar ?
    The code for the app that actually works is:
                URL url = getClass().getResource( fileName );
                inputFile = new File( fileName );
                fr = new FileReader( inputFile );
                char[] dat = new char[ (int) inputFile.length() ];
                fr.read( dat );
                sDat = new String( dat );
                fr.close();
                // Parse config.txt
                System.out.print("Reading metaconfig parameters...\n");
                parseFile() ;where filename is "./config.txt".
    I intend later to use a *.dat file wich will contain an object with the necessary data to configur the rest of the program instead of a *.txt file
    Hope you can help me
    Thank you !

    Hi
    For list of vairbles used in the query.
    clik the tab query properties present on the top when u open the query in the change mode.
    when u clik the query peroperteis u geta a screen which shows the sequence of the vairbles used and even u can change the sequence as per ur convenience
    hope it is helpful asssign points if applicable
    thanks
    puneet

  • How to find XSD file? XML to ABAP using XSLT convertor

    Hi Gurus,
    I am trying to convert an XML file to ABAP internal tables using an XSLT transformation. I used the code posted by Durairaj (XSLT program Y_XML_2_ITAB_SIMPLE as mentioned in the link: [Y_XML_2_ITAB_SIMPLE|Parse data to Internal Table;) and the code worked fine.
    My XML file structure is different, and when I try to modify the code for my purposes I got stuck. While changing the XML file strings in the report, I am unable to replace the tag xsi:noNamespaceSchemaLocation="invoice_btm.xsd" correctly. I am also not sure what this file "invoice_btm.xsd" does and where it is stored. When I remove the tag, I get other errors and cannot proceed ahead.
    Can you please advice as to how I should proceed? Also, where can I see the XSD file? can I add a XSD file for my own XML? Or, is there a way to eliminate the need for an XSD file altogether?
    Thanks in advance.
    Regards,
    Shailesh.

    Hi guys,
    Any help would be most helpful. Thanks again,
    Hi guys,
    Any ideas on this issue? Thanks again for your help.
    Hi Naimesh,
    Thanks for the quick reply. I am getting the error "The element abap was expected for the XML-ABAP transformation". I have replaced the following:
    1) "INVOICES_BTM" with the string "ACCOUNT_INFO"
    2) "INVOICE_BTM" with the string "ROOTNODE"
    My XSLT:
    <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
      <xsl:template match="ACCOUNT_INFO">
        <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
          <asx:values>
            <OUTPUT>
              <xsl:for-each select="ROOTNODE">
                <items>
                  <INV_DATE>
                    <xsl:value-of select="INVOICE_HEAD/INVOICE_DATE"/>
                  </INV_DATE>
                  <INV_NO>
                    <xsl:value-of select="INVOICE_HEAD/INVOICE_NUMBER/NUMBER"/>
                  </INV_NO>
                  <INV_EXT>
                    <xsl:value-of select="INVOICE_HEAD/INVOICE_NUMBER/EXTENSION"/>
                  </INV_EXT>
                  <INV_SEQ>
                    <xsl:value-of select="INVOICE_HEAD/INVOICE_NUMBER/SEQUENCE"/>
                  </INV_SEQ>
                </items>
              </xsl:for-each>
            </OUTPUT>
          </asx:values>
        </asx:abap>
      </xsl:template>
    </xsl:transform>
    My XML program:
    TYPES: BEGIN OF stru,
             inv_date(10),
             inv_no(50),
             inv_ext(10),
             inv_seq(10),
           END OF stru.
    DATA: outtab TYPE STANDARD TABLE OF stru .
    DATA: xslt_error  TYPE REF TO cx_xslt_exception,
          xslt_message  TYPE  string .
    DATA: xml_string TYPE string .
    CLEAR xml_string .
    CONCATENATE
    '<?xml version="1.0" encoding="ISO-8859-1"?>'
    '<ACCOUNT_INFO xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ROOTNODE.xsd">'
      '<ROOTNODE>'
        '<INVOICE_HEAD LANGUAGE="DE" DIRECT_DEBIT_QUALIFIER="NO">'
          '<INVOICE_DATE>20040112</INVOICE_DATE>'
          '<INVOICE_NUMBER>'
            '<NUMBER>0306299999</NUMBER>'
            '<EXTENSION>1</EXTENSION>'
            '<SEQUENCE>01</SEQUENCE>'
          '</INVOICE_NUMBER>'
    '</INVOICE_HEAD>'
    '</ROOTNODE>'
    '<ROOTNODE>'
        '<INVOICE_HEAD LANGUAGE="DE" DIRECT_DEBIT_QUALIFIER="NO">'
          '<INVOICE_DATE>20040113</INVOICE_DATE>'
          '<INVOICE_NUMBER>'
            '<NUMBER>0306299888</NUMBER>'
            '<EXTENSION>2</EXTENSION>'
            '<SEQUENCE>02</SEQUENCE>'
          '</INVOICE_NUMBER>'
    '</INVOICE_HEAD>'
    '</ROOTNODE>'
    '</ACCOUNT_INFO>'
    INTO xml_string .
    TRY .
        CALL TRANSFORMATION ('ZH2_XML_TRANS_I1')
          SOURCE XML  xml_string
          RESULT     output = outtab.
      CATCH cx_xslt_exception INTO xslt_error.
        xslt_message = xslt_error->get_text( ).
    ENDTRY.
    break-point.
    Edited by: Shailesh S Kamath on Jan 16, 2012 2:17 PM
    Edited by: Shailesh S Kamath on Jan 30, 2012 2:47 PM

  • Reading a text file in a jar

    I make an application that need to acces to a small text file within a jar file.
    Never used it before, and don't really know how to do it correctly.
    could anyone show me the way to create this small part of code ?
    Thanks.

    Just use the getResource or getResourceAsStream. They exist in the java.lang.Class class (which actually call the current ClassLoader which has the same methods).
    An example follows below, the text file should be added to the root of the jar file.
    Don't forget the first / in the filename, if you do the method will return null..
    ----- Code begin -----
    import java.io.*;
    public class Test
         public static void main(String args[]) throws Exception
              InputStream in = Test.class.getResourceAsStream("/test.txt");
              BufferedReader reader = new BufferedReader(new InputStreamReader(in));
              System.out.println(reader.readLine());
              reader.close();
    ----- Code end -----
    Good luck,
    Daniel

  • XSD file conversion using stylus studio

    Hi All,
    I have created an Xsd file using stylus studio from XML file .I have given the destination properties as XML Schema file name and TYpe etc. But i am unable to see the structure of the table in the sydicator.can any one let me know  what might be the problem? 
    I am able to see repository , language,table,role,port ,description etc in the destination items?
    Please help me out.

    You can create xsd file using java jar files. To do so follow the following steps:
    1) Repository-> export repository schema->save it in java bin file
    2) open cmd-> create xsd file using java jar files
    3) Again in Console upload the path of the xsd file where it is saved.
    4)Open Syndicator->Destination properties->xml schema-> schema file name. Root automatically gets populated.
    I hope I am able to solve your problem
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bf0e8a97-0d01-0010-f0a2-af3b18b7f4eb

  • ORA-19046 with valid xsd-file (on 11.2.0.2)

    Hello Experts,
    I got an xml-file and had to import it into some relational tables. The xsd-files are given.
    I tried: creating ressources for the xsd-files - works; register schema's -> not possible, because of ORA-19046.
    In XMLSpy validating all xsd-files (a total of seven files) is possible - not error found.
    Are there any ideas, how to import the data to some tables? (I don't really need the xml-file in the database)
    Thanky for any help!
    Frank

    XSD-Upload - Part 1/7
    There are seven files - I will post the ORIGINAL Files without oracle annotations:
    vda_root_V1.2.xsd
    -> vda_header_V1.2.xsd
    -> vda_body_V1.2.xsd
    -> ehd_root_V1.40.xsd
    -> keytabs_V1.40.xsd
    -> ehd_header_V1.40.xsd
    -> datentypen_V1.40.xsd
    My Probelm-baby ist datentypen_V1.40.xsd
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!-- =======================================================================
    Typdefinitionen für Schnittstellen,
    Namensraum ist: keins
    =======================================================================-->
    <xs:schema xmlns="urn:ehd/001" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ehd/001" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <!--
         ============================================================
         Dokument/Instanz Identifikation
         ID-Elemente identifizieren eindeutig Objekte. Werte zur Identifizierung werden in
         Attribute EX, RT und RTV eingetragen:
         RT-Attribut (Root) enthält eine eindeutige OID des Objekts (Person/Organisation oder
         Schlüsseltabelle ...)
         EX-Attribut (Extension) enthält die Erweiterung zu OID z.B. fortlaufende Nummer,
         oder GUID bei XML-Dokumenten oder kodierten Wert aus der Schlüsseltabelle.
         RTV-Attribut wird bei Referenzierung auf Schlüsseltabellen verwendet. Hier wird
         Schlüsseltabellenversion eingegeben.
         ============================================================-->
         <xs:element name="id" type="id_typ">
              <xs:annotation>
                   <xs:documentation>enthält eindeutige Instanz-ID</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="id_typ">
              <xs:attribute name="EX" type="xs:string" use="optional"/>
              <xs:attribute name="RT" type="xs:string" use="required"/>
              <xs:attribute name="RTV" type="xs:string" use="optional"/>
         </xs:complexType>
         <xs:complexType name="doc_id_typ">
              <xs:annotation>
                   <xs:documentation>ist dem id_typ identisch</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="id_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <xs:element name="set_id" type="id_typ">
              <xs:annotation>
                   <xs:documentation>enthält eindeutige Instanz-ID, die über alle Versionen und zusammgengehörende Dokumente konstant bleibt</xs:documentation>
              </xs:annotation>
         </xs:element>
         <!--
         ============================================================
         Dokumentenverwaltung
         Die Zuordnung des Dokuments zu einem bestimmten Dokumenttyp wird über
         das Element <document_type_cd> erreicht. Die Dokumente werden mit
         Hilfe der Elemente <id>, <set_id>, <version_nbr> und <document_relationship>
         verwaltet. Mit <document_relationship> wird eine verkettete Liste von Dokumenten
         abgebildet, wie ein Pointer der auf den Vorgänger oder anderes Dokument zeigt.
         ============================================================
         -->
         <!-- ************************ version_nbr_typ ********************************* -->
         <xs:element name="version_nbr" type="version_nbr_typ">
              <xs:annotation>
                   <xs:documentation>Versionnummer des XML-Dokuments</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="version_nbr_typ">
              <xs:attribute name="V" type="xs:nonNegativeInteger" use="required"/>
         </xs:complexType>
         <!-- ************************ document_relationship_typ ********************************* -->
         <xs:element name="document_relationship" type="document_relationship_typ">
              <xs:annotation>
                   <xs:documentation>Beziehung zu anderen Dokumenten ("Anhang", "Ersatz")</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="document_relationship_typ">
              <xs:sequence>
                   <xs:element name="document_relationship.type_cd" type="document_relationship.type_cd_typ">
                        <xs:annotation>
                             <xs:documentation>Art der Dokumentbeziehung ("Anhang", "Ersatz")</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element ref="related_document"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="document_relationship.type_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.101"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ related_document_typ ********************************* -->
         <xs:element name="related_document" type="related_document_typ">
              <xs:annotation>
                   <xs:documentation>Verweis auf das Original/Anhang-Dokument</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="related_document_typ">
              <xs:sequence>
                   <xs:element ref="id"/>
                   <xs:element ref="set_id" minOccurs="0"/>
                   <xs:element ref="version_nbr" minOccurs="0"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <!-- ************************ document_type_cd_typ ********************************* -->
         <xs:element name="document_type_cd" type="document_type_cd_typ">
              <xs:annotation>
                   <xs:documentation>Dokumenttype Code</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="document_type_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.100"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <!--
         ============================================================
         Zeitangaben:
         service_tmr_typ: Gültigkeitszeitram der Daten (XML-Dokuments).
         origination_dttm_typ: Erstellungsdatum des XML-Dokuments
         ============================================================
         -->
         <!-- ************************ service_tmr_typ ********************************* -->
         <xs:element name="service_tmr" type="service_tmr_typ">
              <xs:annotation>
                   <xs:documentation>Gültigkeitszeitraum (date..date)</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="service_tmr_typ">
              <xs:complexContent>
                   <xs:extension base="v_zeitraum_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ origination_dttm_typ ********************************* -->
         <xs:element name="origination_dttm" type="origination_dttm_typ">
              <xs:annotation>
                   <xs:documentation>Erstellungsdatum</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="origination_dttm_typ">
              <xs:complexContent>
                   <xs:extension base="v_date_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <!--
         ============================================================
         Person/Organisation- Angaben:
         intended_recipient_typ: beabsichtigter Empfänger/Zielgruppe.
         originator_typ: Ersteller/Urheber (Person oder Organisationi).
         provider_typ: Sender/Lieferer (Person oder Organisation).
         person_typ: Person
         person_name_typ: Name der Person
         organization_typ: Organisation
         addr_typ: Adersse
         ============================================================
         -->
         <!-- ************************ intended_recipient_typ ********************************* -->
         <xs:element name="intended_recipient" type="intended_recipient_typ">
              <xs:annotation>
                   <xs:documentation>Empfänger / Zielgruppe der Daten</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="intended_recipient_typ">
              <xs:sequence>
                   <xs:element name="intended_recipient.type_cd" type="intended_recipient.type_cd_typ" minOccurs="0"/>
                   <xs:element ref="function_cd" minOccurs="0"/>
                   <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="intended_recipient.type_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.102"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ originator_typ ********************************** -->
         <xs:element name="originator" type="originator_typ">
              <xs:annotation>
                   <xs:documentation>Ersteller, Urheber des Dokuments / der Daten</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="originator_typ">
              <xs:sequence>
                   <xs:element name="originator.type_cd" type="originator.type_cd_typ" minOccurs="0"/>
                   <xs:element ref="function_cd" minOccurs="0"/>
                   <xs:element ref="participation_tmr" minOccurs="0"/>
                   <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="originator.type_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.103"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ provider_typ ********************************** -->
         <xs:element name="provider" type="provider_typ">
              <xs:annotation>
                   <xs:documentation>Sender, Lieferant des Dokuments (kann gleichzeitig der Urheber sein)</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="provider_typ">
              <xs:sequence>
                   <xs:element name="provider.type_cd" type="provider.type_cd_typ" minOccurs="0"/>
                   <xs:element ref="function_cd" minOccurs="0"/>
                   <xs:element ref="participation_tmr" minOccurs="0"/>
                   <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="provider.type_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.104"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <xs:element name="function_cd" type="function_cd_typ">
              <xs:annotation>
                   <xs:documentation>Funktion/Rolle der Person/Organisation</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="function_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.105"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <xs:element name="participation_tmr" type="v_zeitraum_typ">
              <xs:annotation>
                   <xs:documentation>Zeitraum/Zeitpunkt der Teilnahme</xs:documentation>
              </xs:annotation>
         </xs:element>
         <!-- ************************ person_typ ********************************** -->
         <xs:element name="person" type="person_typ">
              <xs:annotation>
                   <xs:documentation>Person-Daten</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:element name="group" type="group_typ">
              <xs:annotation>
                   <xs:documentation>zugehörende Gruppe, Ausprägung (z.B. Augenarzt)</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="group_typ">
              <xs:complexContent>
                   <xs:extension base="v_s_string_typ">
                        <xs:sequence>
                             <xs:element ref="group.type_cd"/>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:element name="group.type_cd" type="v_s_string_typ">
              <xs:annotation>
                   <xs:documentation>Gruppebezeichnung (z.B. Facharztagruppe)</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="person_typ">
              <xs:sequence>
                   <xs:element ref="id" minOccurs="0"/>
                   <xs:element ref="person_name" minOccurs="0"/>
                   <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:element name="telecom" type="v_string_typ">
              <xs:annotation>
                   <xs:documentation>Telekomunnikation (tel,mail,fax,...)</xs:documentation>
              </xs:annotation>
         </xs:element>
         <!-- ************************ person_name_typ ********************************** -->
         <xs:element name="person_name" type="person_name_typ">
              <xs:annotation>
                   <xs:documentation>Name der Person</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="person_name_typ">
              <xs:sequence>
                   <xs:element name="nm" type="person_name_nm_typ"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="person_name_nm_typ">
              <xs:choice minOccurs="0" maxOccurs="unbounded">
                   <xs:element name="GIV" type="pnxp_string_typ">
                        <xs:annotation>
                             <xs:documentation>Vorname</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="MID" type="pnxp_string_typ">
                        <xs:annotation>
                             <xs:documentation>Zusatzname</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="FAM" type="pnxp_string_typ">
                        <xs:annotation>
                             <xs:documentation>Nachname</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="PFX" type="pnxp_string_typ">
                        <xs:annotation>
                             <xs:documentation>Titel (Dr.)</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="SFX" type="pnxp_string_typ">
                        <xs:annotation>
                             <xs:documentation>Namenzusatz</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="DEL" type="pnxp_string_typ">
                        <xs:annotation>
                             <xs:documentation>Trennzeichen</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:choice>
         </xs:complexType>
         <!-- ************************ organization_typ ********************************** -->
         <xs:element name="organization" type="organization_typ">
              <xs:annotation>
                   <xs:documentation>Organisations-Daten</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="organization_typ">
              <xs:sequence>
                   <xs:element ref="id" minOccurs="0"/>
                   <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <!-- ************************ addr_typ ********************************** -->
         <xs:element name="addr" type="addr_typ">
              <xs:annotation>
                   <xs:documentation>Adresse</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="addr_typ">
              <xs:choice minOccurs="0" maxOccurs="unbounded">
                   <xs:element name="STR" type="v_string_typ"/>
                   <xs:element name="HNR" type="v_string_typ"/>
                   <xs:element name="POB" type="v_string_typ"/>
                   <xs:element name="ZIP" type="v_string_typ"/>
                   <xs:element name="CTY" type="v_string_typ"/>
                   <xs:element name="STA" type="v_string_typ"/>
                   <xs:element name="CNT" type="v_string_typ"/>
                   <xs:element name="ADL" type="v_string_typ"/>
              </xs:choice>
         </xs:complexType>
         <!--
         ============================================================
         CDA-Hilfstypen (patient_typ)
         ============================================================
         -->
         <xs:element name="patient" type="patient_typ">
              <xs:annotation>
                   <xs:appinfo>Patient-Informationen</xs:appinfo>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="patient_typ">
              <xs:sequence>
                   <xs:element name="patient.type_cd" type="v_s_string_typ" minOccurs="0"/>
                   <xs:element ref="person"/>
                   <xs:element name="birth_dttm" type="v_date_typ" minOccurs="0"/>
                   <xs:element name="administrative_gender_cd" type="v_s_string_typ" minOccurs="0"/>
                   <xs:element ref="local_header" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>
         <!--
         ============================================================
         local_header,      Einzige Stelle, wo eigendefinierte Elemente und SCIPHOX SSUS
         verwendet werden können.
         ============================================================
         -->
         <xs:element name="local_header" type="local_header-cont.model">
              <xs:annotation>
                   <xs:documentation>Element für weitere, datenartspezifische, Metainformationen</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="local_header-cont.model" mixed="true">
              <xs:choice minOccurs="0" maxOccurs="unbounded">
                   <xs:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
              </xs:choice>
              <xs:attribute name="ignore" type="ignore_typ" default="markup"/>
              <xs:attribute name="descriptor" type="xs:string"/>
              <xs:attribute name="render" type="xs:string"/>
         </xs:complexType>
         <!--
         ============================================================
         Komplexe Hilfstypen:
         v_string_typ: enthält nur den V-Attribut für einfache Daten-Angaben
         v_s_string_typ: wird für kodierte Wertepaare mit optionaler Schlüsseltabelle verwendet
         v_date_typ: enthält nur den V-Attribut für einfache Datums-Angaben
         v_zeitraum_typ: enthält nur den V-Attribut für Zeitraum-Angaben
         ============================================================
         -->
         <!-- ************************ v_string_typ ********************************** -->
         <xs:complexType name="v_string_typ">
              <xs:attribute name="V" type="xs:string" use="required"/>
         </xs:complexType>
         <!-- ************************ v_s_string_typ ********************************** -->
         <xs:element name="TRANSLTN" type="transltn_typ">
              <xs:annotation>
                   <xs:documentation>interne/alternative Kodes und Schlüsseltabellen</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="transltn_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="v_s_string_typ">
              <xs:attribute name="V" type="xs:string" use="required"/>
              <xs:attribute name="DN" type="xs:string" use="optional"/>
              <xs:attribute name="S" type="xs:string" use="optional"/>
              <xs:attribute name="SN" type="xs:string" use="optional"/>
              <xs:attribute name="SV" type="xs:string" use="optional"/>
         </xs:complexType>
         <!-- ************************ v_date_typ ********************************** -->
         <xs:complexType name="v_date_typ">
              <xs:attribute name="V" type="xs:date" use="required"/>
         </xs:complexType>
         <!-- ************************ v_zeitraum_typ ********************************** -->
         <xs:complexType name="v_zeitraum_typ">
              <xs:annotation>
                   <xs:documentation>Zeitraum: datum..datum</xs:documentation>
              </xs:annotation>
              <xs:attribute name="V" type="zeitraum_typ" use="required"/>
         </xs:complexType>
         <!-- ************************ pnxp_string_typ ********************************** -->
         <xs:complexType name="pnxp_string_typ">
              <xs:attribute name="V" type="xs:string" use="required"/>
              <xs:attribute name="QUAL" type="xs:NMTOKENS" use="optional"/>
         </xs:complexType>
         <!-- ======================================================================= -->
         <!-- Eigendefinierten Datentypen -->
         <!-- ======================================================================= -->
         <!--
         ============================================================
         Schnittstelle-Angaben:
         interface_typ: enthält Informationen über die Schnittstelle selbst.
         interface_nm_typ: Bezeichnung der Schnittstelle kann auch als kodierter Wert angegeben werden.
         interface_version_typ: Die Version der Schnittstelle
         description_typ: Kurzbeschreibung der Schnittstelle.
         ============================================================-->
         <!-- ************************ interface_typ ********************************* -->
         <xs:element name="interface" type="interface_typ">
              <xs:annotation>
                   <xs:documentation>enthält Informationen über die Schnittstelle selbst</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="interface_typ">
              <xs:sequence>
                   <xs:element name="id" type="interface_id_typ"/>
                   <xs:element name="interface.nm" type="interface_nm_typ"/>
                   <xs:element name="version" type="interface_version_typ"/>
                   <xs:element ref="originator" minOccurs="0" maxOccurs="unbounded"/>
                   <xs:element name="description" type="description_typ" minOccurs="0"/>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="interface_id_typ">
              <xs:complexContent>
                   <xs:restriction base="id_typ">
                        <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.109"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ interface_nm_typ ********************************* -->
         <xs:complexType name="interface_nm_typ">
              <xs:annotation>
                   <xs:documentation>Bezeichnung der Schnittstelle</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="v_string_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ interface_version_typ ********************************* -->
         <xs:complexType name="interface_version_typ">
              <xs:annotation>
                   <xs:documentation>Version der Schnittstellenbeschreibung</xs:documentation>
              </xs:annotation>
              <xs:complexContent>
                   <xs:extension base="v_string_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <!-- ************************ description_typ ********************************* -->
         <xs:complexType name="description_typ">
              <xs:annotation>
                   <xs:documentation>Kurzbeschreibung oder Link auf die WebSite mit der Schnittstellenbeschreibung</xs:documentation>
              </xs:annotation>
              <xs:attribute name="V" type="xs:string" use="required"/>
              <xs:attribute name="URL" type="xs:anyURI" use="optional"/>
         </xs:complexType>
         <!--
         ============================================================
         Geltungsbereich:
         wenn die Daten nur in bestimmten KV-Bereichen gelten
         ============================================================-->
         <xs:element name="scope" type="scope_typ">
              <xs:annotation>
                   <xs:documentation>Geltungsbereich</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="scope_typ">
              <xs:sequence>
                   <xs:element name="id" type="scope_id_typ" maxOccurs="unbounded"/>
                   <xs:element name="scope.type_cd" type="scope.type_cd_typ">
                        <xs:annotation>
                             <xs:documentation>z.B. 1=KV-Geltungsbereich</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="scope.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>Name des Bereichs zu dem id-Element (z.B. KV-Nord)</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="scope_id_typ">
              <xs:complexContent>
                   <xs:restriction base="id_typ">
                        <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.106"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="scope.type_cd_typ">
              <xs:complexContent>
                   <xs:restriction base="v_s_string_typ">
                        <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.107"/>
                   </xs:restriction>
              </xs:complexContent>
         </xs:complexType>
         <!--
         ============================================================
         Bearbeitungszustand:
         kann als kodierter Wert angegeben werden, im welchen Bearbeitungszustand das Dokument sich befindet
         ============================================================-->
         <xs:element name="state" type="state_typ">
              <xs:annotation>
                   <xs:documentation>Bearbeitungszustand</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="state_typ">
              <xs:complexContent>
                   <xs:extension base="v_s_string_typ"/>
              </xs:complexContent>
         </xs:complexType>
         <!-- ======================================================================= -->
         <!-- einfache Typen -->
         <!-- ======================================================================= -->
         <xs:simpleType name="null.code.set">
              <xs:annotation>
                   <xs:documentation>Ausprägungen für NULL-Attribut</xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:enumeration value="NI"/>
                   <xs:enumeration value="NA"/>
                   <xs:enumeration value="UNK"/>
                   <xs:enumeration value="NASK"/>
                   <xs:enumeration value="ASKU"/>
                   <xs:enumeration value="NAV"/>
                   <xs:enumeration value="OTH"/>
                   <xs:enumeration value="PINF"/>
                   <xs:enumeration value="NINF"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="guid_typ">
              <xs:annotation>
                   <xs:documentation>Typ für einen Global Unique Identifier</xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:pattern value="[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="zeitraum_typ">
              <xs:annotation>
                   <xs:documentation>Zeitraum datum..datum</xs:documentation>
              </xs:annotation>
              <xs:restriction base="xs:string">
                   <xs:pattern value="([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|(\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.)"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="ignore_typ">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="all"/>
                   <xs:enumeration value="markup"/>
              </xs:restriction>
         </xs:simpleType>
    </xs:schema>

  • Where to place xml and xsd files in Tomcat

    Hi,
    This is rather a stupid question but I am totally new to JAXP technology and i wanted to know is there a specific location where i need to store the xml and xsd files i created?. And how would i mention the target name space for the xsd file? I am usinf eclipse IDE and Tomcat 5.5.
    Thanks for the patiance.

    Is the question so stupid that no one even want to try to reply?

Maybe you are looking for

  • Reconfigured itself, now stuck on test page, please help

    I went to go listen to my ipod on my way home from work this morning. When I turned it on, it went to a weird screen and said it was reconfiguring. I followed all the prompts it told me to. However, it came to a to a certain screen and it wont let me

  • Asset procurement process

    Respected gurus, could you discuss the asset procurement complete process by invololving mm &ps module. regards jana

  • SQL question - how to get only the leafs

    i have a table of departments create table departments (   dept   number ,   father number )this is the data 1 1/2 1/2/4 1/2/4/6 1/2/4/7 1/2/4/8 1/3 1/3/5 1/3/9given a department number i need only the leafs (the lowest member in the hierarchy). for

  • How to print custom label print after Pick drop happen

    Dear All, I have a requirement, Have to print the custom label printing report after pick drop happening. can you please suggest how to do this, Seems there is no workflow business event or other methods. please suggest to how do achieve this. Thanks

  • Forms 9i tab pages inside a tab page

    hi, i m using forms 9i, is it possible to set a tab page inside a tab page ie i have a master tab page called 'Office' and i have to add two tab pages called 'excel', 'word' as the sub of this main tab..is it possible.......? if yes how ? thanks in a