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

Similar Messages

  • 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 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.

  • Oracle XML parser and schema validation

    Hi Forum,
    I have problem parsing XML with validation against XML schema. I define location of schema (URL) in xml file and Oracle parser could not find the schema (xml file is correct - checked in other programs). When I point to xml schema directly from Java (using parser.setXMLSchema) before calling parser.parse, it works just fine. Where is the problem? Does oracle parser works correctly with XML Schema?
    TIA,
    Alex

    SAXParser saxParser=new SAXParser();
    saxParser.setValidationMode(XMLParser.SCHEMA_VALIDATION);
    Specify a Schema to validate a XML document with, for the SAXParser.
    saxParser.setXMLSchema(SchemaUrl);
    DefaultHandler handler=new DefaultHandler();
    saxParser.setErrorHandler(handler);
    Parse the XML document to validate with the XML schema.
    saxParser.parse(XmlDocumentUrl);

  • Oracle XML Parser validation against XML Sxhema

    Hi,
    I am developing a program in C++ on Unix, that does parsing on an XML document. For parsing I am using "Oracle XML Parser" [using DOM API]. My question is, Can Oracle XML Parser validate xml document against an XML Schema file also? I have read in many tutorials that it can validate against DTD. Please clarify my question as early as possible?
    Regards,
    Raghuram.

    Hi Kulkarni,
    I think you are trying to retrieve the text of the parent element of book. For example if this is the xml element
    <bookdetails>
    <book>Harry Potter</book>
    <author>JK Rowling</author>
    <price>34.55</price>
    </book>
    </bookdetails>
    You must be trying to retrieving the text of bookdetails.
    Check XMLNode.getNodeName() to retrieve the name of the node.
    To get 'Harry Potter' as output you need to traverse till book and then use XMLNode.getText()
    You can check the 'getQuestions()' method in Survey Sample
    to know how to tranverse to any element of an XML using Java.
    The Survey Sample is located at
    http://otn.oracle.com/sample_code/tech/xml/survey/content.html
    Download the sample and unjar it. The location of Analyser.java is
    SurveySample\code\Survey\src\oracle\otnsamples\survey\business\Analyser.java
    Have a look at it.
    Regards,
    Anupama
    http://otn.oracle.com/sample_code/content.html

  • XML validation using Oracle XML parser v2

    Not sure if this is the right forum for this question as I didn't found any.
    I had a tough time trying to build an XMLSchema (Oracle XML Parser V2) object from the input schema having include/import. Actually I am working on a Java program to validate the input xml with input schema using Oracle XML parser v2 api.
    The issue is that the code doesn't work for schema that has some "include" in it. The code is working fine for the schema without any import/include. Here is the lines of code -
    XSDBuilder builder = new XSDBuilder();
    schema = builder.build(new InputSource(xsdReader));
    I am writing this in JDeveloper. The error is -
    oracle.xml.parser.schema.XSDException: Can not build schema 'http://www.fpml.org/2005/FpML-4-2' located at 'xsd\FpML42\xml\fpml-fx-4-2.xsd'
    I also tried creating the EntityResolver to specify the path of included schema. But that doesn't solves the problem.
    I am not sure whether parser is able to locate the included schema or not.The main schema and included schema are all in same folder. The included schema is perfectly fine and has no errors.
    Please help if you have encountered this issue and resolved it. I will really appreciate any pointers or clue to solve this issue.
    Thanks.

    Thanks for the reply. But it does not seem to be working. Am I missing something
    I put <TrxDate xsi:nil="true"/> but still getting error.
    Here's my xsd:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified">
    <xsd:element name="TrxDate" type="xsd:date" nillable="true" />
    XML:
    <?xml version="1.0" encoding="UTF-8" ?>
    <ServiceRequest>
    <TrxDate nil="true"/>
    </ServiceRequest>

  • 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

  • Howto force Oracle XML parser not to expand entity references?

    Hi,
    Is it possible to force Oracle XML parser (Java) not to expand entity references, so that they appear in DOM tree as separated nodes after parsing XML?
    Example:
    for following XML
    <tag>abc&auml;xyz</tag>
    I get:
    Element: "tag"
    |-Text: "abcdxyz"
    but I would like to get:
    Element: "tag"
    |-Text: "abc"
    |
    |-EntityReference: "auml"
    |
    |-Text: "xyz"
    I've already tried to use JAXP api (setExpandEntityReferences method in java.xml.parsers.DocumentBuilderFactory), but it doesn't seem to work.
    I'm using parser from XDK Java v9.2.0.2.0 Production.
    Thx,
    James

    This is requested code sample:
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
    dbf.setExpandEntityReferences(false);
    System.out.println("isExpandEntityReferences = "+dbf.isExpandEntityReferences());
    DocumentBuilder db = dbf.newDocumentBuilder();
    Document d = db.parse("file://c:/test.xml");
    Element e = d.getDocumentElement();
    System.out.println("documentElement"+ e.getTagName() + " nodeType=" +e.getNodeType());
    System.out.println("ChildNodes:");
    NodeList nodeList = e.getChildNodes();
    for(int i=0; i<nodeList.getLength();i++) {
    System.out.println(i+" value=\""+nodeList.item(i).getNodeValue()+"\" nodeType="+nodeList.item(i).getNodeType());
    Content of test.xml:
    <!DOCTYPE test SYSTEM "test.dtd">
    <test>abc&auml;xyz</test>
    Content of test.dtd:
    <!ELEMENT test (#PCDATA)>
    <!ENTITY auml "&#x00E4;">
    When you run it you will get the following output:
    isExpandEntityReferences = true
    documentElementtest nodeType=1
    ChildNodes:
    0 value="abcdxyz" nodeType=3
    which means that EntityReference has been expanded.
    As you can see in the output the isExpandEntityReferences method returns "true", even though I set it to false in code!
    Does it mean that Oracle parser simple doesn't support this feature???
    Thx,
    James

  • Oracle.xml.parser.v2.SAXParser error

    I'm reposting this error that I recently received one more time before removing the XML transforms from my Java projects and doing them in .NET.
    Code that was working fine suddenly getting a transform error using JDeveloper.
    Get the following:
    javax.servlet.ServletException: javax.xml.transform.TransformerConfigurationException: XML-22000: (Fatal Error) Error while parsing XSL file (weblogic.xml.jaxp.RegistryXMLReader cannot be cast to oracle.xml.parser.v2.SAXParser).
         at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:417)
    Seems that
    <!--
    <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <h1>Project Weekly Hours Worked</h1>
    <table>
    <c:import url="HoursWorked.xml" var="xmlHoursWorked" charEncoding="windows-1252"/>
    <c:import url="./HoursWorked3.xsl" var="xslt" charEncoding="windows-1252"/>
    <x:transform xml="${xmlHoursWorked}" xslt="${xslt}" />
    </table>
    -->
    will not transform XML to HTML via XSL in JSP anymore.
    If I run the XSL i get the HTML results I expected in an HTML test page.
    So I know the XML and XSL is sound.
    XSL and DOM parsing in Java/Oracle was a major pain in the ass in the first place and now this.
    Well I've spent hours going through Oralce/Java documentation on XML, DOM and XSL transforms.
    All that time spent and still so unstable. I don't think I was ever able to really get what I wanted
    which was to transform my XML document to HTML, update via JSP and have the XML document
    be updated and ready to view in a summary page. The XML document changes were never really
    available unless I closed the app and restarted. So all in all a failure of capabilities compared to my
    use of XML in .NET.
    So........
    Me thinks it will be a good idea to take out the transforms and have my JSP use a script to invoke a
    method in a class that extracts it from a message. Just have PL/SQL interface with XML and do the
    transform or serialize thing there.
    I don't want to give up on XML but I'm tired of trying to jam a square peg into a round hole
    with Java and JDeveloper.
    Brian

    We don't support file references ("cv1_0.dtd"). Only url type references
    are supported, of the form:
    @ <!DOCTYPE cv1 SYSTEM "http://www.oracle.com/public/cv1_0.dtd>
    Note that the url should be accessible to the world without the need to authenticate.
    you could put your dtd in the "public" area in your iFS system.
    Thanks,
    Sirisha
    null

  • Oracle XML Parser for Java

    Does the latest release of the Oracle XML Parser for Java support JDK 1.2.2?
    I have an application which makes use of the XML Parser which runs fine with JDK 1.1.7.
    But the application crashes with the use of JDK 1.2.2 .
    Any insight into this is appreciated.
    null

    The Oracle XSQL Servlet makes extensive use of the Oracle XML Parser for Java V2 as well as its XSLT Engine and runs without issue under 1.1.8 and 1.2.2.

  • Deployment problem : oracle.xml.parser.v2.XMLParseException

    Hi to all.
    I have a strange problem deplying an application. When the first jsp is loaded the follwing excteption is raised :
    OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib uri="/webapp/DataTags.tld" prefix="jbo" %>
    Error: oracle.xml.parser.v2.XMLParseException ( /notifiche.jsp ):
    line #:10 column #:10 : Element taglib not complete, expected elements '[validator, listener, tag]'.
    With the embedded OC4J server all works fine. This is not the first application i deploy but this is the first time i have a problem. I'm doing somthings wrong in the deployment descriptor ?
    TIA
    sergio sette

    After restarting the JDeveloper its working.

  • ADM-75024 [oracle.xml.parser] [904 vs. 906]

    Hi!,
    After running in the following exception in a 904 appserv (oracle.xml.parser.v2.XMLDOMException: Implementation does not support the object requested) we decided to use the 906 parser frrom the xdk. But now we are having a big problem: now there will no application will have been deployed/undeployed/redeployed interupted by an ADM-75024 exception. When restoring the original 904 parser it does work. but this isn't usuable!
    We tried following parameters, but it doesn't work:
    JVM parameters:
    -server -Djava.security.policy=/opt/oracle/oracleas/j2ee/app/config/java2.policy
    -Djava.awt.headless=false -Xms256m -Xmx1024m
    -Dhttp.proxySet=true -Dhttp.proxyHost=proxy -Dhttp.proxyPort=80
    -Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser
    -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
    -Djavax.xml.parsers.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
    -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
    but these parameters doesnt' have any influence because libraries will be loaded as follows:
    1. system
    2. container
    3. application
    We read many documents --> There exist following BUG numbers: 3565902, 4353119, 3654742, 3136577, 2591746, 3557552
    3565902 is nearest; The effect is always the same but different conditions. The suggestions are different. But one thing can be seen: that exception only occurs within 904 oracle xml parser!! With 3565902 the 906 switch solution is preferred.
    As seen under http://www.oracle.com/technology/tech/java/oc4j/904/collateral/OC4J-FAQ-904.html (25)
    the switch is no supported. Under http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-swapxmlparser/doc/readme.html the switching capabilites will be brougth with 10.1.3. But i can't use 10.1.3...however I need a solution for 904.
    1st: Is there any workaround for the problem mentioned above (oracle.xml.parser.v2.XMLDOMException)
    2nd: why the error while deployment/undeployment/redeployment occurs?
    thanks, merci, grazie ..en avance
    Andreas
    ps: i can provide log files if needed.

  • Oracle XML parser functionality

    I would like to clarify the following about Oracle XML parser:
    1. checks if the parser resolves and inserts tags that were omitted in tag minimization?
    2. checks if the parser will suggest ways to correct errors when encountering such error conditions?
    3. checks parsing errors when the DTD does not allow some elements to be nested?
    Would really appreciate a detailed explanation on the questions above.
    Thanks.

    I would like to clarify the following about Oracle XML parser:
    1. checks if the parser resolves and inserts tags that were omitted in tag minimization?
    Would you be more specific?
    2. checks if the parser will suggest ways to correct errors when encountering such error conditions?
    Would you be more specific? What kind of errors?
    3. checks parsing errors when the DTD does not allow some elements to be nested?
    Support.

  • Oracle9i: Difference between oraxml and oracle.xml.parser.v2.DOMParser?

    I have parsed the following xml document with the oraxml batch
    and with the sample '..\xdk\demo\java\parser\dom\DOMSample' and
    observed a diffent behavior in Oracle9i:
    <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
    <Document xmlns:n1='urn:example:some-names'
    xmlns:n2='urn:example:some-names'>
    <BadAttrs_XML_1.0 att='1' att='2' />
    <BadAttrs_Namespaces n1:att='1' n2:att='2' />
    <OKAttrs_XML_1.0 att='1' n2:att='2' />
    </Document>
    ----------------------------1.) oraxml
    C:\oracle\ora9011\xdk\demo\java\parser\dom>oraxml -version
    -warning Namespaces2.xml
    Parser version: Oracle XDK Java 9.0.1.0.0 Production
    The input XML file is parsed without errors using partial
    validation mode
    Oraxml does not recognize the two attributes with the same name
    in element 'BadAttrs_XML_1.0' as an error.
    2.) oracle.xml.parser.v2.DOMParser
    C:\oracle\ora9011\xdk\demo\java\parser\dom>java DOMSample
    Namespaces2.xml
    file:Namespaces2.xml<Line 8, Column 38>: XML-0124: (Fata
    l Error) An attribute cannot appear more than once in the same
    start tag.
    oracle.xml.parser.v2.XMLParseException: An attribute cannot
    appear more than once in the same start tag.
    I have modified the DomSample.java. The DomParser just checks for
    well-formed documents and doesn't validate the document anymore.
    (only a comment before
    parser.setValidationMode(DOMParser.DTD_VALIDATION);)
    My question is:
    Is there really a difference between oracle.xml.parser.v2.oraxml
    and oracle.xml.parser.v2.DOMParser or which parameters do I have
    to use to get the same results?
    With Oracle8i, both report an xml error!!
    (Oracle9i, Win2000, JDK1.3)
    Thanx in advance!
    Markus

    It would appear that there is a difference when a loadjava is given a jar vs. the individual class files. When I load the jar, I get the previously described error, but when I load the individual class files (the same class files that the jar contains) the error goes away.
    Why?

  • XML publisher : Error oracle.xml.parser.v2.XMLParseException: Expected ';'

    I am trying to output a customer list containing customer number and customer name using 11i ( 11.5.10 CU2) with latest XML publisher patches on.
    How do I debug the following error in OPP log:
    [UNEXPECTED] [72156:RT1088889] oracle.xml.parser.v2.XMLParseException: Expected ';'.
    The XML ouput file is generated fine but get the following error in the log file.
    | Starting concurrent program execution...
    +-----------------------------
    Spawned Process 13471
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 1088898 on node O11IDEV at 03-APR-2006 13:57:35.
    Post-processing of request 1088898 failed at 03-APR-2006 13:57:37 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    ------------- 2) PRINT   -------------
    Finished executing request completion options.
    The OPP service log messge is :
    [4/3/06 6:02:53 AM] [main] Starting GSF service with concurrent process id = 72156.
    [4/3/06 6:02:53 AM] [main] Initialization Parameters: oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
    [4/3/06 6:02:53 AM] [Thread-12] Service thread starting up.
    [4/3/06 6:02:53 AM] [Thread-13] Service thread starting up.
    [4/3/06 1:16:08 PM] [OPPServiceThread0] Post-processing request 1088889.
    [4/3/06 1:16:08 PM] [72156:RT1088889] Executing post-processing actions for request 1088889.
    [4/3/06 1:16:09 PM] [72156:RT1088889] Starting XML Publisher post-processing action.
    [4/3/06 1:16:09 PM] [72156:RT1088889]
    Template code: COCXDOTEST
    Template app: COC
    Language: en
    Territory: US
    Output type: PDF
    [040306_011610131][][EXCEPTION] [DEBUG] ------- Preferences defined PreferenceStore -------
    [040306_011610132][][EXCEPTION] [DEBUG] ------- Environment variables stored in EnvironmentStore -------
    [040306_011610133][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MAX]:[2]
    [040306_011610134][][EXCEPTION] [DEBUG] [USER_ID]:[-1]
    [040306_011610134][][EXCEPTION] [DEBUG] [FND_JDBC_PLSQL_RESET]:[false]
    [040306_011610135][][EXCEPTION] [DEBUG] [NLS_TERRITORY]:[AMERICA]
    [040306_011610135][][EXCEPTION] [DEBUG] [RESP_APPL_ID]:[-1]
    [040306_011610136][][EXCEPTION] [DEBUG] [FND_MAX_JDBC_CONNECTIONS]:[500]
    [040306_011610136][][EXCEPTION] [DEBUG] [NLS_SORT]:[BINARY]
    [040306_011610137][][EXCEPTION] [DEBUG] [FND_JDBC_IDLE_THRESHOLD.LOW]:[-1]
    [040306_011610138][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MIN]:[1]
    [040306_011610138][][EXCEPTION] [DEBUG] [RESP_ID]:[-1]
    [040306_011610139][][EXCEPTION] [DEBUG] [NLS_NUMERIC_CHARACTERS]:[.,]
    [040306_011610139][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_DECAY_SIZE]:[5]
    [040306_011610140][][EXCEPTION] [DEBUG] [NLS_LANGUAGE]:[AMERICAN]
    [040306_011610140][][EXCEPTION] [DEBUG] [FND_JDBC_IDLE_THRESHOLD.HIGH]:[-1]
    [040306_011610140][][EXCEPTION] [DEBUG] [NLS_DATE_LANGUAGE]:[AMERICAN]
    [040306_011610141][][EXCEPTION] [DEBUG] [LOGIN_ID]:[-1]
    [040306_011610141][][EXCEPTION] [DEBUG] [NLS_DATE_FORMAT]:[DD-MON-RR]
    [040306_011610142][][EXCEPTION] [DEBUG] [APPS_JDBC_URL]:[jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS_LIST=(ADDRESS
    =(PROTOCOL=tcp)(HOST=O11IDEV.concentra.com)(PORT=9200)))(CONNECT_DATA=(SID=DEV1)))]
    [040306_011610143][][EXCEPTION] [DEBUG] [SECURITY_GROUP_ID]:[0]
    [040306_011610144][][EXCEPTION] [DEBUG] [NLS_CHARACTERSET]:[US7ASCII]
    [040306_011610144][][EXCEPTION] [DEBUG] [FND_JDBC_CONTEXT_CHECK]:[true]
    [040306_011610145][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_DECAY_INTERVAL]:[300]
    [040306_011610145][][EXCEPTION] [DEBUG] [FND_JDBC_USABLE_CHECK]:[false]
    [040306_011610147][][EXCEPTION] [DEBUG] ------- Properties stored in Java System Properties -------
    [040306_011610148][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MAX]:[2]
    [040306_011610149][][EXCEPTION] [DEBUG] [sun.cpu.isalist]:[pa2.0 pa1.2 pa1.1 pa1.0]
    [040306_011610149][][EXCEPTION] [DEBUG] [java.version]:[1.3.1.09]
    [040306_011610150][][EXCEPTION] [DEBUG] [java.awt.graphicsenv]:[sun.awt.X11GraphicsEnvironment]
    [040306_011610150][][EXCEPTION] [DEBUG] [java.specification.vendor]:[Sun Microsystems Inc.]
    [040306_011610151][][EXCEPTION] [DEBUG] [sun.io.unicode.encoding]:[UnicodeBig]
    [040306_011610151][][EXCEPTION] [DEBUG] [JTFDBCFILE]:[oracle/app/dev1app/dev1appl/fnd/11.5.0/secure/o11idev_dev1.dbc]
    [040306_011610152][][EXCEPTION] [DEBUG] [java.runtime.name]:[Java(TM) 2 Runtime Environment, Standard Edition]
    [040306_011610153][][EXCEPTION] [DEBUG] [user.home]:[u02/app/dev1app]
    [040306_011610153][][EXCEPTION] [DEBUG] [java.specification.version]:[1.3]
    [040306_011610154][][EXCEPTION] [DEBUG] [java.vm.info]:[mixed mode]
    [040306_011610154][][EXCEPTION] [DEBUG] [user.dir]:[u02/app/dev1app/dev1appl/dev1csf/log/DEV1_o11idev]
    [040306_011610155][][EXCEPTION] [DEBUG] [java.io.tmpdir]:[var/tmp/]
    [040306_011610155][][EXCEPTION] [DEBUG] [LONG_RUNNING_JVM]:[true]
    [040306_011610155][][EXCEPTION] [DEBUG] [java.ext.dirs]:[opt/java1.3/jre/lib/ext]
    [040306_011610156][][EXCEPTION] [DEBUG] [dbcfile]:[oracle/app/dev1app/dev1appl/fnd/11.5.0/secure/o11idev_dev1.dbc]
    [040306_011610156][][EXCEPTION] [DEBUG] [FND_JDBC_BUFFER_MIN]:[1]
    [040306_011610157][][EXCEPTION] [DEBUG] [java.awt.fonts]:[]
    [040306_011610157][][EXCEPTION] [DEBUG] [java.class.version]:[47.0]
    [040306_011610158][][EXCEPTION] [DEBUG] [OVERRIDE_DBC]:[true]
    [040306_011610158][][EXCEPTION] [DEBUG] [sun.cpu.endian]:[big]
    [040306_011610159][][EXCEPTION] [DEBUG] [java.class.path]:[/opt/java1.3/lib/rt.jar:/opt/java1.3/lib/tools.jar:/opt/java1.3/jre/lib/rt.jar:/opt
    /java1.3/jre/lib/i18n.jar:/oracle/app/dev1app/dev1comn/java/appsborg.zip:/oracle/app/dev1app/dev1ora/8.0.6.9/forms60/java:/oracle/app/dev1app/d
    ev1comn/java]
    [040306_011610160][][EXCEPTION] [DEBUG] [os.name]:[HP-UX]
    [040306_011610160][][EXCEPTION] [DEBUG] [sun.boot.class.path]:[/opt/java1.3/jre/lib/rt.jar:/opt/java1.3/jre/lib/i18n.jar:/opt/java1.3/jre/lib/
    sunrsasign.jar:/opt/java1.3/jre/classes]
    [040306_011610161][][EXCEPTION] [DEBUG] [java.vendor.url.bug]:[http://www.hp.com/go/Java]
    [040306_011610161][][EXCEPTION] [DEBUG] [user.timezone]:[America/Chicago]
    [040306_011610162][][EXCEPTION] [DEBUG] [java.vm.name]:[Java HotSpot(TM) Server VM]
    [040306_011610163][][EXCEPTION] [DEBUG] [CACHEMODE]:[DISTRIBUTED]
    [040306_011610164][][EXCEPTION] [DEBUG] [cpid]:[72156]
    [040306_011610164][][EXCEPTION] [DEBUG] [java.vm.specification.name]:[Java Virtual Machine Specification]
    [040306_011610165][][EXCEPTION] [DEBUG] [java.vm.vendor]:[Hewlett-Packard Company]
    [040306_011610165][][EXCEPTION] [DEBUG] [user.language]:[en]
    [040306_011610166][][EXCEPTION] [DEBUG] [java.library.path]:[/opt/java1.3/bin/../jre/lib/PA_RISC2.0/native_threads:/opt/java1.3/bin/../jre/lib
    /PA_RISC2.0/server:/opt/java1.3/bin/../jre/lib/PA_RISC2.0:/oracle/app/dev1app/dev1ora/iAS_1.0.2/lib:/oracle/app/dev1app/dev1ora/8.0.6.9/network
    /jre11/lib/PA_RISC/native_threads:/oracle/app/dev1app/dev1appl/cz/11.5.0/bin::/oracle/app/dev1app/dev1ora/8.0.6.9/lib:/usr/lib:/usr/lib]
    [040306_011610167][][EXCEPTION] [DEBUG] [path.separator]:[:]
    [040306_011610167][][EXCEPTION] [DEBUG] [java.vm.specification.version]:[1.0]
    [040306_011610168][][EXCEPTION] [DEBUG] [java.awt.printerjob]:[sun.awt.motif.PSPrinterJob]
    [040306_011610168][][EXCEPTION] [DEBUG] [file.separator]:[]
    [040306_011610169][][EXCEPTION] [DEBUG] [java.runtime.version]:[1.3.1.09-030418-12:59]
    [040306_011610170][][EXCEPTION] [DEBUG] [java.vm.specification.vendor]:[Sun Microsystems Inc.]
    [040306_011610171][][EXCEPTION] [DEBUG] [java.vendor]:[Hewlett-Packard Co.]
    [040306_011610172][][EXCEPTION] [DEBUG] [file.encoding.pkg]:[sun.io]
    [040306_011610172][][EXCEPTION] [DEBUG] [java.vendor.url]:[http://www.hp.com/go/Java]
    [040306_011610173][][EXCEPTION] [DEBUG] [logfile]:[oracle/app/dev1app/dev1appl/dev1csf/log/DEV1_o11idev/FNDOPP72156.txt]
    040306_011610174][][EXCEPTION] [DEBUG] [os.arch]:[PA_RISC2.0]
    [040306_011610174][][EXCEPTION] [DEBUG] [os.version]:[B.11.11]
    [040306_011610174][][EXCEPTION] [DEBUG] [java.home]:[opt/java1.3/jre]
    [040306_011610175][][EXCEPTION] [DEBUG] [java.specification.name]:[Java Platform API Specification]
    [040306_011610175][][EXCEPTION] [DEBUG] [sun.boot.library.path]:[opt/java1.3/jre/lib/PA_RISC2.0]
    [040306_011610176][][EXCEPTION] [DEBUG] [line.separator]:[
    [040306_011610176][][EXCEPTION] [DEBUG] [file.encoding]:[8859_1]
    [040306_011610177][][EXCEPTION] [DEBUG] [user.name]:[oradev]
    [040306_011610177][][EXCEPTION] [DEBUG] [java.vm.version]:[1.3.1 1.3.1.09-_18_apr_2003_14_01 PA2.0]
    [4/3/06 1:16:13 PM] [UNEXPECTED] [72156:RT1088889] oracle.xml.parser.v2.XMLParseException: Expected ';'.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
    at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1001)
    at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1677)
    at oracle.xml.parser.v2.XMLReader.getEntity(XMLReader.java:1928)
    at oracle.xml.parser.v2.NonValidatingParser.parseContentEntityRef(NonValidatingParser.java:1575)
    at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1202)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:227)
    at oracle.apps.xdo.common.xml.XSLTClassic.transform(XSLTClassic.java:172)
    at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:160)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1015)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:968)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:209)
    at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1561)
    at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5975)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3555)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3614)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:229)
    at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)

    I was able to correct the error. The data contained an '&' sign and that was causing the xml parser to fail with the above error. If the & is replaced by a different character other than & then this error does not occur.
    Ashok

Maybe you are looking for