DOCTYPE/DTD problem

I am having an issue with JSP's on a network without internet access. The problem seems to be with the DOCTYPE setting in the jsp. The error is showing up in the netbeans status bar (java.lang.AbstractMethodError at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:226)at org.apache.jasper.compiler.JspConfig.processWebDotXml(Jsp.................
Does anyone have any advice on how to resolve this issue. I am not able to find a local copy of http://www.w3.org/TR/html4/loose.dtd, which may have helped resolve the issue. Unfortunately I don't think it is possible to get a downloaded copy from the internet due to security restrictions enforced by our admins.

i dunno if there is a generic way of writing a SYSTEM uri that would look into a jar, so:
* using DOM, I would create my own EntityResolver that would point the parser to the DTD located in the jar.
* using SAX, I would do the same in the resolveEntity() method of my handler.

Similar Messages

  • ALSB 3.0 - Is it possible to insert doctype DTD?

    We are integrating with a client that requires a DTD to be define in the XML ie:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE Request SYSTEM "Request.dtd">
    <Xml></Xml>
    But I can't find any way to insert this doctype/dtd in a ALSB proxy service. Have tried with several different xquery methods and also an XSLT stylesheet that I know will ad the DTD correctly, but somehow it doesn't work in ALSB.
    The service is configured with message type 'Any XML' and HTTP transport.
    Does anyone know the correct way to do this?
    Thanks,
    Jens-Martin

    Hello,
    to be honest I have no idea about the exact location of doctypes.
    But if it is part of the payload you can insert anything with the insert action.
    Insert '<DOCTYPE ...>' before chapter in body
    <?xml version="1.0" encoding="utf-8" ?>
    <!DOCTYPE chapter
    PUBLIC "-//OASIS//DTD DocBook XML//EN" "../dtds/docbookx.dtd">
    <chapter><title>Chapter 1</title>
    anyway it is just a guess.

  • Creation of XML !DOCTYPE DTD Validation line

    Hello all!
    I've been working in the creation of an XML File via Abap Objects.
    <b>if_ixml</b>          For Document Header
    <b>if_ixml_document</b> For Document Header
    <b>if_ixml_element</b>  For Nodes and their Child Nodes
    I have already developed the code for creating the XML File.
    I think I have it completed, but I don't know how to insert the line that starts with <!DOCTYPE>.
    This line validates all the DOM tree structure against a DTD File.
    I've been searching for an example of how to do it, but I dind't find anything
    Wich is the proper Class, object or method that I have to implement for this topic?
    The Line I have to post on the XML file is one like this:
    <!DOCTYPE e-billing-payable PUBLIC "-//BxxxxFxxxxx.com//DTD Ebilling Enterprise to Bank 1.0//EN" "https://hb.xxx.com.ar/cobranzasonline/ebillingE2B.dtd">
    Thanks in advance,
    Claudio.

    Thanks Sandra, I was succesfull in getting the doc type but here is the format that I need
    <!DOCTYPE gsafeed PUBLIC "-//Google//DTD GSA Feeds//EN" "gsafeed.dtd">
    If I try to use entity declaration , it dosen't let me without passing the SYSTEM paramater. Is there any method within if_ixml_document_type or outside, that would help me pass the attributes to get in the below format.
    <!DOCTYPE rootElement PUBLIC "PublicIdentifier" "URIreference">
    Thanks
    Ganesh.S

  • Ignore !DOCTYPE DTD Link

    I want to Check in XML Files that have been created with an editor and validated against a DTD.
    Here my Question:
    Is it possible to tell the SimpleXMLParser to ignore the <!DOCTYPE ... Reference, since it isn't able to validate against the DTD that is referenced.

    Oracle iFS 1.0 does not support the use of DTDs with the SimpleXMLParser. It is not possible to have the SimpleXMLParser ignore the <!DOCTYPE> tag.
    Oracle iFS' XML parsing capabilities are planned to be enhanced in release 1.1.

  • DTD problem....

    Hello,
    I have to create a DTD in which each element can have three conditions,
    example
    <elementOne>
    can be either "required" or "applicable" or "not-applicable"
    I know if I declare an element in dtd and do not put any * or + sign infront of it,it becomes
    required.
    Question is,that is there a way to represent applicable or not applicable in a dtd.

    Actually, I think it might be a question mark "?". In defining an element, you can then say whether it has other elements and how many. The possibilities are:
    ? = optional
    * = zero to many
    + = one to many
    So optional means it doesn't matter either way, which could sort of handle the "N/A" case.

  • Problems with german language in golive 9

    hello i have problems if I want to past a text form word or another text editor into a new golive 9 html page. The letters like öäü are not shown correctly. what can I do?

    A lnik to the page might help...
    It sound like at DOCTYPE/Charset problem
    in HTML youll have to use the Alpha/ASCII codes to display those carecters coret across browsets
    http://www.visibone.com/htmlref/char/ceralpha.htm
    http://www.visibone.com/htmlref/char/webascii.htm

  • Spry Image Slideshow problems with IE?

    I have set up the Spry Image Slideshow widget and it works beautifully in Firefox and Chrome.  I'm having the same problems others have had.  I've read through the various discussions on here and have sorted some of them but am still stumped on a couple things!
    Here is the link to where I have it currently uploaded for testing purposes:  www.wohowebdesign.com/sidestrand/gallery.php
    My first problem was how the images just would not flow, skip all over and freeze.  After I changed the DOCTYPE, this problem was gone.
    My Second problem is now the images are blending ok, but when you go to use the controls to pause or click the arrows, a vertical line appears and does not go away. This is still occuring on my local computer tests, but the uploaded version seemed to work itself out... I have no idea how!!
    My third problem is the alignment of the whole gallery box will not line up properly on the page.  It is shifted to the right and this only happens when I view it in IE8 (not Firefox or Chrome).  Unfortunately most of our school uses IE8 so I need to have it working perfectly before I put the new site live.
    Any help or suggestions are greatly appreciated!
    Thank you,
    Debbie

    mdr4win wrote:
    i dont think you understood my question, wasnt about body background, but abut the spry image slideshow to work properly in IE
    I was not talking about body background, but about having markup that screws up your document when using a browser. Body background just happened to be there. Perhaps you would do well to have a look here http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Flittletreats.org%2F.
    I have noticed that you ignored my solution; your document still shows two bodies.
    Perhaps I should have mentioned that I tested in IE6 through to IE9 using IETester and the above was the only thing stopping IE from performing properly.
    How did you determine that the slideshow was not working correctly in IE and which versions of IE?
    Grumps

  • Creating XMLDocuments and setting their DTD

    Hello,
    i am exporting java objects to XML. I can construct a DOM with a XMLDocument and using its print method export it.
    What i was unable to do so far was setting the DTD of these documents.
    If i construct a parser, parse the DTD and then get the DTD via
    Document doc = parser.getDocument() and
    DocType dtd = doc.getDocumentType() how
    do i set the DTD of the freshly constructed XMLDocuments to use this one in order to be able to check the correctness of the documents using this DTD at a later time?
    Thanks.
    Regards,
    Dirk

    Your method of getting the DTD object is correct. However, we do not do any validation while creating the DOM tree
    using the DOM APIs. So setting the DTD in the Document will not help in validating the DOM tree that is constructed.
    The only way to validate an XML file is to parse the XML document using DOMParser or SAXParser.
    Oracle XML Team
    null

  • Topic: Incorrect Tag:Multiple Attributes with Same Collection Type

    I have an Object Type that contains multiple attributes with the same collection type. When I use OracleXML getXML to generate xml, the tag for all elements created for any of the matching types is the tag for the 1st of the similar attributes.
    work_t_v is an object view of a relational schema
    SQL> desc work_t_v
    Name Null? Type
    WORK_ID NUMBER(38)
    TITLE_OF_WORK VARCHAR2(512)
    MESH_HEADINGS MESH_HEADINGS_T
    AUTHORS AUTHORS_T
    COMMENT_ON WORK_REFERENCES_T
    COMMENT_IN WORK_REFERENCES_T
    ERRATUM_IN WORK_REFERENCES_T
    REPUBLISHED_FROM WORK_REFERENCES_T
    REPUBLISHED_IN WORK_REFERENCES_T
    SQL> desc work_references_t
    work_references_t TABLE OF WORK_REFERENCE_T
    Name Null? Type
    REFSOURCE VARCHAR2(255)
    NOTE VARCHAR2(255)select
    work.work_id,
    work.title_of_work,
    work.comment_on comment_on,
    work.comment_in comment_in,
    work.erratum_in erratum_in,
    work.republished_from republished_from,
    work.republished_in republished_in
    from work_t_v work
    where work_id = 99350984
    results in tag of <comment_on> for all the elements built from the work_references_t type (i.e., there are no <comment_in>, <erratum_in>, <republished_from> or <republished_in> elements)
    sample result is:
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [CommentOn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [CommentIn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [ErratumIn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [RepublishedFrom]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [RepublishedIn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    The above xml should be:
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [CommentOn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_IN>
    <COMMENT_IN_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [CommentIn]</REFSOURCE>
    </COMMENT_IN_ITEM>
    </ERRATUM_IN>
    <COMMENT_ON>
    <ERRATUM_IN_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [ErratumIn]</REFSOURCE>
    </ERRATUM_IN_ITEM>
    </ERRATUM_IN>
    <REPUBLISHED_FROM>
    <REPUBLISHED_FROM_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [RepublishedFrom]</REFSOURCE>
    </REPUBLISHED_FROM_ITEM>
    </REPUBLISHED_FROM>
    <REPUBLISHED_IN>
    <REPUBLISHED_IN_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601 [RepublishedIn]</REFSOURCE>
    </REPUBLISHED_IN_ITEM>
    </REPUBLISHED_IN>bracketed portion [] is contained within the refsource string to indicate what type of reference it should be displayed as.
    I also found that if I use the -withDTD parameter to include the dtd, the dtd includes the appropriate elements (comment_in, erratum_in, republished_from and republished_in). However, it incorrectly defines refsource and note multiple times (once for each WORK_REFERENCES_T attribute).
    Are these known problems? Will they be fixed? I'm more concerned about the XML problem than the DTD problem.
    Thanks! -- John Butler
    null

    Using the version of XML SQL Utility that comes with the next XSQL Servlet release 0.9.8.6 I did the following:
    create type foo as object (a number);
    create type foolist as table of foo;
    create view fooview
    as select
    cast(multiset(
    select sal from emp where rownum < 2)
    as foolist) list1,
    cast(multiset(
    select sal from emp where rownum < 2)
    as foolist) list2
    from dual;
    When I request a "SELECT * FROM FOOVIEW"
    through getXML I get:
    <?xml version="1.0"?>
    <ROWSET>
    <ROW num="1">
    <LIST1>
    <LIST1_ITEM>
    <A>800</A>
    </LIST1_ITEM>
    </LIST1>
    <LIST2>
    <LIST2_ITEM>
    <A>800</A>
    </LIST2_ITEM>
    </LIST2>
    </ROW>
    </ROWSET>
    So this appears fixed in the next code drop.
    In the interim, I'll email you the new JAR file until (since it won't be on OTN for a few more days).
    null

  • Incorrect Tag:Multiple Attributes with Same Collection Type

    I have an Object Type that contains multiple attributes with the
    same collection type. When I use OracleXML getXML to generate
    xml, the tag for all elements created for any of the matching
    types is the tag for the 1st of the similar attributes.
    work_t_v is an object view of a relational schema
    SQL> desc work_t_v
    Name Null? Type
    WORK_ID NUMBER(38)
    TITLE_OF_WORK VARCHAR2(512)
    MESH_HEADINGS MESH_HEADINGS_T
    AUTHORS AUTHORS_T
    COMMENT_ON WORK_REFERENCES_T
    COMMENT_IN WORK_REFERENCES_T
    ERRATUM_IN WORK_REFERENCES_T
    REPUBLISHED_FROM WORK_REFERENCES_T
    REPUBLISHED_IN WORK_REFERENCES_T
    SQL> desc work_references_t
    work_references_t TABLE OF WORK_REFERENCE_T
    Name Null? Type
    REFSOURCE VARCHAR2(255)
    NOTE VARCHAR2(255)
    select
    work.work_id,
    work.title_of_work,
    work.comment_on comment_on,
    work.comment_in comment_in,
    work.erratum_in erratum_in,
    work.republished_from republished_from,
    work.republished_in republished_in
    from work_t_v work
    where work_id = 99350984
    results in tag of <comment_on> for all the elements built from
    the work_references_t type (i.e., there are no <comment_in>,
    <erratum_in>, <republished_from> or <republished_in> elements)
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601
    [CommentOn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601
    [CommentIn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601
    [ErratumIn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601
    [RepublishedFrom]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    <COMMENT_ON>
    <COMMENT_ON_ITEM>
    <REFSOURCE>J Infect Dis 1998 Aug;178(2):601
    [RepublishedIn]</REFSOURCE>
    </COMMENT_ON_ITEM>
    </COMMENT_ON>
    bracketed portion [] is contained within the refsource string to
    indicate what type of reference it should be displayed as.
    I also found that if I use the -withDTD parameter to include the
    dtd, the dtd includes the appropriate elements (comment_in,
    erratum_in, republished_from and republished_in). However, it
    incorrectly defines refsource and note multiple times (once for
    each WORK_REFERENCES_T attribute).
    Are these known problems? Will they be fixed? I'm more
    concerned about the XML problem than the DTD problem.
    Thanks! -- John Butler
    null

    Using the version of XML SQL Utility that comes with the next XSQL Servlet release 0.9.8.6 I did the following:
    create type foo as object (a number);
    create type foolist as table of foo;
    create view fooview
    as select
    cast(multiset(
    select sal from emp where rownum < 2)
    as foolist) list1,
    cast(multiset(
    select sal from emp where rownum < 2)
    as foolist) list2
    from dual;
    When I request a "SELECT * FROM FOOVIEW"
    through getXML I get:
    <?xml version="1.0"?>
    <ROWSET>
    <ROW num="1">
    <LIST1>
    <LIST1_ITEM>
    <A>800</A>
    </LIST1_ITEM>
    </LIST1>
    <LIST2>
    <LIST2_ITEM>
    <A>800</A>
    </LIST2_ITEM>
    </LIST2>
    </ROW>
    </ROWSET>
    So this appears fixed in the next code drop.
    In the interim, I'll email you the new JAR file until (since it won't be on OTN for a few more days).
    null

  • Installing JAXB on Solaris 8

    I apologize in advance for the long mail, it is so only to explain my problem clearly.
    I am having a problem in using xjc compiler on Solaris 8.
    I want to use JAXB on Solaris 8.
    For that required JWSDP, and for JWSDP I require Java2 and for installing Java2 on Solaris 8, I require a Patch recommended for Solaris 8.
    All software was available on the Sun website.
    1. I installed the patch(J2SE_Solaris_8_Recommended.zip) on Solaris 8 machine. There were about 27 patches. While installing some patches failed, around 11-12 and rest were installed successfully, those that failed returned either Code 2 or Code 8 error. Then I rebooted machine.
    2.Installed j2sdk-1_4_1_07-solaris-sparc.sh.
    3. Installed jwsdp-1_3-unix.sh and floowed requisite instructions.
    4. Now I set the requisite PATH and CLASSPATH variables.
    5. I ran xjc compiler to generate java files from 'dtd' document.
    %xjc.sh -dtd try.dtd
    Problem
    When i run xjc on windows machine, all java files are created in 'generated' directory.(Everything works fine on Windows)
    When i run xjc.sh on Solaris 8, all java files are created in 'null' directory. And code in java files are like import null.XXXX.
    Thus i am not able to use the xjc for parsing my XML documents.
    Thanks

    Sure, Oracle's App. Server are develop in Solaris platform.
    Best regards, Marcelo.
    null

  • Error parsing TLD?!

    Hi everyone:
    I test my taglib file use JRun.I place the .tld and the .class in correct dir.But when I compile my jsp file testtag.jsp and JRun report the under error:
    ////////////////////////testtag.jsp/////////////
    Error parsing TLD '/WEB-INF/taglib/mytag.tld': com.sun.xml.parser/P-082 http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd.
    org.xml.sax.SAXParseException: com.sun.xml.parser/P-082 http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd
         at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
         at com.sun.xml.parser.Parser.externalParameterEntity(Parser.java:2506)
         at com.sun.xml.parser.Parser.maybeDoctypeDecl(Parser.java:1137)
         at com.sun.xml.parser.Parser.parseInternal(Parser.java:481)
         at com.sun.xml.parser.Parser.parse(Parser.java:284)
         at com.sun.xml.parser.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:95)
         at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:78)
         at allaire.jrun.jsp.JRunTagLibraryInfo.<init>(../jsp/JRunTagLibraryInfo.java:198)
         at allaire.jrun.jsp.JRunTagLibraryInfo.lookupTLI(../jsp/JRunTagLibraryInfo.java:109)
         at allaire.jrun.jsp.JSPParser.taglibDirective(../jsp/JSPParser.java:842)
         at allaire.jrun.jsp.JSPParser.directive(../jsp/JSPParser.java:973)
         at allaire.jrun.jsp.JSPParser.parse(../jsp/JSPParser.java:921)
    It seems the .dtd problem.But I download the .dtd1.2 for my JRun and the problem remain happen! What does it mean?Could anyone explanation for me?

    Hi tolmank:
    Thank you to reply.I open it with xmlwriter.It report error when I run it.It says:
    DTD can't have DTD declare in external DTD��handle source: 'file:///E:/JRun/lib/web-jsptaglibrary_1_2.dtd' a error happen��nineteen range��location: 12
    <!NOTATION WEB-JSPTAGLIB.1_2 PUBLIC "-//Sun Microsystems, Inc.//DTD JSP T... .
    -----------^
    But I download the DTD file from sun's homepage!Why?

  • Structure recognised, element catalogue not populated

    Must be doing something wrong, but can't work out what!
    b what I've got:
    * FM 8.0
    * a well-structured, valid xml file with a doctype
    * dtd for the same (obviously)
    * structure-only (no formatting yet) edd generated from the dtd
    * udpated structapps file with an entry identifying the doctype and the dtd
    b what happens
    I open FrameMaker and then file > open the xml; no errors, and the structure window is populated ... but everything is red, and there are no entries in the element catalogue
    I'll see if I find any tips in the Structure Development guide, but any hints and tips in the meantime would be appreciated and welcome.
    [ps] Ain't those out-of-frame bullets something =8-}

    Hi,
    Looks like you haven't import the edd to the template file. Frame does not use the edd directly, in structapps.fm, the application defines the rw-rules, template to be used etc, but the edd must separately be imported to template.
    Open the edd, then template and use "Import Element Definitions" to populate the template (don't remember by heart where the command is in fm8, prob. under "Structure Tools")
    Martti

  • EAR specification

    What is a valid EAR? Can someone direct me to a specification? We are building an EAR using ant's ear task. This ear deploys and runs fine on both JBoss 3.0 and JRun 4. But when we run Sun's verifier tool from J2EE 1.3.1 there is a NullPointerException, apparently trying to read a library jar. This happens also if the jar in question is extracted and verified. The library jar contains only plain Java classes. There are also some ERRORS and WARNINGS on the ejb.jar too.
    We we want to make our application verify and deploy on the RI server. Can someone help?
    Thanks,
    -Richard Brewster

    Richard,
    The following is the DTD for the application.xml file in the META_INF path:
    http://java.sun.com/dtd/application_1_3.dtd
    If you have installed and started the J2EE RI server, you should be able to access the following DTD for the sun-j2ee-ri.xml file in the same path:
    http://localhost:8000/sun-j2ee-ri_1_3.dtd
    Problems with trying to access library jars can sometimes be due to the security permissions on the server. You might need to add the following to your server.policy and/or client.policy files in $J2EE_HOME/lib/security/ path:
    grant
       java.lang.RuntimePermission "loadLibrary.*";
    }If you know the library you wish to load and still wish to restrict access to other libraries, replace the * with the name of the library.
    This should get you started. Without knowing the exact nature of the errors and warnings its pretty hard to help any further.
    Ben New
    [email protected]
    Leftclick Software Development
    http://www.leftclick.com.au/

  • XML load using PL/SQL (XSU) problem with dtd file.

    Hi,
    I'm trying to load a xml file and receives this errormassage:
    SQL> exec loadxml;
    In Exception
    ORA-29532: Java call terminated by uncaught Java exception:
    oracle.xml.sql.OracleXMLSQLException: Error opening external DTD
    'Businesscard.DTD'.
    Any idea what I can change? Below is the things I've done and also how the xml file looks
    and the dtd file.
    Regards
    Jorgen
    CREATE DIRECTORY XML_DIR AS 'C:\XML';
    CREATE TABLE XML_TEMP (key NUMBER, f_lob BFILE);
    INSERT INTO XML_TEMP VALUES (1,BFILENAME('XML_DIR','TeleAdressVKI0209021728.xml'));
    CREATE TABLE XML_DOC (
    Key1 VARCHAR2(32),
    Key2     VARCHAR2(32),
    Key3 VARCHAR2(32),
    Terminate     VARCHAR2(3),
    LegalName     VARCHAR2(420),
    PopName          VARCHAR2(420),
    StreetName     VARCHAR2(60),
    StreetNumber     VARCHAR2(10),
    PostNumber     VARCHAR2(10),
    PostAdress VARCHAR2(30),
    CordinateLevel     VARCHAR2(32),
    xCor          VARCHAR2(10),
    yCor VARCHAR2(10),
    PoiCategory VARCHAR2(32),
    Telephone VARCHAR2(30));
    CREATE OR REPLACE PROCEDURE loadxml AS
    fil BFILE;
    buffer RAW(32767);
    len INTEGER;
    insrow INTEGER;
    BEGIN
    SELECT f_lob INTO fil FROM xml_temp WHERE key = 1;
    DBMS_LOB.FILEOPEN(fil,DBMS_LOB.FILE_READONLY);
    len := DBMS_LOB.GETLENGTH(fil);
    DBMS_LOB.READ(fil,len,1,buffer);
    xmlgen.resetOptions;
    insrow := xmlgen.insertXML('xml_doc',UTL_RAW.CAST_TO_VARCHAR2(buffer));
    DBMS_OUTPUT.PUT_LINE(insrow);
    IF DBMS_LOB.FILEISOPEN(fil) = 1 THEN
    DBMS_LOB.FILECLOSE(fil);
    END IF;
    EXCEPTION
    WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE('In Exception');
    DBMS_OUTPUT.PUT_LINE(SQLERRM(SQLCODE));
    IF DBMS_LOB.FILEISOPEN(fil) = 1 THEN
    DBMS_LOB.FILECLOSE(fil);
    END IF;
    end;
    The xml file look like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE Cards SYSTEM 'Businesscard.DTD'>
    <Cards>
    <Comment>TeleAdress initial</Comment>
    <OldFile>xxxx</OldFile>
    <NewFile>xxxx</NewFile>
    <Card>
    <Key1>95352</Key1>
    <Key2>159651</Key2>
    <Key3>3807868</Key3>
    <Terminate>no</Terminate>
    <Cardholder>
    <LegalName>
    <Name>
    <Full>AXFOOD DIREKT AB</Full>
    </Name>
    </LegalName>
    <PopName>
    <Name>
    <Full>WILLYS LEGPRIS AB</Full>
    </Name>
    </PopName>
    </Cardholder>
    <Location>
    <Address>
    <StreetInfo>
    <StreetName>BAGARBYVDGEN</StreetName>
    <StreetNumber>61</StreetNumber>
    </StreetInfo>
    <ZipCode>19134</ZipCode>
    <City>SOLLENTUNA</City>
    <Coordinate>
    <Level>1</Level>
    <xCor>1620480</xCor>
    <yCor>6592717</yCor>
    </Coordinate>
    </Address>
    <Business>
    <POI>
    <POIId>46</POIId>
    <POIId>84</POIId>
    </POI>
    <InfoRow>
    <Subscriptions>
    <TelAddress>08 6234540</TelAddress>
    </Subscriptions>
    </InfoRow>
    </Business>
    </Location>
    </Card>
    <Card_Count>1</Card_Count>
    </Cards>
    the dtd file looks like this:
    <!-- BusinessCard.dtd -->
    <!-- History:          See end of this file -->
    <!-- Description:      This DTD is used for transferring business cards-->
    <!--               from TeleAdress Information AB to its customers. -->
    <!--===================== Root Element ===========================-->
    <!ELEMENT     Cards     (Comment,OldFile?,NewFile,Card*,Card_Count)>
         <!ELEMENT     Comment                         (#PCDATA)>
         <!ELEMENT     OldFile                         (#PCDATA)>
         <!ELEMENT     NewFile                         (#PCDATA)>
    <!--===================== Card ============================-->
    <!ELEMENT     Card     (Key1, Key2, Key3, Terminate, (RegNo?, Cardholder, Row*)?)>
         <!ELEMENT     Key1          (#PCDATA)>
         <!ELEMENT     Key2          (#PCDATA)>
         <!ELEMENT     Key3          (#PCDATA)>
         <!ELEMENT     Terminate     (#PCDATA)> <!-- Values can be yes or no-->
    <!--====================== Cardholder ============================-->
    <!ELEMENT     Cardholder     (RegNo, OrgType, LegalName, PopName?, Location)     >
         <!ELEMENT     RegNo          (#PCDATA)>
         <!ELEMENT     OrgType          (#PCDATA) >
    <!--====================== RegName ==================================-->
    <!ELEMENT     LegalName          (Name)>
    <!--====================== PopName ==================================-->
    <!ELEMENT     PopName          (Name+)>
    <!--====================== Location ==================================-->
    <!ELEMENT     Location          (Adress+, Unit*, Business)>
    <!--====================== Unit ==================================-->
    <!ELEMENT     Unit          (UnitNo, UnitName?, Status, HQ, SNI1?, SNI2?, SNI3?, WorkPlaceNo, WorkPlaceName?)>
         <!ELEMENT     UnitNo          (#PCDATA)>
         <!ELEMENT     UnitName     (#PCDATA)>
         <!ELEMENT     Status          (#PCDATA)>
         <!ELEMENT     HQ          (#PCDATA)> <!-- Values can be yes or no-->
         <!ELEMENT     SNI1          (#PCDATA)>
         <!ELEMENT     SNI2          (#PCDATA)>
         <!ELEMENT     SNI3          (#PCDATA)>
         <!ELEMENT     WorkPlaceNo     (#PCDATA)>
         <!ELEMENT     WorkPlaceName     (#PCDATA)>
    <!--====================== Business ==================================-->
    <!ELEMENT     Business          (POI?, InfoRow*)>
    <!--====================== POI =======================================-->
    <!ELEMENT     POI          (POIId+)>
         <!ELEMENT     POIId          (#PCDATA)>
    <!--====================== InfoRow ===================================-->
    <!ELEMENT     InfoRow          (Number,Heading*,Name?, Address?, Text?, HomePageAddresses?, EMailAddresses?, Subscriptions?)>
         <!ELEMENT     Number          (#PCDATA)>
    <!--====================== Heading =================================-->
    <!ELEMENT     Heading          (LevelNo, LevelName)>
         <!ELEMENT      LevelNo          (#PCDATA)>
         <!ELEMENT     LevelName     (#PCDATA)>
    <!--====================== Name =================================-->
    <!ELEMENT     Name          (Full,First?,Middle?,Last?)>
         <!ELEMENT      Full          (#PCDATA)>
         <!ELEMENT     First          (#PCDATA)>
         <!ELEMENT     Middle          (#PCDATA)>
         <!ELEMENT     Last          (#PCDATA)>
    <!--====================== Address ==============================-->
    <!ELEMENT     Address               (Type, StreetInfo?,TextBeforeZipCode?,ZipCode?,City?,AReg?,
                             Municipality?,County?,Country?,Coordinate?)>
         <!ELEMENT     Type               (#PCDATA)>     
         <!--====================== StreetInfo ==============================-->
         <!ELEMENT     StreetInfo          (PostBox?, StreetName?,StreetNumber?,Entrance?, CO?)>
              <!ELEMENT     PostBox               (#PCDATA)>
              <!ELEMENT     StreetName          (#PCDATA)>
              <!ELEMENT     StreetNumber          (#PCDATA)>
              <!ELEMENT     Entrance          (#PCDATA)>
              <!ELEMENT     Co               (#PCDATA)>
         <!ELEMENT     TextBeforeZipCode     (#PCDATA)>
         <!ELEMENT     ZipCode               (#PCDATA)>
         <!ELEMENT     City               (#PCDATA)>
         <!ELEMENT     AReg               (#PCDATA)>     
         <!ELEMENT     Municipality          (#PCDATA)>
         <!ELEMENT     County               (#PCDATA)>
         <!ELEMENT     Country               (#PCDATA)>
         <!--====================== Coordinate ==============================-->
         <!ELEMENT     Coordinate          (Level, xCor,yCor)>
              <!ELEMENT     Level          (#PCDATA)>
              <!ELEMENT     xCor          (#PCDATA)>
              <!ELEMENT     yCor          (#PCDATA)>
    <!--====================== Text =================================-->
    <!ELEMENT     Text          (InfoText+)>
         <!ELEMENT     InfoText          (#PCDATA)>     
    <!--====================== HomePageAddresses =================================-->
    <!ELEMENT     HomePageAddresses          (HomePage+)>
         <!ELEMENT     HomePage          (#PCDATA)>     
    <!--====================== EMailAddresses =================================-->
    <!ELEMENT     EMailAddresses          (EMail+)>
         <!ELEMENT     EMail          (#PCDATA)>     
    <!--======================= Subscriptions ===========================-->
    <!ELEMENT     Subscriptions     (ClassifiedCode?, Type, TelAddress, TextAfter?)     >
         <!ELEMENT     TelAddress     (#PCDATA)>
         <!ELEMENT     TextAfter     (#PCDATA)>
    <!ELEMENT     Card_Count               (#PCDATA)>
    <!--==============================================================-->
    <!-- History:          2002-06-06 created this file -->
    <!--                2002-07-04 Added Source on Coordinates -->
    <!--               2002-08-15 Changed Source to Level -->
    <!--               2002-08-15 Changed RegName to LegalName-->

    I've got the same problem,
    How to define the directory in witch the DTD is????
    We need something like DBMS_XMLSave.setdirectoryDTD, that doesn't exist.
    ben
    ERREUR ` la ligne 1 :
    ORA-29532: appel Java arrjti par une exception Java non interceptie :
    oracle.xml.sql.OracleXMLSQLException: Error opening external DTD
    'annoncesv22.dtd'.
    ORA-06512: ` "SDEV.SIMPORT", ligne 205
    ORA-06512: ` ligne 1

Maybe you are looking for