XML Parser Exception on Punch Out Setup Request

I am on the supplier side of the procurement process. Recently I was tasked with bringing on a new buying group, but we have encountered a strange issue. The buyer set up my company in their ERP system, however they are getting an error when trying to punch out to my website...which is listed below.
Error Code: 400 Invalid XML Format In Login Response Document Unable to parse the Login Response XML.
XMLParserException
oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'meta'.
at oracle.xml.parser.v2.XMLError.flushErrors1
After some investigation, I am confident the problem resides in the buyers BrowserFormPost URL. The problem seems to be that instead of using "&" for ampersand between the URL variables, it is passing in the & symbol (& is a protected character in XML), which is causing the Oracle XML parser to throw this exception. As a result, the set up request is never getting to me.
The buyer has opened a couple of tickets now with Oracle support, but both times the ticket has been closed and the buyer has been instructed to contact the supplier (me). I don't know enough about the buyer side Oracle system to instruct them on how to fix this issue. Any help would be greatly appreciated.

Hi Rakesh,
You need to have an S-User ID to access SAP Notes. For your convenience, I am pasting the content of SAP Note 954035.
Process, block and CO could not be created in GP
Symptom
After upgrade of SAP-EU component to version 7.0 SP8 in Guided Procedures process, block and callable object could not be created. On design time screen   appears error message:
com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
During attempt to start process through the Runtime screen you will get an error message:
Cannot load callable object container:
Failed to get Related Model Object for the object
com.sap.caf.eu.gp.ui.actions.decpage.
CDecisionPageInterfaceViewdecisionPageUsage1,relation View
In SP9, the following message could be found:
Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.co.exec.decision.COExecDecision
Proceed as stated for SP8.
Other terms
This is WebDynpro problem caused by an inconsistency of versions.
Solution
      1. Redeploy the SCA SAP-EU (if redeployment does not help undeploy and deploy again) components:
          o caf/eu/gp/ui/dt/comp/cons,
          o caf/eu/gp/ui/dt/comp and
          o caf/eu/gp/ui/actions  from software component SAP-EU
or
      2. Apply the SP8 patch 1 if you upgrade to SP8. Both components mentioned below will be updated:
          o caf/eu/gp/ui/dt/comp/cons
          o caf/eu/gp/ui/dt/comp
See if it solves your problem.
Bye
Ankur

Similar Messages

  • XML Parser Exception in Install of AIA 11.1.1.5 on SOA 11.1.1.5

    I am attempting to install AIA Foundation Pack on a SOA domain and continually encounter an XML parsing exception error as the installer is attempting to install WSM security policies. Here are the key details:
    AIA version = 11.1.1.5
    SOA Suite = 11.1.1.5
    WebLogic = 10.3.5
    Operating System = Fedora14 (a home lab machine but I don't think this is an OS issue)
    The error is encountered about 17 minutes into the lengthy process. Just before the error appears in the installation log, the following message appears indicating roughly what step is being performed:
    [zip] Building zip: /opt/oraclemw/aia11115/aia_instances/dev1/tmp/aia_security_policies.zip
    The core error messages are:
    [exec] SEVERE: WSM-01605 XML parser exception
    [exec] oracle.xml.parser.v2.XMLParseException: Expected 'EOF'.
    [exec] at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
    The python modules being executed by the WLST scripting tool at the time of the failure are:
    [exec] Problem invoking WLST - Traceback (innermost last):
    [exec] File "/opt/oraclemw/aia11115/Infrastructure/Install/AID/lib/py/importpolicy.py", line 29, in ?
    [exec] File "/opt/oraclemw/oracle_common/common/wlst/wsmManage.py", line 719, in importRepository
    [exec] File "/opt/oraclemw/oracle_common/common/wlst/lib/ora_util.py", line 51, in raiseScriptingException
    [exec] OracleScriptingException: None
    Finally, the outer XML files being used as input for the deployer that seems to be running at the time are:
    /opt/oraclemw/aia11115/Infrastructure/Install/AID/AIAExecuteDriver.xml
    with references to lines 221 and 64.
    The problem occurs whether I try to use Java JDK 16.0.20 or JRockit R28.2.0 as the JRE when running the AIA installer. (The WebLogic domain is configured to use JRockit).
    Any suggestions? Is there a library conflict being picked up between different releases of XercesImpl? I would hope there isn't actually a bad XML file in the AIA artifacts or WSM (Web Service Management) policies being deployed.

    HI
    How this issue was resolved? Please explain in detail. I am facing the same issue.
    Regards
    Arun

  • XML parser Exception

              Hi
              I try to deploy a servlet that serve as a MapPoint web services client. So the
              servlet receive a post with latitude and longitude then it try it to retrieve
              a Map showing the location from MapPoint through web services. I am able to deploy
              the servlet, but it throws the following exception when it receives a request.
              java.lang.RuntimeException: ; nested exception is:
                   org.xml.sax.SAXParseException: The root element is required in a well-formed
              document.
                   at com.spatialpoint.mappoint.storelocator.StoreLocator.getAddressMatches(StoreLocator.java:266)
                   at jsp_servlet.__locate._jspService(__locate.java:181)
                   at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
                   at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
                   at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
              Any help will be very much appreciated. Thanks
              

    If you're using the XMLTYPE constructor to insert your XML into the DB you can avoid the well-formed validation declaring that the xml is well formed:
    SQL> insert into MYXMLTABLE values (
      2  XMLTYPE('
      3  <ROOT a="1" a="3"/>
      4  ',null,0,1));
    1 row created.Oracle inserts the xml in the table but, obvoiusly, you'll never be able to use it as an XML file:
    SQL> select object_value
      2  from MYXMLTABLE ;
    OBJECT_VALUE
    <ROOT a="1" a="3"/>
    SQL> select extract(object_value,'/*')
      2  from MYXMLTABLE ;
    ERROR:
    ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00224: multiple occurrences of attribute "a" found
    Error at line 8Max
    [My Italian Oracle blog|http://oracleitalia.wordpress.com/2010/01/31/le-direttive-di-compilazione-pragma/]

  • XML parser exception: No documentation !

    Hi,
    I'm getting an exception when looking for
    an <xsl:apply-templates> tag in an XSL file
    thats loaded via the DOMParser.
    Do I need to do anything special to declare
    the XSL Namespace?
    Also, the Parser API docs don't seem to have
    this Exception listed!!!
    Does anyone know more regarding this?
    TIA,
    Vijay
    oracle.xml.parser.v2.XPathException: Namespace prefix 'xsl' used but not declared.
    at oracle.xml.parser.v2.XSLParseString.nextToken(XSLParseString.java:406)
    at oracle.xml.parser.v2.PathExpr.<init>(XSLNodeSetExpr.java:313)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:147)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:131)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:124)
    at oracle.xml.parser.v2.UnaryExpr.parse(XSLExpr.java:357)
    at oracle.xml.parser.v2.MultiplicativeExpr.parse(XSLExpr.java:295)
    at oracle.xml.parser.v2.AdditiveExpr.parse(XSLExpr.java:243)
    at oracle.xml.parser.v2.RelExpr.parse(XSLExpr.java:210)
    at oracle.xml.parser.v2.EqualExpr.parse(XSLExpr.java:160)
    at oracle.xml.parser.v2.AndExpr.parse(XSLExpr.java:110)
    at oracle.xml.parser.v2.XSLExpr.parse(XSLExpr.java:59)
    at oracle.xml.parser.v2.FilterExpr.getPrimaryExpr(XSLNodeSetExpr.java:1444)
    at oracle.xml.parser.v2.FilterExpr.<init>(XSLNodeSetExpr.java:1128)
    at oracle.xml.parser.v2.PathExpr.<init>(XSLNodeSetExpr.java:275)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:147)
    at oracle.xml.parser.v2.XSLNodeSetExpr.parse(XSLNodeSetExpr.java:131)
    at oracle.xml.parser.v2.XSLExprBase.createNodeSetExpr(XSLExprBase.java:123)
    at oracle.xml.parser.v2.XMLNode.selectNodes(XMLNode.java:763)
    at oracle.xml.parser.v2.XMLNode.selectSingleNode(XMLNode.java:861)
    at com.citicorp.gra.portlets.fxrates.FxRatesPortletContentProvider.createStylesheet(FxRatesPortletContentProvider.java:302)
    at com.citicorp.gra.portlets.fxrates.FxRatesPortletContentProvider.getStylesheet(FxRatesPortletContentProvider.java:341)
    at com.citicorp.gra.portlets.fxrates.FxRatesPortletContentProvider.getContent(FxRatesPortletContentProvider.java:125)
    at portlet.BasePortlet.doPost(BasePortlet.java:100)
    at portlet.BasePortlet.doGet(BasePortlet.java:137)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1013)
    at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:925)
    at allaire.jrun.servlet.JRunNamedDispatcher.include(JRunNamedDispatcher.java:42)
    at allaire.taglib.ServletTag.doEndTag(ServletTag.java:84)
    at jrun__html__fxrates__tagtest2ejsp19._jspService(jrun__html__fxrates__tagtest2ejsp19.java:53)
    at allaire.jrun.jsp.HttpJSPServlet.service(HttpJSPServlet.java:40)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1013)
    at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:925)
    at allaire.jrun.servlet.JRunNamedDispatcher.forward(JRunNamedDispatcher.java:34)
    at allaire.jrun.jsp.JSPServlet.service(JSPServlet.java:175)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1013)
    at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:925)
    at allaire.jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:88)
    at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1131)
    at allaire.jrun.servlet.JvmContext.dispatch(JvmContext.java:330)
    at allaire.jrun.jrpp.ProxyEndpoint.run(ProxyEndpoint.java:367)
    at allaire.jrun.ThreadPool.run(ThreadPool.java:272)
    at allaire.jrun.WorkerThread.run(WorkerThread.java:75)
    null

    Hi
    below is the statement which is looking
    for the "xsl:app-templates" element under
    node1, it need an instance of NSResolver.
    XMLElement node1Child2 = (XMLElement) node1.selectSingleNode ("//xsl:apply-templates", resolver );
    // Name Space Resolver
    private class MyNSResolver implements NSResolver {
    * returns the Namespace definition int scope for a given namespace prefix
    public String resolveNamespacePrefix( String prefix ) {
    if ( prefix.equals("xsl")) {
    return "http://www.w3.org/1999/XSL/Transform";
    } else return null;
    } // private class MyNSResolver
    null

  • XML Parse Exception

    Hi All,
    I am trying to parse the xml which is shown below but i am getting following exception, is there any wrong in format of xml.
    code:
    <abo:CodeCombinationsResponse xmlns:abo="http://xmlns.oracle.com/ApplicationObjects/Ebiz/Core/ABO/ChartOfAccounts/V1"><abo:CodeCombinationId>11111</abo:CodeCombinationId><abo:ReasonCode>111 segment 1</abo:ReasonCode><abo:ReasonCode> 111 segment 2</abo:ReasonCode></abo:CodeCombinationsResponse> <abo:CodeCombinationsResponse xmlns:abo="http://xmlns.oracle.com/ApplicationObjects/Ebiz/Core/ABO/ChartOfAccounts/V1"><abo:CodeCombinationId>22222</abo:CodeCombinationId><abo:ReasonCode>222 segment 1</abo:ReasonCode><abo:ReasonCode> 222 segment 2</abo:ReasonCode></abo:CodeCombinationsResponse>
    Error:
    oracle.xml.parser.v2.XMLParseException: Expected 'EOF'.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:312)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    at oracle.apps.xla.fsahint.server.XMLGeneratorClass.parseXML(XMLGeneratorClass.java:132)
    at oracle.apps.xla.fsahint.server.XMLGeneratorClass.main(XMLGeneratorClass.java:42)
    Please suggest.
    thanks in advance,
    Rakesh.

    You can only have one root tag.
    Your xml looks like this:
    <abo:CodeCombinationsResponse
         xmlns:abo="http://xmlns.oracle.com/ApplicationObjects/Ebiz/Core/ABO/ChartOfAccounts/V1">
         <abo:CodeCombinationId>11111</abo:CodeCombinationId>
         <abo:ReasonCode>111 segment 1</abo:ReasonCode>
         <abo:ReasonCode>111 segment 2</abo:ReasonCode>
    </abo:CodeCombinationsResponse>
    <abo:CodeCombinationsResponse
         xmlns:abo="http://xmlns.oracle.com/ApplicationObjects/Ebiz/Core/ABO/ChartOfAccounts/V1">
         <abo:CodeCombinationId>22222</abo:CodeCombinationId>
         <abo:ReasonCode>222 segment 1</abo:ReasonCode>
         <abo:ReasonCode>222 segment 2</abo:ReasonCode>
    </abo:CodeCombinationsResponse>Wrap this in a root tag. Example:
    <abo:CodeCombinationsResponses>
         <abo:CodeCombinationsResponse
              xmlns:abo="http://xmlns.oracle.com/ApplicationObjects/Ebiz/Core/ABO/ChartOfAccounts/V1">
              <abo:CodeCombinationId>11111</abo:CodeCombinationId>
              <abo:ReasonCode>111 segment 1</abo:ReasonCode>
              <abo:ReasonCode>111 segment 2</abo:ReasonCode>
         </abo:CodeCombinationsResponse>
         <abo:CodeCombinationsResponse
              xmlns:abo="http://xmlns.oracle.com/ApplicationObjects/Ebiz/Core/ABO/ChartOfAccounts/V1">
              <abo:CodeCombinationId>22222</abo:CodeCombinationId>
              <abo:ReasonCode>222 segment 1</abo:ReasonCode>
              <abo:ReasonCode>222 segment 2</abo:ReasonCode>
         </abo:CodeCombinationsResponse>
    </abo:CodeCombinationsResponses>- Roy

  • Mapping Error - XML Parser Exception

    We have a scenario where an ABAP Client Proxy sends a message to PI. This message is transformed into the mail package format and an email sent via the mail adapter.
    The Interface Mapping has 2 steps. The 1st step uses an XSL transformation to format the <Content> as html. This step also sets the <Subject>, <To> and <Content_Type> fields. The 2nd step uses a graphical message mapping to dynamically set the <From> field based on the sender system.
    We are experiencing the following intermittent error with this scenario:
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_EUK_MM_MailFrom_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
    This relates to the 2nd mapping step (graphical message mapping) described above.
    The message trace provides the following detail
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity 'lt' undefined(:main:, row:3, col:227) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    This suggests that the XML produced by the XSL transformation is invalid.
    The strange thing is that it is very difficult to replicate the error as it doesn't always occur even with the same payload! If the message is restarted it processes successfully. Testing the interface mapping in the IR, with the same payload, works successfully.
    I would welcome any ideas you may have on this.
    Thanks
    Mark

    Hi Mark,
    thing i know now why it works at "restart".
    When the message comes first you get the character '&lt;' in your xml for example: '&<(0'
    and you get the ParserException.
    Now the message is stored for queueing in the db. I assume the characters are now stored in the 'right way': '&amp;amp;&amp;lt;(0'
    When the message now will be restarted everything works fine.
    Regards,
    Olaf

  • XML parse Exception when running when dynpro

    Hello,
    When I try to run my web dynpro I get the following error.
    org.xml.sax.SAXException: Fatal Error: URI=:main: Line=7: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: = expected in attlist(:main:, row:7, col:50)
    The error occured after I reimported my model. We're on SP13 on both the Developer Studio and WAS.

    I found something interesting on the error page, it seems I'm missing SapDictionaryGenerationCore.
    SapDictionaryGenerationCore 6.4012.00.0000.20050331142541.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:59:41[UTC], changelist=339145, host=PWDFM026.wdf.sap.corp) sap.com/tc~wd~dispwda
    No information available
    sap.com/tc~wd~corecomp
    No information available
    SapDictionaryGenerationTemplates 6.4012.00.0000.20050331142541.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:59:52[UTC], changelist=339145, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4012.00.0000.20050407155601.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:06:39[UTC], changelist=340806, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4012.00.0000.20050414173816.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:53:54[UTC], changelist=342170, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4012.00.0000.20050414173816.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:53:45[UTC], changelist=342170, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4012.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:57:09[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4012.00.0000.20050121170001.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:03:01[UTC], changelist=322883, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4012.00.0000.20050419173537.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:19:03[UTC], changelist=342907, host=PWDFM026)
    SapWebDynproGenerationCore 6.4012.00.0000.20050407155601.0000 (release=630_VAL_REL, buildtime=2005-04-21:20:07:08[UTC], changelist=340806, host=PWDFM026.wdf.sap.corp)

  • XML Parsing exception: org.w3c.dom.ls.LSException

    Hi All,
    <p>We have a WSM(Webservice Management Application) product which will generate a 'Proxy WSDL URL' for a 'Real WSDL URL' and it does security/auditing/logging/routing and other stuffs at runtime while getting a webservice request (on Proxy WSDL) and route it to the Functional(Real WSDL URL - Application server where the actual webservice is deployed) endpoint.
    On receiving response from the functional endpoint, it again comes back to WSM which has to just give the response back to the user unless and until some special policies are attached (like schema validation policy - it will validate the response body based on the schema XSD) </p>
    <p/>
    <p>Here, while reading the response (from functional/application endpoint) over the wire and at the time of creating the actual SoapResponse (XmlResponse) for the end user
    xercesImpl.jar is used to parse the data -lsParser.parse(lsInput); which is throwing the exception <b>"org.w3c.dom.ls.LSException: An invalid XML character (Unicode: 0x16) was found in the element content of the document" </b>when it sees not properly formatted XML at any cause (having incompatible data/special character).</p>
    <p/>
    <p><b>As the exception does not even give enough information like where the XML is corrupt/having incompatible data/special character, we cant have a control to do anything from our application/product side ,as it is third party jar xercesImpl.jar. It would be really very helpful if we
    > either get a option/boolean to turn off the validation logic which is done internally in xercesImpl.jar at the time of parsing 'lsParser.parse(lsInput);'
    > or get additional information in the exception (original cause - like the incompatible/special character (or) a full corrupted response in the exception itself) with which we can get a clue to resolve the issue.</b></p>
    <p/>
    Thanks in Advance
    Priya

    I did a search on Sun site, nothing came back.
    It is on http://xml.apache.org/xerces2-j though.
    You might need to go there and download it. or make sure your
    classpath includes the right jar file.

  • Xml parsing exception

    Hi,
    I am having xml content as a string like below
    <?xml version="1.0" encoding="UTF-8"?>
    <TransactionResponse>
    <InterchangeControlHeader>
    <AuthorInfoQualifier>00</AuthorInfoQualifier>
    <AuthorInformation> </AuthorInformation>
    </InterchangeControlHeader>
    </TransactionResponse>
    I am trying to parse this xml using below code
    factory.setValidating(false);
    factory.setNamespaceAware(true);
    DocumentBuilder builder = factory.newDocumentBuilder();
    StringReader XMLStringReader = new StringReader(xmlString);
    InputSource XMLInputSource = new InputSource(XMLStringReader);
    document = builder.parse(XMLInputSource);
    I am using
    javax.xml.parsers.DocumentBuilderFactory and DocumentBuilder for parsing but i am getting exception
    "The markup in the document preceding the root element must be well-formed"
    any idea what is missing?
    Thanks

    I am using websphere4.0.6,in standalone appln it works fine.

  • ADF Telnet -TML Parse Exception

    I have just followed the process to use ADF to create a telnet session as mentioned in following URL
    [ http://www.oracle.com/technology/obe/obe1013jdev/telnet/eim_telnet_final.htm | http://www.oracle.com/technology/obe/obe1013jdev/telnet/eim_telnet_final.htm ]
    But not getting the final result.I am able to see first screen after that i clicked on first option and got the following exception
    My Environment: Windows XP+SP3,Jdeveloper 10.1.3.3
    SEVERE: TML Parse Exception
    oracle.wireless.its.mdb.requester.TMLParserException: Invalid TML
    at oracle.wireless.its.mdb.requester.TMLParser.startElement(TMLParser.java:370)
    at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1288)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    at oracle.wireless.its.mdb.requester.TMLParser.parse(TMLParser.java:202)
    at oracle.wireless.its.mdb.requester.ApplicationServerRequesterImpl.handleRequestToUri(ApplicationServerRequesterImpl.java:220)
    at oracle.wireless.its.mdb.requester.ApplicationServerRequesterImpl.handleRequest(ApplicationServerRequesterImpl.java:266)
    at oracle.wireless.its.mdb.PageProcessorImpl.loadUri(PageProcessorImpl.java:905)
    at oracle.wireless.its.mdb.PageProcessorImpl.start(PageProcessorImpl.java:116)
    at oracle.wireless.its.mdb.DeviceSelectionPageProcessor.process(DeviceSelectionPageProcessor.java:223)
    at oracle.wireless.its.mdb.TelnetMessageListenerImpl.onMessageInput(TelnetMessageListenerImpl.java:852)
    at oracle.wireless.its.mdb.TelnetMessageListenerImpl.onMessage(TelnetMessageListenerImpl.java:110)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
    at ITS_MDB_EndPointProxy_6mlognn.onMessage(Unknown Source)
    at oracle.wireless.its.ra.ClientInputProcessor.callOnMessage(ClientInputProcessor.java:598)
    at oracle.wireless.its.ra.ClientInputProcessor.handleOnMessageInput(ClientInputProcessor.java:376)
    at oracle.wireless.its.ra.ClientInputProcessor.runInternal(ClientInputProcessor.java:297)
    at oracle.wireless.its.ra.ClientInputProcessor.run(ClientInputProcessor.java:76)
    at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
    at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
    at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
    at java.lang.Thread.run(Thread.java:595)
    Apr 27, 2009 2:46:29 PM oracle.wireless.its.mdb.requester.TMLParser handleParseError
    SEVERE: The response from the application server was not understood. This will typically happen if there was an error in the application, though in rare cases it could indicate an issue with how a valid response from the server is being processed. If the log level is not currently at the finest level, please set it to the finest level and recreate the situation the caused this problem so that the response from the server can be logged.
    Apr 27, 2009 2:46:29 PM oracle.wireless.its.mdb.requester.TMLParser handleParseError
    SEVERE: The following TML Markup was returned from ADFT: <html><head><title>Error instantiating web-application</title></head><body><h1>Error instantiating web-application</h1>Application: EIM_PDA-ViewController-webapp has been stopped</body></html>
    Apr 27, 2009 2:46:30 PM oracle.wireless.its.mdb.PageProcessorImpl start
    WARNING: Unable to load the initial uri for 127.0.0.1
    Please help me in this regards
    Thanks
    Ismail

    I resolved the parser issue with Jdeveloper 10.1.3.4 .
    Now,I am running different problem.
    If i ran pages individually then it works.But same will not works using navigation's(page1->page2 etc like that)
    I can see following log when i tried with pag1->page2
    Apr 29, 2009 2:42:39 PM oracle.wireless.device.capability.CapabilitiesDocument getCapabilities
    WARNING: No match found, checking for default attributes
    Please help me in this.
    Thanks
    Ismail
    Edited by: Kalee on Apr 29, 2009 2:38 AM

  • XML Parse in Oracle App Server

    Hi All,
    I am getting an XML parse exception while trying to parse a file in my application in Oracle 10g Appserver.The same file is working perfectly in oracle.Can any one please help me in resolving this or anyone please tell me how can i use other xml parsers instead of oracle's one.I shall be really grateful if someone could help me in resolving this.
    Thanks In Advance
    Best Regards
    Sujith
    org.xml.sax.SAXParseException: : XML-0220: (Fatal Error) Invalid InputSource.
         at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:226)
         at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:162)
         at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:220)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:148)
         at org.apache.commons.digester.Digester.parse(Digester.java:1591)
         at com.wellogic.synapse.management.common.ConfigurationServlet.init(ConfigurationServlet.java:47)
         at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2094)
         at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4523)
         at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4617)
         at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:765)
         at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:497)
         at com.evermind.server.Application.getHttpApplication(Application.java:886)
         at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:688)
         at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:570)
         at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:263)
         at com.evermind.server.http.HttpServer.setSites(HttpServer.java:259)
         at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:160)
         at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2325)
         at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1498)
         at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
         at java.lang.Thread.run(Thread.java:534)
    04/11/11 19:45:35 org.xml.sax.SAXParseException: : XML-0220: (Fatal Error) Invalid InputSource.
    04/11/11 19:45:35      at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:226)
    04/11/11 19:45:35      at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:162)
    04/11/11 19:45:35      at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:220)
    04/11/11 19:45:35      at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:148)
    04/11/11 19:45:35      at org.apache.commons.digester.Digester.parse(Digester.java:1591)
    04/11/11 19:45:35      at com.wellogic.synapse.management.common.ConfigurationServlet.init(ConfigurationServlet.java:47)
    04/11/11 19:45:35      at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2094)
    04/11/11 19:45:35      at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4523)
    04/11/11 19:45:35      at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4617)
    04/11/11 19:45:35      at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:765)
    04/11/11 19:45:35      at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:497)
    04/11/11 19:45:35      at com.evermind.server.Application.getHttpApplication(Application.java:886)
    04/11/11 19:45:35      at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:688)
    04/11/11 19:45:35      at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:570)
    04/11/11 19:45:35      at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:263)
    04/11/11 19:45:35      at com.evermind.server.http.HttpServer.setSites(HttpServer.java:259)
    04/11/11 19:45:35      at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:160)
    04/11/11 19:45:35      at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2325)
    04/11/11 19:45:35      at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1498)
    04/11/11 19:45:35      at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
    04/11/11 19:45:35      at java.lang.Thread.run(Thread.java:534)

    Refer Note:413558.1 on MetaLink, it says:
    *4. Ensure you run RDA against the Oracle Home in which the problem is occurring. RDA will only collect from a single Oracle Home at any one time. If an issue affects multiple OracleAS instances you will have to setup / rerun RDA against for each OracleAS instance.*
    Thanks
    Shail

  • Remove xml parser from the database

    I am deinstalling a version of xml and putting a newer version of
    it. how do i do that? I know that there is something like
    dropjava , but still there are other packages which are loaded
    into the schema. I want to clean out the earlier version and
    install the new version in a clean manner.
    Thanks
    nidhi
    null

    you'll need to write SQL to write SQL
    based on the USER_OBJECTS table
    where:
    SELECT 'drop java class '''&#0124; &#0124;
    dbms_java.longname(object_name)&#0124; &#0124;''';'
    from user_objects where
    OBJECT_TYPE = 'JAVA CLASS'
    and DBMS_JAVA.LONGNAME(OBJECT_NAME)
    LIKE 'oracle/xml/parser/%'
    This will spew out a set of DROP JAVA CLASS
    command which you can capture in a file
    using SQL*Plus':
    SPOOL somefilename
    command. Then run that spool file as a
    SQL script and all the right classes
    will be dropped.

  • Perl-xml-parser Conflict

    I'm needing to install intltool and perl-xml-parser is a dependency of it but the files for perl-xml-parser are conflicting with perlxml. I read this thread and ran
    pacman -Qo /usr/lib/perl5/vendor_perl/XML/Parser.pm
    to find out that it was conflicting with perlxml.
    Is it safe to run
    pacman -Sf perl-xml-parser
    or is there a way to work around the conflicts?
    This is the error that I'm getting:
    perl-xml-parser: /usr/lib/perl5/vendor_perl/XML/Parser.pm exists in filesystem
    and there are around 35-50 other files that have the same error and they all belong to perlxml.
    Last edited by ShadowsDemise (2011-02-26 23:40:50)

    I had the same problem when installing xmltv.
    First I checked what package owned the file: pacman -Qo /usr/lib/perl5/site_perl/current/XML/SAX/ParserDetails.ini
    Then I removed the package, and I still got a similar error, so I just removed the file, because no package owned it any longer.

  • Internal Exception: oracle.xml.parser.v2.XMLParseException xsi:type "toplin

    i am using toplink 10.1.3.0.0 with oracle app server 10.1.2.2, i am using change field optimistic locking and generating the project xml,
    application runs great locally in the jdeveloper, but when it is deployed on app server getting following error
    here are the headers from both my project.xml as well as session xml..
    <?xml version="1.0" encoding="UTF-8"?>
    <toplink:object-persistence version="Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)" xmlns:opm="http://xmlns.oracle.com/ias/xsds/opm" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:toplink="http://xmlns.oracle.com/ias/xsds/toplink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <opm:name>PROJ</opm:name>
    <opm:class-mapping-descriptors>
    <opm:class-mapping-descriptor xsi:type="toplink:relational-class-mapping-descriptor">
    <?xml version="1.0" encoding="UTF-8"?>
    <toplink-sessions version="4.5" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <session xsi:type="server-session">
    <name>PROJSession</name>
    <event-listener-classes/>
    <logging xsi:type="toplink-log">
    <log-level>finer</log-level>
    </logging>
    <primary-project xsi:type="xml">PROJ.xml</primary-project>
    <login xsi:type="database-login">
    <platform-class>oracle.toplink.platform.database.oracle.OraclePlatform</platform-class>
    <user-name></user-name>
    any help/idea appreciated...
    Exception [TOPLINK-9005] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.SessionLoaderException
    Exception Description: An exception was thrown while loading the <project-xml> file [PROJ.xml].
    Internal Exception: Exception [TOPLINK-25004] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.XMLMarshalException
    Exception Description: An error occurred unmarshalling the document
    Internal Exception: Exception [TOPLINK-27101] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.platform.xml.XMLPlatformException
    Exception Description: An error occurred while parsing the document.
    Internal Exception: oracle.xml.parser.v2.XMLParseException: xsi:type "toplink:changed-field-locking-policy" not resolved to a type definition
    at oracle.toplink.exceptions.SessionLoaderException.failedToLoadProjectXml(SessionLoaderException.java:74)
    at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.loadProjectConfig(TopLinkSessionsFactory.java:316)
    at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.createSession(TopLinkSessionsFactory.java:241)
    at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildServerSessionConfig(TopLinkSessionsFactory.java:215)
    at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildSession(TopLinkSessionsFactory.java:168)
    at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildTopLinkSessions(TopLinkSessionsFactory.java:124)
    at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.load(XMLSessionConfigLoader.java:103)
    at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:367)
    at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:334)
    at myProjectPackage.common.data.toplink.ToplinkDataManagerPeer.<init>(ToplinkDataManagerPeer.java:41)
    at myProjectPackage.common.data.DataManagerFactory.getDataManagerInstance(DataManagerFactory.java:40)
    at myProjectPackage.common.servlet.NYSDOTFilter.getDataManager(NYSDOTFilter.java:964)
    at myProjectPackage.common.servlet.NYSDOTFilter.doFilter(NYSDOTFilter.java:144)
    at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
    at myProjectPackage.caf.servlet.NYSDOTCAFFilter.doFilter(NYSDOTCAFFilter.java:90)
    at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
    at myProjectPackage.common.servlet.NYSDOTLoginFilter.doFilter(NYSDOTLoginFilter.java:95)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:669)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:340)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:228)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    at java.lang.Thread.run(Thread.java:570)

    first thanks for your reply,
    i already figured that out and deployed it using 10.1.3.1 jars
    my question
    1) if it is a bug , how come it works fine with jdeveloper (
    i would appreciate if you could provide any info about it.
    2) i dont want to sound sarcastic , but 10.1.3.1 has of optimistic locking and the recommended solution i found was to use descriptor.getQueryManager().setUpdateCallCacheSize(0);
    looks like 10.1.3.1 fixed one bug and introduced other one which was working fine earlier...
    is there any other way of fixing optimistic locking issue other than using the
    descriptor.getQueryManager().setUpdateCallCacheSize(0);
    where i can find the latest/greatest (up to date patched version of toplink)
    thanks again for your help

  • Oracle.xml.parse.v2.XMLParserException: Whitespace Exception

    Can any body help to sort out this problem, When I am trying to transform an XML to another XML using XSLT I am getting the following exception oracle.xml.parser.v2.XMLParserException: Whitespace Exception. My piece of codes are as below .
    XSLT:
    <?xml version="1.0"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:quipmentGenerator="http://www.oracle.com/XSL/Transform/java/EquipmentGenerator xmlns:TypeGenerator="http://www.oracle.com/XSL/Transform/java/TypeGenerator xmlns:ShelfGenerator="http://www.oracle.com/XSL/Transform/java/ShelfGenerator">
    </xsl:stylesheet>
    JAVA :
    import java.io.*;
    import java.net.URL;
    import java.net.MalformedURLException;
    import oracle.xml.parser.v2.*;
    public class Transformer
    public static void main(String args[]) throws Exception{
    String fileName = "abc.xsl", XMLStr = "C:\\dev\\task2\\abc.xml";
    XSLProcessor processor = new XSLProcessor();
    // you can also use a standard HTTP URL instead of
    // the file protocol shown below
    // URL xslURL = new URL(fileName);
    // instantiate a stylesheet
    InputStream xslInput = new FileInputStream(fileName);
    XSLStylesheet stylesheet = processor.newXSLStylesheet(xslInput);
         DOMParser parser = new DOMParser();
         URL xslURL = new URL("file://" + XMLStr);
         parser.setPreserveWhitespace(true);
    parser.parse(xslURL);
    // Preparing the XML document
    XMLDocument xml = parser.getDocument();
    XMLDocumentFragment result;
    result = processor.processXSL(stylesheet, xml);
         // create an output document to hold the result
    XMLDocument out = new XMLDocument();
         // create a dummy document element for the
              // output document
         out.appendChild(result);
         ByteArrayOutputStream outStream =      new ByteArrayOutputStream( );
         out.print(outStream);
         String transformedXML = outStream.toString();
         System.out.println(transformedXML);
    }     

    Remove any blank spaces or empty lines before the XML declaration.

Maybe you are looking for