NullPointerException is weblogic xml parser

We are using weblogic server 8.1 SP4 on HP Tru64.
A NullPointerException is happening when parsing documents. I tried to find the source code however could not match the source version with the line numbers. Is this a problem in the message? Or a bug in the parser?
<?xml version="1.0" encoding="UTF-8"?>
<ns0:notificationOfApprovalResponse xmlns:ns0="http://www.auspost.com.au/elms/xml/notificationofapproval/response" elmsMailingStatementId="775507" pricingStatementNumber="0070922517">
<notificationOfApprovalStatus>
<code>S</code>
<extendedCode>233</extendedCode>
<description>ORDER_HEADER_IN has been processed successfully VBAKKOM </description>
</notificationOfApprovalStatus>
</ns0:notificationOfApprovalResponse>
java.lang.NullPointerException
at weblogic.apache.xerces.util.XMLAttributesImpl.getName(XMLAttributesImpl.java:261)
at weblogic.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:428)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:877)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java:569)
at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:727)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:759)
at weblogic.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:957)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1544)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:152)
at com.bea.xbean.store.Root$SaxLoader.load(Root.java:776)
at com.bea.xbean.store.Root.loadXml(Root.java:1077)
at com.bea.xbean.store.Root.loadXml(Root.java:1069)
at com.bea.xbean.store.Root.loadXml(Root.java:1089)
at com.bea.xbean.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:241)
at au.com.auspost.elms.xml.notificationofapproval.response.NotificationOfApprovalResponseDocument$Factory.parse(Unknown Source)

WLS 6.1 is not yet certifed with JDK 1.4.
Venki wrote:
Hi,
Does weblogic ships it's own XML parser.
We tried parsing an XML document using JDK1.4(default XML parser) it all worked
well, but after deploying in weblogic container, the document didn't parse correctly.
We are using Weblogic 6.1 sp2.
Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
i guess.
Any comments , help thanx !
Venki--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Similar Messages

  • Weblogic  XML Parser ?

    Hi,
    Does weblogic ships it's own XML parser.
    We tried parsing an XML document using JDK1.4(default XML parser) it all worked
    well, but after deploying in weblogic container, the document didn't parse correctly.
    We are using Weblogic 6.1 sp2.
    Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
    i guess.
    Any comments , help thanx !
    Venki

    WLS 6.1 is not yet certifed with JDK 1.4.
    Venki wrote:
    Hi,
    Does weblogic ships it's own XML parser.
    We tried parsing an XML document using JDK1.4(default XML parser) it all worked
    well, but after deploying in weblogic container, the document didn't parse correctly.
    We are using Weblogic 6.1 sp2.
    Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
    i guess.
    Any comments , help thanx !
    Venki--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • Fatal Error and NullPointerException in Oracle XML Transformer

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

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

  • Java XML Parser:Null Pointer exception in EntityReader

    I got NullPointer Exception when trying to parse a XML file which
    is pointed by a net URL, (say "http://www..."). The code causing
    problem is like:
    parser.parse(new URL("http://www.../demo.xml"));
    the exception I got is:
    java.lang.NullPointerException
    java.lang.NullPointerException
    at oracle.xml.parser.EntityReader.initXMLInput(Compiled
    Code)
    at
    oracle.xml.parser.EntityReader.<init>(EntityReader.java:64)
    at oracle.xml.parser.XMLParser.parse(XMLParser.java:245)
    at DemoXML.main(DemoXML.java:47)
    The very same code works fine with a simple local file URL and we
    also know that the URL exists in correct in XML format because we
    can open the URL with IE5.
    Another question - where can we get the source for the Java XML
    Parser.
    null

    This bug has already been reported and will be fixed in our next
    release.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    Fiona Lu (guest) wrote:
    : I got NullPointer Exception when trying to parse a XML file
    which
    : is pointed by a net URL, (say "http://www..."). The code
    causing
    : problem is like:
    : parser.parse(new URL("http://www.../demo.xml"));
    : the exception I got is:
    : java.lang.NullPointerException
    : java.lang.NullPointerException
    : at oracle.xml.parser.EntityReader.initXMLInput
    (Compiled
    : Code)
    : at
    : oracle.xml.parser.EntityReader.<init>(EntityReader.java:64)
    : at oracle.xml.parser.XMLParser.parse
    (XMLParser.java:245)
    : at DemoXML.main(DemoXML.java:47)
    : The very same code works fine with a simple local file URL and
    we
    : also know that the URL exists in correct in XML format because
    we
    : can open the URL with IE5.
    : Another question - where can we get the source for the Java
    XML
    : Parser.
    null

  • XML Parsing in Weblogic

    Hi all,
    Am releatively new to weblogic and am migrating my web app from the tomcat container to weblogic 9.2
    I use a XerxesImpl jar to parse my XML using a DOMParser and I dont want to use any libraries provided by weblogic atleast now!!
    It always gives the SAXParserException, but the same bit of code works fine with the tomcat container.
    I have also checked for the well-formedness of the xml and the xml and the dtd looks fine.
    Any inputs on this would help!
    Thnx
    Cyrus

    The solution to this being that ---
    1. Whenever using the local jar file for any XML parsing such as XerxesImpl.jar the weblogic provided services may try to override it and hence must be added on to the classpath before the ap[plication is deployed.
    2.Also that somtimes the pageContext.getServletContext() returns a null and hence some other means mustbe found to find the corresponding xml file.(probably loading it as an initparam)
    3. Also make sure that your xml matches the dtd declarations since atomcat container doesnt validate this but the weblogic container.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Error parsing XSL file (weblogic.xml.jaxp.RegistryXMLReader cannot be cast

    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html>
    <head>
    <meta name="generator" content="HTML Tidy for Java (vers. 26 Sep 2004), see www.w3.org">
    <title></title>
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
    <title>Transform</title>
    <link type="text/css" rel="stylesheet" href="css/CascadeMenu.css">
    </head>
    <body id="Bdy">
    Hello all, I've run into a perplexing problem with a new and unexptected error on a web application that resides in a JDeveloper 11g environment. I just run it from JDeveloper on my laptop. No deployement other than to the default server at run time Integratedweblogicserver. I am doing an XML transform using XSLT and it has been working fine until I tried to use the page yesterday. I get the following error. 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) at jsp_servlet.__transform._jspService(__transform.java:109) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: 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 oracle.xml.jaxp.JXSAXTransformerFactory.reportConfigException(JXSAXTransformerFactory.java:759) at oracle.xml.jaxp.JXSAXTransformerFactory.newTemplates(JXSAXTransformerFactory.java:371) at oracle.xml.jaxp.JXSAXTransformerFactory.newTransformer(JXSAXTransformerFactory.java:272) at weblogic.xml.jaxp.RegistryTransformerFactory.newTransformer(RegistryTransformerFactory.java:209) at org.apache.taglibs.standard.tag.common.xml.TransformSupport.doStartTag(TransformSupport.java:145) at jsp_servlet.__transform._jsp__tag2(__transform.java:223) at jsp_servlet.__transform._jspService(__transform.java:102) ... 25 more Caused by: java.lang.ClassCastException: weblogic.xml.jaxp.RegistryXMLReader cannot be cast to oracle.xml.parser.v2.SAXParser at oracle.xml.jaxp.JXSAXTransformerFactory.newTemplates(JXSAXTransformerFactory.java:357) ... 30 more ------------------------------------------------ I changed no code or moved any XML or XSLT file. I do see an error in the log regarding a bad URL ----------------------------------------------- XML-22108: (Error) Invalid Source - URL format is incorrect. XML-22000: (Fatal Error) Error while parsing XSL file (weblogic.xml.jaxp.RegistryXMLReader cannot be cast to oracle.xml.parser.v2.SAXParser). &lt;[ServletContext@10343785[app:QSBQAR module:QSBQAR-QSBQAR-context-root path:/QSBQAR-QSBQAR-context-root spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@699744[ GET /QSBQAR-QSBQAR-context-root/Transform.jsp?reqtype=1 HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; . ------------------------------ Here is the XML ------------------------------ <?xml version="1.0" encoding="windows-1252" standalone="no"?>
    ACME Bird Seed Co. Capture the Road Runner using a boulder, rope and bird seed. Quinn Brian 00 00 00 00 00 00 00 00 00 11 08 08 08 08 00 43 43 Hours have been approved. APPROVED Smart Jean 00 00 00 00 00 00 00 00 00 Hours approved. APPROVED --------------------------------------------------------------------------------------- Here is the XSL --------------------------------------------------------------------------------------- <?xml version="1.0" encoding="windows-1252"?>
    <!-- Root template -->
    <h2>Project Hours Worked</h2>
    ----------------------------------------------------------------------------------------- Here is the JSP with the transform ----------------------------------------------------------------------------------------
    <table>
    <tr>
    <td>Week Ending Date:--</td>
    </tr>
    <tr>
    <td></td>
    </tr>
    <tr>
    <th>Client</th>
    <td></td>
    <th>Project</th>
    <td></td>
    </tr>
    <tr>
    <td></td>
    </tr>
    <tr>
    <td></td>
    </tr>
    <tr>
    <th>Last Name</th>
    <th>First Name</th>
    <th>Task</th>
    <th>---</th>
    <th>Sun</th>
    <th>Mon</th>
    <th>Tue</th>
    <th>Wed</th>
    <th>Thu</th>
    <th>Fri</th>
    <th>Sat</th>
    <th>---</th>
    <th>Ttl</th>
    </tr>
    <tr>
    <td></td>
    <td></td>
    </tr>
    <tr>
    <td>---</td>
    <td>---</td>
    <td></td>
    <td>---</td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td>---</td>
    <td></td>
    </tr>
    <tr>
    <td>Total Hours: </td>
    <td></td>
    <td></td>
    </tr>
    <%@ page contentType="text/html;charset=windows-1252"%><%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %><%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %></table>
    <script type="text/javascript" src="scripts/CascadeMenu.js">
    </script>
    <% int bad = 1; %>
    <div id="menuBar" class="menuBar">
    <div id="Bar1" class="Bar">Home</div>
    <div id="Bar3" class="Bar">Accounting</div>
    <div id="Bar4" class="Bar">Help</div>
    </div>
    <div style="background:#84ffff; color:Aqua; "><br>
    <br>
    <p style="color:Orange; font-size:x-large; font-style:italic; font-weight:bold;
    font-family:Arial, Helvetica, sans-serif; "><img src="images/logoqsq.jpg" style="border:1" height="120" width="120" alt="Q Squared">
    </p>
    </div>
    <div>
    <p style="color:Black; font-size:x-large; font-style:italic; font-weight:bold; font-family:Arial, Helvetica, sans-serif;"><img src="images/dilbert.gif" alt="Dilbert" height="100" width="100">
    ? ? Welcome to Q Squared-Brian Quinn Consulting - Manager Time Approval</p>
    </div>
    <div>
    <table width="100%" class="table1">
    <tr>
    <td style="width:15%; border-width:medium; background-color:silver ">
    <h3>Contractor Resources</h3>
    <ul style="list-style-type:circle; ">
    <li>Time Entry</li>
    <li>Profile</li>
    </ul>
    <h3>Manager Resources</h

    LOL - I didn't think about the forum message area having trouble displaying my XML XSLT problem
    It seemed to mix the code with the site XML.
    Oh brother
    The deal is this.
    The XML XSLT transform was working and now it is not and I think it has something to do with
    the HTTP links for either the Oracle core and/or XML TAGLIBs. Either that or the W3.org has
    outdated XSLT http links.
    Anyone know if changes have been made to any of these taglib links?
    This in the JSP
    <!--
    <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <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}" />
    -->
    This in the XSL
    <!--
    <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    -->
    And the other JSP having the same problem.
    <!--
    <%@ page contentType="text/html;charset=windows-1252"
    import="java.util.List, qsbqar.XMLHandler, org.w3c.dom.NodeList,
    javax.xml.transform.*, javax.xml.transform.stream.*,
    org.w3c.dom.Node, oracle.xml.parser.v2.*, java.io.File,
    java.io.FileReader " %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
    <xsl:param name="employeeID" value="2"/>
    <%session.setAttribute("employee_ID", request.getParameter("consultantID")); %>
    <c:import url="HoursWorked.xml" var="xmlHoursWorked" charEncoding="windows-1252"/>
    <c:import url="./HoursWorked4.xsl" var="xslt" charEncoding="windows-1252"/>
    <x:transform xml="${xmlHoursWorked}" xslt="${xslt}">
    <x:param name="employeeID" value="${sessionScope.employee_ID }"/>
    </x:transform>
    -->
    Edited by: B of Carbon on Dec 19, 2010 12:25 AM

  • Weblogic 6.0  deplying ear, xml parsing error occurs in a repeating deployment of the files !

    Hello there !
    I am using WLS 6.0 and deploying our application (developed on jboss)
    now on weblogic.I am receiving the attached message at the end of this
    mail. The Strange thing is, it keeps compiling and generating
    wl_comp<nnnnnn>.ear files non-stop in the wl_temp_do_not_delete
    directory. I have to delete the ear file that this behavior will stop.
    so two questions:
    - is there a way to stop this "repeating" behavior, because it only
    uses diskpace? Is this a bug in the 6.0 version?
    - what exactly is this error, what I have done wrong in my ear, which
    xml ?
    Thanks for your time.
    Regards
    Mark
    Weblogic Error Message (taken from the log file):
    Apr 18, 2002 2:49:03 PM CEST Info Management
    MBean=(BankingCSFB:Name=seprosift,Type=Application)
    Attribute=(LastModified) modified from (1019134139382) to
    (1019134143132).
    Apr 18, 2002 2:49:03 PM CEST Error Management Error parsing XML
    descriptor for application BankingCSFB:Name=seprosift,Type=Application
    weblogic.xml.process.ProcessorFactoryException: XML document does not
    appear to contain a properly formed DOCTYPE header
         at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:189)
         at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:164)
         at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:83)
         at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:67)
         at weblogic.management.mbeans.custom.Application.getDD(Application.java:358)
         at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:284)
         at weblogic.management.mbeans.custom.Application.load(Application.java:230)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
         at $Proxy15.load(Unknown Source)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:528)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
         at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
         at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)
    --------------- nested within: ------------------
    weblogic.xml.process.XMLProcessingException: XML document does not
    appear to contain a properly formed DOCTYPE header - with nested
    exception:
    [weblogic.xml.process.ProcessorFactoryException: XML document does not
    appear to contain a properly formed DOCTYPE header]
         at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:85)
         at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:67)
         at weblogic.management.mbeans.custom.Application.getDD(Application.java:358)
         at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:284)
         at weblogic.management.mbeans.custom.Application.load(Application.java:230)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
         at $Proxy15.load(Unknown Source)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:528)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:504)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:428)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:380)
         at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
         at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)

    These links may be useful
    Oracle JDBC 2.0 Connector configuration
    http://help.sap.com/saphelp_nw04/helpdata/en/5f/3733418bb16e24e10000000a155106/content.htm

  • WebLogic's High-Performance XML parser

    I understand that 6.1's high performance XML parser is the replacement of 6.0's
    custom generated parser. Per the documentation, I need to set SAXParserFactory
    to weblogic.xml.babel.jaxp.SAXParserFactoryImpl, but I couldn't find weblogic/xml/babel/jaxp/SAXParserFactoryImpl
    in either weblogic.jar or xmlx.jar. There are bunch of weblogicx/xml/babel/* in
    xmlx.jar.
    When I call JAXP code, I got this error:
    javax.xml.parsers.FactoryConfigurationError: Failed to find SAXParserFactory.
    weblogic.xml.babel.jaxp.SAXParserFactoryImpl
    javax.xml.parsers.FactoryConfigurationError: Failed to find SAXParserFactory.
    weblogic.xml.babel.jaxp.SAXParserFactoryImpl
    Am I missing something, or the 6.1 beta download forget to include the *.babel.jaxp.*
    stuff?
    Jim Zhou.

    Jim,
    Please don't use System.setProperty() in any server code. This was intended
    as an example only. I think the XMLReaderFactory is not specified in
    JAXP1.1.
    Thanks,
    Chris
    "Chris Fry" <[email protected]> wrote in message
    news:[email protected]...
    Jim,
    Here is a code fragment to acess the parser:
    System.setProperty("javax.xml.parsers.SAXParserFactory","weblogic.xml.babel.
    jaxp.SAXParserFactoryImpl");
    SAXParserFactory factory = SAXParserFactory.newInstance();
    SAXParser parser = factory.newSAXParser();
    parser.parse("yourfile.xml",defaultHandler);
    "Jim Zhou" <[email protected]> wrote in message
    news:[email protected]...
    I just found out that XML Registry setting on SAXParserFactory does notapply to
    XMLReaderFactory() and XMLReader:
    XMLReader parser = XMLReaderFactory.createXMLReader();
    I have to use SAXParserFactory to get High Performance Parser kicked in:
    SAXParserFactory factory = SAXParserFactory.newInstance();
    SAXParser parser = factory.newSAXParser();
    Is this the right behavior? Thanks for the help.
    Jim Zhou.
    "Jim Zhou" <[email protected]> wrote:
    Chris,
    Thanks for the reply. It still doesn't work. I think the problem is
    that weblogic.jar
    and xmlx.jar both does not have eihter
    "weblogicx.xml.babel.jaxp.SAXParserFactoryImpl"
    or "weblogic.xml.babel.jaxp.SAXParserFactoryImpl". So the current Beta
    download
    forgot to include the above classes. I might try download Beta again
    to see if
    any difference.
    Regards,
    Jim Zhou.
    "Chris Fry" <[email protected]> wrote:
    Jim,
    This is a mismatch between our beta and the final place that the
    parser
    will
    live in the release, you should be able to get the parser by setting
    the
    SAXParserFactory to weblogicx.xml.babel.jaxp.SAXParserFactoryImpl (it
    will
    be weblogic.xml.babel.jaxp.SAXParserFactoryImpl in the final release).
    A couple notes:
    The parser only handles standalone documents, with no entityreferences
    and
    is optimized for small to midsize documents (IE soap and wsdl type
    documents).
    Pleas let me know if you can get it to work.
    Chris
    "Jim Zhou" <[email protected]> wrote in message
    news:[email protected]...
    I understand that 6.1's high performance XML parser is the
    replacement
    of
    6.0's
    custom generated parser. Per the documentation, I need to setSAXParserFactory
    to weblogic.xml.babel.jaxp.SAXParserFactoryImpl, but I couldn't findweblogic/xml/babel/jaxp/SAXParserFactoryImpl
    in either weblogic.jar or xmlx.jar. There are bunch ofweblogicx/xml/babel/* in
    xmlx.jar.
    When I call JAXP code, I got this error:
    javax.xml.parsers.FactoryConfigurationError: Failed to findSAXParserFactory.
    weblogic.xml.babel.jaxp.SAXParserFactoryImpl
    javax.xml.parsers.FactoryConfigurationError: Failed to findSAXParserFactory.
    weblogic.xml.babel.jaxp.SAXParserFactoryImpl
    Am I missing something, or the 6.1 beta download forget to includethe
    *.babel.jaxp.*
    stuff?
    Jim Zhou.

  • Weblogic 6.1 and xml parser empty elements

    FYI, It looks like Weblogic changed there xml parser in the transition from
    6.0sp2 to 6.1. Example : The empty Extra Info Class produced and error,
    because it is empty. Where in 6.0sp2 it did not produce and error:
    <taglib>
    <tag>
    <name>indexProperty</name>
    <info>
    some info..
    </info>
    <tagclass>com.pssg.jsp.tags.IndexPropertyTag</tagclass>
    <teiclass></teiclass>
    </tag>
    </taglib>
    ####<Aug 20, 2001 12:20:52 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101047>
    <[WebAppServletContext(7008653,cam,/cam)] resolved taglib uri '/pssglibtags'
    to taglib-location /WEB-INF/tlds/pssgtaglib.tld:>
    ####<Aug 20, 2001 12:20:53 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101160> <Deployment
    descriptor is malformed, check against the DTD:
    org.xml.sax.SAXParseException: The content of element type "tag" must match
    "(name,tagclass,teiclass?,bodycontent?,info?,attribute*)"..>
    ####<Aug 20, 2001 12:20:53 PM PDT> <Error> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101020>
    <[WebAppServletContext(7008653,cam,/cam)] Servlet failed with Exception>
    weblogic.servlet.jsp.JspException: (line 1): Error in using tag library
    uri='/pssglibtags' prefix='pssglibtag': For tag 'indexProperty', cannot load
    extra info class ''
    at
    weblogic.servlet.jsp.StandardTagLib.tld_jspException(StandardTagLib.java:901
    -Scot

    hi,
    there are two versions of ldap supported in wls6.1 , ldapv1 and ldavp2
    ldap v1 only has the functionality of listing groups.
    but where ldapv2 doesn't have that functionality,
    by looking at your config , it seems you are using ldap v2..
    if u need that functionality u can use ldapv1.
    thanks
    kiran
    "Bert Cliche" <[email protected]> wrote in message
    news:[email protected]..
    Per a proof of concept, I am having trouble getting WL6.1 to see
    group members as defined in iPlanet LDAP. I can see the groups,
    but modifies to create groups only create them in the local DB.
    Created users also only get placed in the local DB. I can bind
    for searches as Directory Manager via ldapsearch and run queries,
    and the DS gateway works fine. I can dump the LDIF file and the
    entries look fine.
    I copied and modified the template for the Netscape server and
    have the realm setup per the GUI.
    For sanity, everything is very generic as:
    the Root DN is "o=test.org"
    and my "Configuration" part from the config.xml looks like:
    server.authprotocol=simple;
    server.host=localhost;
    membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));
    server.port=390;
    group.dn=o=test.org;
    group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
    server.principal=cn=Directory Manager;
    user.dn=o=test.org;
    server.groupiscontext=false;
    user.filter=(&(uid=%u))
    I added the "authprotocol" as a guess. Note that the server is
    running on port 390, this is not a typo.
    Any ideas what is going wrong?

  • NullPointerException from weblogic.i18ntools.l10ngen

    Using the environment for the example server (on winNT)...
    Go to \bea\wlserver6.1_beta\samples\examples\i18n\logging and run
    build. The build go boom with the following stack track...
    D:\bea\wlserver6.1_beta\samples\examples\i18n\logging>java weblogic.i18ntools.l1
    0ngen -verbose -d d:\bea\wlserver6.1_beta\config\examples\clientclasses ..\msgca
    t\I18nLog.xml ..\msgcat\I18nSimple.xml
    Parsing catalog, D:\bea\wlserver6.1_beta\samples\examples\i18n\msgcat\fr\I18nLog
    .xml
    java.lang.NullPointerException
    java.lang.NullPointerException
    at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:25)
    at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:130)
    at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:99)
    at weblogic.i18ntools.L10nLookup$Logger.<init>(L10nLookup.java:282)
    at weblogic.i18ntools.L10nLookup.<init>(L10nLookup.java:114)
    at weblogic.i18ntools.L10nLookup.init(L10nLookup.java:70)
    at weblogic.i18ntools.L10nLookup.getL10n(L10nLookup.java:58)
    at weblogic.i18ntools.parser.LocaleLogMessage.validate(LocaleLogMessage.
    java:65)
    at weblogic.i18ntools.parser.LocaleMessageCatalog.validate(LocaleMessage
    Catalog.java:240)
    at weblogic.i18ntools.parser.LocaleCatalogParser.endDocument(LocaleCatal
    ogParser.java:175)
    at org.xml.sax.helpers.XMLReaderAdapter.endDocument(XMLReaderAdapter.java:286)
    at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1
    230)
    at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument
    (XMLValidator.java:1064)
    at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatc
    her.dispatch(XMLDocumentScanner.java:1555)
    at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
    mentScanner.java:381)
    at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
    at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
    at weblogic.i18ntools.parser.LocaleCatalogParser.parse(LocaleCatalogPars
    er.java:126)
    at weblogic.i18ntools.l10ngen.parseIt(l10ngen.java:327)
    at weblogic.i18ntools.l10ngen.buildLangOutputs(l10ngen.java:302)
    at weblogic.i18ntools.l10ngen.generate(l10ngen.java:406)
    at weblogic.i18ntools.l10ngen.run(l10ngen.java:423)
    at weblogic.i18ntools.l10ngen.main(l10ngen.java:459)
    java.lang.NullPointerException
    weblogic.i18n.tools.GenException: Code gen exception: Parse failed for: D:\bea\w
    lserver6.1_beta\samples\examples\i18n\logging\..\msgcat\fr\I18nLog.xml

    Lauren,
    Actually, it does not appear as though the example itself is
    broken. The example looks the same as the one that worked fine under
    WLS 6.0. The example seems to expose a something that is broken (a
    regression?) in the codegen tool or in the API.
    Ben
    On 20 Jun 2001 11:31:02 -0800, Lauren Wright <[email protected]> wrote:
    >
    Ben,
    I forwarded your message to the appropriate group.
    Would you mind reposting to the examples newsgroup?
    Lauren
    [email protected] (Ben Eng) wrote:
    Using the environment for the example server (on winNT)...
    Go to \bea\wlserver6.1_beta\samples\examples\i18n\logging and run
    build. The build go boom with the following stack track...
    D:\bea\wlserver6.1_beta\samples\examples\i18n\logging>java weblogic.i18ntools.l1
    0ngen -verbose -d d:\bea\wlserver6.1_beta\config\examples\clientclasses
    ..\msgca
    t\I18nLog.xml ..\msgcat\I18nSimple.xml
    Parsing catalog, D:\bea\wlserver6.1_beta\samples\examples\i18n\msgcat\fr\I18nLog
    ..xml
    java.lang.NullPointerException
    java.lang.NullPointerException
    at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:25)
    at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:130)
    at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:99)
    at weblogic.i18ntools.L10nLookup$Logger.<init>(L10nLookup.java:282)
    at weblogic.i18ntools.L10nLookup.<init>(L10nLookup.java:114)
    at weblogic.i18ntools.L10nLookup.init(L10nLookup.java:70)
    at weblogic.i18ntools.L10nLookup.getL10n(L10nLookup.java:58)
    at weblogic.i18ntools.parser.LocaleLogMessage.validate(LocaleLogMessage.
    java:65)
    at weblogic.i18ntools.parser.LocaleMessageCatalog.validate(LocaleMessage
    Catalog.java:240)
    at weblogic.i18ntools.parser.LocaleCatalogParser.endDocument(LocaleCatal
    ogParser.java:175)
    at org.xml.sax.helpers.XMLReaderAdapter.endDocument(XMLReaderAdapter.java:286)
    at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1
    230)
    at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument
    (XMLValidator.java:1064)
    at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatc
    her.dispatch(XMLDocumentScanner.java:1555)
    at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
    mentScanner.java:381)
    at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
    at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
    at weblogic.i18ntools.parser.LocaleCatalogParser.parse(LocaleCatalogPars
    er.java:126)
    at weblogic.i18ntools.l10ngen.parseIt(l10ngen.java:327)
    at weblogic.i18ntools.l10ngen.buildLangOutputs(l10ngen.java:302)
    at weblogic.i18ntools.l10ngen.generate(l10ngen.java:406)
    at weblogic.i18ntools.l10ngen.run(l10ngen.java:423)
    at weblogic.i18ntools.l10ngen.main(l10ngen.java:459)
    java.lang.NullPointerException
    weblogic.i18n.tools.GenException: Code gen exception: Parse failed for:
    D:\bea\w
    lserver6.1_beta\samples\examples\i18n\logging\..\msgcat\fr\I18nLog.xml

  • XML Parsing Error: no element found

    Hi,
    I'm working with BIPublisher 11g and I'm having the following error, this error occurred when I'm in the report and try to get the XML :
    XML Parsing Error: no element found
    Location: http://172.16.10.46:9704/xmlpserver/servlet/xdo
    Line Number 4, Column 1:
    And this is the DataEngine log I got:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <debugLog>
    - <msg time="2010-09-29T13:49:03.619+13:00" comp_id="bi_server1" type="NOTIFICATION" level="1" host_id="birepo.nzbus.net" host_addr="172.16.10.46" module="oracle.xdo" tid="45" user="<anonymous>" ecid="0000IhQxgQ15qYG6yzZf6G1Cbv8m0003n8" rid="0">
    <attr name="APP" value="bipublisher#11.1.1.3.0" />
    <txt>ReportModelContextImpl- Invoking dataengine dataprocessor..</txt>
    </msg>
    - <msg time="2010-09-29T13:49:03.817+13:00" comp_id="bi_server1" type="WARNING" level="1" host_id="birepo.nzbus.net" host_addr="172.16.10.46" module="oracle.xdo" tid="45" user="<anonymous>" ecid="0000IhQxgQ15qYG6yzZf6G1Cbv8m0003n8" rid="0">
    <attr name="APP" value="bipublisher#11.1.1.3.0" />
    <txt>java.lang.NullPointerException at oracle.xdo.dataengine.perf.StringPoolList.cleanup(StringPoolList.java:55) at oracle.xdo.dataengine.XMLPGEN.cleanup(XMLPGEN.java:1729) at oracle.xdo.dataengine.XMLPGEN.writeXMLDataStructure(XMLPGEN.java:220) at oracle.xdo.dataengine.XMLPGEN.processDataSet(XMLPGEN.java:1390) at oracle.xdo.dataengine.XMLPGEN.processMergedDataSet(XMLPGEN.java:1203) at oracle.xdo.dataengine.DataProcessor.processData(DataProcessor.java:365) at oracle.xdo.servlet.dataengine.DataProcessor.processData(DataProcessor.java:402) at oracle.xdo.servlet.dataengine.DataProcessor.processData(DataProcessor.java:389) at oracle.xdo.online.data.ClassicDataProcessor.process(ClassicDataProcessor.java:157) at oracle.xdo.servlet.ReportModelContextImpl.getReportXMLData(ReportModelContextImpl.java:188) at oracle.xdo.servlet.CoreProcessor.process(CoreProcessor.java:301) at oracle.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:87) at oracle.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:1038) at oracle.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:603) at oracle.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:440) at oracle.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:419) at oracle.xdo.servlet.XDOServlet.doGet(XDOServlet.java:235) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.xdo.servlet.metadata.track.MostRecentFilter.doFilter(MostRecentFilter.java:64) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:116) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.xdo.servlet.init.InitCheckingFilter.doFilter(InitCheckingFilter.java:63) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)</txt>
    </msg>
    - <msg time="2010-09-29T13:49:03.818+13:00" comp_id="bi_server1" type="NOTIFICATION" level="1" host_id="birepo.nzbus.net" host_addr="172.16.10.46" module="oracle.xdo" tid="45" user="<anonymous>" ecid="0000IhQxgQ15qYG6yzZf6G1Cbv8m0003n8" rid="0">
    <attr name="APP" value="bipublisher#11.1.1.3.0" />
    <txt>Data Generation Completed...</txt>
    </msg>
    - <msg time="2010-09-29T13:49:03.818+13:00" comp_id="bi_server1" type="NOTIFICATION" level="1" host_id="birepo.nzbus.net" host_addr="172.16.10.46" module="oracle.xdo" tid="45" user="<anonymous>" ecid="0000IhQxgQ15qYG6yzZf6G1Cbv8m0003n8" rid="0">
    <attr name="APP" value="bipublisher#11.1.1.3.0" />
    <txt>Total Data Generation Time 0.0 seconds</txt>
    </msg>
    </debugLog>
    Any suggestions.
    Thanks,

    Hi,
    I am getting the same error.
    Do we have a fix for this? The query was working fine until recently. But has started failing now with dataengine log same as above.
    Is there any solution?
    Thanks,
    Divya
    Edited by: 900143 on May 29, 2012 2:03 AM

  • XML parsing problem

    Hi, my problem is :
    In my Application i want to parse an XML file with DOM parser. The problem is that in my Project "MyProject -> Project Properties -> Libraries and Classpath"
    I have included some 15 libraries which are useful for my Application: ADF Faces Runtime 11, ADF Web Runtime and etc.
    Problems are causing the libraries: BC4J Runtime,ADF Model Runtime, MDS Runtime Dependencies
    because when added my source which is parsing an XML file stops working.The source code is:
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
    DocumentBuilder db = dbf.newDocumentBuilder();
    File file =
    new File("C:\\Documents and Settings\\ilia\\Desktop\\begin.xml");
    Document doc = db.parse(file);
    Element root = doc.getDocumentElement();
    NodeList dots = root.getElementsByTagName("w:t");
    Element firstDot = (Element)dots.item(0);
    String textValue = firstDot.getFirstChild().getNodeValue();
    I use DOM because i need to change some values in the XML file, but its not working neither for reading nor for writing.When debugging I see that it gets the root of the xml but " firstDot.getFirstChild().getNodeValue() " returns null and it breaks with NullPointerException. And that's only when the libraries mentioned above are added to the project. Without them it works just fine !
    I don't know, it's like when added the parser validates my xml against some schema and returns null.
    The xml file is very simple MS Word Document saved as .xml .But I don't think that's the problem.
    Thanks in advance !
    iliya

    Hi all,
    I found the solution to my problem.The right way to parse and change an XML file with DOM parser using the Oracle XML Parser v2 should look like this:
    JXDocumentBuilderFactory factory =
    (JXDocumentBuilderFactory)JXDocumentBuilderFactory.newInstance();
    JXDocumentBuilder documentBuilder =
    (JXDocumentBuilder)factory.newDocumentBuilder();
    File file = new File("c:/Documents and Settings/ilia/Desktop/begin.xml");
    InputStream input =
    new FileInputStream(file);
    XMLDocument xmlDocument = (XMLDocument)(documentBuilder.parse(input));
    System.out.println("Encoding: " + xmlDocument.getEncoding());
    System.out.println("Version: " + xmlDocument.getVersion());
    NodeList namespaceNodeList =
    xmlDocument.getElementsByTagNameNS("http://schemas.microsoft.com/office/word/2003/wordml","t");
    XMLElement namespaceElement17 = (XMLElement)namespaceNodeList.item(17);
    namespaceElement17.getFirstChild().setNodeValue("someString");

  • XML Parsing Error: no element found Location:Line Number 1, Column 1:

    Hi,
    i have a servlet code in which i am using bouncy castle encryption algorithm , if i tried to run that servlet on embeded weblogic server than my servlet works fine without error.
    but if i deploy same Servlet code on SOA domain console than i get following error.
    XML Parsing Error: no element found
    Location: http://localhost:7001/Encryption-PGPEncrypt-context-root/pgpservlet
    Line Number 1, Column 1:
    Please help me friends...

    Hi Chandra,
    Based on my research, the error message is only generated by FireFox when the render page is blank in Internet. For some reason, .NET generates a response type of "application/xml" when it creates an empty page. Firefox parses the file as XML and finding
    no root element, spits out the error message.
    Also, based on your description, the other sites are opened correctly, the issue only happened in Central Administration(CA). This means the SharePoint services are working fine.
    Since this issue only occurred in the CA, it might be due the application pool for the CA is corrupted. Please try to restart the application pool for the CA to resove the issue:
    1. Open Internet Information Service(IIS)
    2. List the application pools
    3. Select the application pool used for the CA
    4. Stop it, and then start it again.
    Note, if the application pool is running in Classic mode, please change it to be Integrated mode.
    Additionally, I found a similar thread, which may help you too:
    http://social.msdn.microsoft.com/Forums/en/sharepoint2010general/thread/824d7dda-db03-452b-99c4-531c5c576396
    If you have any more questions, please feel free to ask.
    Thanks,
    Jin Chen
    Jin Chen - MSFT

  • 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

  • Error message while loading XML parser into db

    I get the following error message while loading xmlparserv2.jar
    ORA-29534 referenced object SYSTEM.oracle/xml/parser/v2/XMLNOde could not be resolved
    ORA-29545: badly formed class: java.lang.NullPointerException
    using XSU111 package

    I had the same problem. I did a search of the forum looking for the error number (that's how I ran across your question). It seems that the xmlparserv2.jar (v2.0.2.8 or 2.0.2.9) which is included was compiled with java 1.2 which is incompatible with Oracle 8.1.5 (which is what I have and probably what you have). You probably need xmlparser v2.0.2.7.
    Do a search on the error number, the post is from Steve back on June 8. I found the correct version of the xmlparserv2.jar in my copy of the xmlschema stuff (xmlschema_v0_9_0_0.zip). I don't know which version is in the current xmlschema
    (v1.0.0.0) but it is probably the new version.
    Steve will email you the correct version if you ask.
    Eric
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by nrajav ():
    I get the following error message while loading xmlparserv2.jar
    ORA-29534 referenced object SYSTEM.oracle/xml/parser/v2/XMLNOde could not be resolved
    ORA-29545: badly formed class: java.lang.NullPointerException
    using XSU111 package<HR></BLOCKQUOTE>
    null

Maybe you are looking for