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)

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 Parse issues when using Network Data Model LOD with Springframework 3

Hello,
I am having issues with using using NDM in conjuction with Spring 3. The problem is that there is a dependency on the ConfigManager class in that it has to use Oracle's xml parser from xmlparserv2.jar, and this parser seems to have a history of problems with parsing Spring schemas.
My setup is as follows:
Spring Version: 3.0.1
Oracle: 11GR2 and corresponding spatial libraries
Note that when using the xerces parser, there is no issue here. It only while using Oracle's specific parser which appears to be hard-coded into the ConfigManager. Spring fortunately offers a workaround, where I can force it to use a specific parser when loading the spring configuration as follows:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl But this is an extra deployment task we'd rather not have. Note that this issue has been brought up before in relation to OC4J. See the following link:
How to change the defaut xmlparser on OC4J Standalone 10.1.3.4 for Spring 3
My question is, is there any other way to configure LOD where it won't have the dependency on the oracle parser?
Also, fyi, here is the exception that is occurring as well as the header for my spring file.
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
Line 11 in XML document from URL [file:/C:/projects/lrs_network_domain/service/target/classes/META-INF/spring.xml] is invalid;
nested exception is oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
 [snip]
 ... 31 more
Caused by: oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
 at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:425)
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:331)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:222)
 at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
 at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388)Here is my the header for my spring configuration file:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:aop="http://www.springframework.org/schema/aop"
 xmlns:tx="http://www.springframework.org/schema/tx"
 xmlns:context="http://www.springframework.org/schema/context"
 xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
 http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd
 http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx.xsd
 http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd">Thanks, Tom

I ran into this exact issue while trying to get hibernate and spring working with an oracle XMLType column, and found a better solution than to use JVM arguments as you mentioned.
Why is it happening?
The xmlparserv2.jar uses the JAR Services API (Service Provider Mechanism) to change the default javax.xml classes used for the SAXParserFactory, DocumentBuilderFactory and TransformerFactory.
How did it happen?
The javax.xml.parsers.FactoryFinder looks for custom implementations by checking for, in this order, environment variables, %JAVA_HOME%/lib/jaxp.properties, then for config files under META-INF/services on the classpath, before using the default implementations included with the JDK (com.sun.org.*).
Inside xmlparserv2.jar exists a META-INF/services directory, which the javax.xml.parsers.FactoryFinder class picks up and uses:
META-INF/services/javax.xml.parsers.DocumentBuilderFactory (which defines oracle.xml.jaxp.JXDocumentBuilderFactory as the default)
META-INF/services/javax.xml.parsers.SAXParserFactory (which defines oracle.xml.jaxp.JXSAXParserFactory as the default)
META-INF/services/javax.xml.transform.TransformerFactory (which defines oracle.xml.jaxp.JXSAXTransformerFactory as the default)
Solution?
Switch all 3 back, otherwise you'll see weird errors. javax.xml.parsers.* fix the visible errors, while the javax.xml.transform.* fixes more subtle XML parsing (in my case, with apache commons configuration reading/writing).
QUICK SOLUTION to solve the application server startup errors:
JVM Arguments (not great)
To override the changes made by xmlparserv2.jar, add the following JVM properties to your application server startup arguments. The java.xml.parsers.FactoryFinder logic will check environment variables first.
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
However, if you run test cases using @RunWith(SpringJUnit4ClassRunner.class) or similar, you will still experience the error.
BETTER SOLUTION to the application server startup errors AND test case errors:
Option 1: Use JVM arguments for the app server and @BeforeClass statements for your test cases.
System.setProperty("javax.xml.parsers.DocumentBuilderFactory","com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl");
System.setProperty("javax.xml.parsers.SAXParserFactory","com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl");
System.setProperty("javax.xml.transform.TransformerFactory","com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl");
If you have a lot of test cases, this becomes painful.
Option 2: Create your own Service Provider definition files in the compile/runtime classpath for your project, which will override those included in xmlparserv2.jar.
In a maven spring project, override the xmlparserv2.jar settings by creating the following files in the %PROJECT_HOME%/src/main/resources directory:
%PROJECT_HOME%/src/main/resources/META-INF/services/javax.xml.parsers.DocumentBuilderFactory (which defines com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl as the default)
%PROJECT_HOME%/src/main/resources/META-INF/services/javax.xml.parsers.SAXParserFactory (which defines com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl as the default)
%PROJECT_HOME%/src/main/resources/META-INF/services/javax.xml.transform.TransformerFactory (which defines com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl as the default)
These files are referenced by both the application server (no JVM arguments required), and solves any unit test issues without requiring any code changes.
This is a snippet of my longer solution for how to get hibernate and spring to work with an oracle XMLType column, found on stackoverflow.

XML Parsing Error when opening Dreamweaver CS4

Hi guys, I downloaded a trial version of Dreamweaver CS4
which was downloaded from the adobe website and once i try
installing it it comes up with 'please delete current menus.xml
file and then rename menus.bak file to menus.xml'. Once I tried
that the new renamed xml file has the same problem as the old one.
Now, When i opened up the file in Firefox it came up with an XML
Parsing error. The exact error is as below:
XML Parsing Error: prefix not bound to a namespace
Location:
file:///C:/Program%20Files/Adobe/Adobe%20Dreamweaver%20CS4/configuration/Menus/menus.xml
Line Number 12, Column 5: <shortcut
mmstring:name="menus/DWShortcuts_Main_Quit" key="Opt+F4"
command="dw.quitApplication()" id="DWShortcuts_Main_Quit" />
----^
I am running windows XP SP3. Can anyone offer an
insight/possible solution? I've already tried the following methods
which have been suggested by other forums:
CS4 clean script on Adobe website
Microsoft installer clean up
uninstall and reinstall all CS4/adobe products
deleting Cache.db
deleting Macromedia folder
deleting faulty line in menus.xml file
Is there anything else I can do? Thanks guys!

1) Close Dreamweaver
2) Navigate to the Design.xml file and rename it.
3) Launch Dreamweaver and it will recreate the Design.xml file
The AppData folder is hidden by default on Windows, so you need to enable the option to view hidden files and folders in order to locate it, as follows:
In Vista/Windows 7, select Start > Computer > Organize > Folder and Search Options > View. In Advanced settings, choose Show hidden files and folders.
In Windows XP, select Start > My Computer > Tools > Folder Options > View. In Advanced settings, choose Show hidden files and folders.
Once you turn on this option, hidden folders are displayed as dimmed icons to remind you to treat them with care.

XML parser error; when XPath elements starts with "_"

Hi,
I have a problem in extracting elements from XML which is starting with "_". please check the queries below executed on Oracle 10g.
Query 1:
SELECT EXTRACTVALUE(XMLTYPE('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'),'/A/_B') FROM DUAL;
Error starting at line 1 in command:
SELECT EXTRACTVALUE(XMLTYPE('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'),'/A/_B') FROM DUAL
Error report:
SQL Error: ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00601: Invalid token in: '/A/_B'
31011. 00000 - "XML parsing failed"
*Cause: XML parser returned an error while trying to parse the document.
*Action: Check if the document to be parsed is valid.
Query 2:
SELECT EXTRACTVALUE(XMLTYPE('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'),'/A/E') FROM DUAL;
EXTRACTVALUE(XMLTYPE('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'),'/A/E')
4
Oracle version:
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
Please let me know if there is any workaround for this.*
Thanks,
Veerababu Kanumilli.

Hi MichaelS,
- I have executed the queries provided by you, but I am not able to get the result in 10g when I am trying to access elements with "_" in XPath.
select * from v$version where rownum = 1;
select extractvalue (xmltype ('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'), '/A/_B') "_B" from dual;
select extractvalue (xmltype ('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'), '/A/E') "E" from dual;
Output:
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
Error starting at line 4 in command:
select extractvalue (xmltype ('<A><_B>1</_B><_C>2</_C><_D>3</_D><E>4</E></A>'), '/A/_B') "_B" from dual
Error report:
SQL Error: ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00601: Invalid token in: '/A/_B'
31011. 00000 - "XML parsing failed"
*Cause: XML parser returned an error while trying to parse the document.
*Action: Check if the document to be parsed is valid.
E
4
Thanks,
Veerababu Kanumilli

Adobe Designer 7.0 - XML parsing error when data connection to XML with UTF-16

Hi all
 
 I need to change my data connection xml file to use UTF-16 instead of ISO-8859-1. When I connect the file with the UTF-16 encoding, I receive the following error
 
 Invalid XML: Xml parsing error: encoding specified in XML declaration is incorrect (error code 19) ..
 
 The XML declaration is:
 <?xml version="1.0" encoding="utf-16"?>
 
 I am able to succesfully set the encoding to "UTF-8". UTF-16 should also be possible.
 
 Has anyone seen this error before ? How can I resolve this ?
 
 Thanks in advance
 
 Bilal Haniff

Thank you, expert, for your quick reply.
Described problem got solved: we noticed later that the extra text only appears for users using Adobe professional 7.0, 'normal' users with adobe 8.0 reader don't get the extra text, so that is ok for us.

UCSPE XML parsing error when importing from live UCS

Hi all,
I'm trying to import our live UCS hardware inventory in to the UCS platform emulator but keep getting an error stating:
Server Error: code ERR-xml-parse-error: XML PARSING ERROR: no class named computeExtBoard
The UCSPE imports all of our chassis' and blade servers, but it's missing all the chassis fans and psus, and the dimms, hdds, cpus, and storage controllers from all the blades. I haven't been able to figure out how to download or export the hardware inventory from the live UCS Manager as an XML for editing/loading in to UCSPE. It looks like you can only export as XML from USCPE, not from UCS Manager. Anybody have experience dealing with this?
Thanks in advance!
Jordan

Hi all,
I'm trying to import our live UCS hardware inventory in to the UCS platform emulator but keep getting an error stating:
Server Error: code ERR-xml-parse-error: XML PARSING ERROR: no class named computeExtBoard
The UCSPE imports all of our chassis' and blade servers, but it's missing all the chassis fans and psus, and the dimms, hdds, cpus, and storage controllers from all the blades. I haven't been able to figure out how to download or export the hardware inventory from the live UCS Manager as an XML for editing/loading in to UCSPE. It looks like you can only export as XML from USCPE, not from UCS Manager. Anybody have experience dealing with this?
Thanks in advance!
Jordan

XML Parsing Error when diplaying the downloads window

After upgrading to the 3.6.15 version everytime I open the downloads window the following text is displayed:
XML Parsing Error: unclosed token
Location: chrome://mozapps/content/downloads/downloads.xul
Line Number 83, Column 5: <menuitem id="menuitem_show"
----^

After upgrading to the 3.6.15 version everytime I open the downloads window the following text is displayed:
XML Parsing Error: unclosed token
Location: chrome://mozapps/content/downloads/downloads.xul
Line Number 83, Column 5: <menuitem id="menuitem_show"
----^

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

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 '<' 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;&lt;(0'
When the message now will be restarted everything works fine.
Regards,
Olaf

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

Xml parsing issue when xmlns present xquery sqlserver

Hi ,
I have this xml
declare @xml xml
set @xml ='<students xmlns="http://www.abcdef.com/pqrs/1.3.0" xsi:schemaLocation="http://www.abcdef.com/pqrs/1.3.0_f3">
<student>
<id>1</id>
<name>aaa</name>
</student>
</students>'
when I am xquering this data like below.
select
s.n.value('(id/text())[1]', 'varchar(50)') as id ,
s.n.value('(name/text())[1]','varchar(50)') as name
from
@XML.nodes('/students/student') as S(N)
Its not returning any rows. But when I remove the below lines in xml.
xmlns="http://www.abcdef.com/pqrs/1.3.0" xsi:schemaLocation="http://www.abcdef.com/pqrs/1.3.0_f3"
Its working fine.
can any one tell me what is the reason ? how to over come this ?
Thanks in advance.

Hello,
It seems contain incorrect "schemaLocation" in the definition, please refer to the following T-SQL below:
declare @xml xml
set @xml ='<students xmlns="http://www.abcdef.com/pqrs/1.3.0">
<student>
<id>1</id>
<name>aaa</name>
</student>
</students>';
; with xmlnamespaces (default 'http://www.abcdef.com/pqrs/1.3.0')
select
s.n.value('(id/text())[1]', 'varchar(50)') as id ,
s.n.value('(name/text())[1]','varchar(50)') as name
from
@XML.nodes('/students/student') as S(N)
Regards,
Elvis Long
TechNet Community Support

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

Hi All,
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) 

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 "org.w3c.dom.ls.LSException: An invalid XML character (Unicode: 0x16) was found in the element content of the document" when it sees not properly formatted XML at any cause (having incompatible data/special character).

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.

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 parse Exception when running when dynpro

Similar Messages

Maybe you are looking for