XML Parser related.

Hi!
Has anybody tried building the IBM's XML4c3_5_1
XML C++ parser source on Solaris7/8 using Forte6 Update 1 compiler ?
If yes, can you let me know the issues involved.
thanks in advance.
-sri

Anthony D. Noriega (guest) wrote:
: I need to have further information about some of the following
: issues and XML features and make a determination useful for
: evaluation and recommendation:
: ISSUES
: 1) Is there a maximum size for an XML document to provide data
: for PL/SQL(or SQL) across tables, provided that no CLOB are
used?
The limit should be what can be inserted into an object view.
: 2) How about from Oracle to an XML document ?
The limit should be what can be retrieved from an object view.
: 3) Is there a ratio between XML document size and main memory
:and SGA size. What are Oracle's recommendations /
Not directly due to the relationship between XML metadata and
data not being constrained.
: 4) Can the Oracle Application Server run on a DHCP NT server
: when using XML parsing ?
If it can run a JavaVM with the correct permissions there are no
other special requirements.
:Is it NT Service Pack 3 and 4 compatible ?
No special requirements here.
: 5) How parsers can interact with one another or related tools ?
: For example, how the XML parser for c/c++ could be useful when
: using Pro*C/C++ (programmer 2000) or OCI interfaces ? In
other
: words, what is the business logic in using these tools ?
Not really sure of your question. The XML components are useful
in any application where I am processing documents or data with
an XML structure. The choice to use XML can be based on quite a
range of requirements due to its declarative syntax and open
standards. If you give me a specific application, I can perhaps
be more helpful.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Similar Messages

XML Parser for PL/SQL and related issues

I need to have further information about some of the following
issues and XML features and make a determination useful for
evaluation and recommendation:
ISSUES
1) Is there a maximum size for an XML document to provide data
for PL/SQL(or SQL) across tables, provided that no CLOB are used?
2) How about from Oracle to an XML document ?
3) Is there a ratio between XML document size and main memory and
SGA size. What are Oracle's recommendations /
4) Can the Oracle Application Server run on a DHCP NT server when
using XML parsing ? Is it NT Service Pack 3 and 4 compatible ?
5) How parsers can interact with one another or related tools ?
For example, how the XML parser for c/c++ could be useful when
using Pro*C/C++ (programmer 2000) or OCI interfaces ? In other
words, what is the business logic in using these tools ?
null

Anthony D. Noriega (guest) wrote:
: I need to have further information about some of the following
: issues and XML features and make a determination useful for
: evaluation and recommendation:
: ISSUES
: 1) Is there a maximum size for an XML document to provide data
: for PL/SQL(or SQL) across tables, provided that no CLOB are
used?
The limit should be what can be inserted into an object view.
: 2) How about from Oracle to an XML document ?
The limit should be what can be retrieved from an object view.
: 3) Is there a ratio between XML document size and main memory
:and SGA size. What are Oracle's recommendations /
Not directly due to the relationship between XML metadata and
data not being constrained.
: 4) Can the Oracle Application Server run on a DHCP NT server
: when using XML parsing ?
If it can run a JavaVM with the correct permissions there are no
other special requirements.
:Is it NT Service Pack 3 and 4 compatible ?
No special requirements here.
: 5) How parsers can interact with one another or related tools ?
: For example, how the XML parser for c/c++ could be useful when
: using Pro*C/C++ (programmer 2000) or OCI interfaces ? In
other
: words, what is the business logic in using these tools ?
Not really sure of your question. The XML components are useful
in any application where I am processing documents or data with
an XML structure. The choice to use XML can be based on quite a
range of requirements due to its declarative syntax and open
standards. If you give me a specific application, I can perhaps
be more helpful.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

XML Parsing error in PL/SQL

Hello,
I have some problem in parsing Mircrosoft OpenXML file using Oracle 10g Release2 XML Parser for PL/SQL.
I use dbms_xmlparser, dbms_xmldom, dbms_xslprocessor packages
OpenXML file use "w:" as namespace, so every element has prefix "w:" like
<w:wordDocument ..>
<w:body..>
<w:p..>
<w:r..>
<w:t..>
My job is to read OpenXML file inside PL/SQL code, parse it, and load it into the corresponding table.
Here is my PL/SQL code.
DECLARE
doc dbms_xmldom.DOMDocument;
node_list dbms_xmldom.DOMNodeList;
l_node dbms_xmldom.DOMNode;
one_element dbms_xmldom.DOMElement;
PROCEDURE p (msg VARCHAR2, nl BOOLEAN := TRUE) IS
BEGIN
dbms_output.put_line (msg);
IF nl THEN dbms_output.put(CHR(10)); END IF;
END:
BEGIN
doc := xml.parse(BFileName('XML_DIR','OpenXMLFile.xml'));
node_list := xpath.selectNodes(doc, '/w:wordDocument/w:body/w:p/w:r/w:t');
FOR j IN 0..dbms_xmldom.getLength(node_list)-1
LOOP
p( xpath.valueOf(dbms_xmldom.item(node_list, j), '.'), nl=>FALSE );
END LOOP;
Here is the error message.
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00601: Invalid token in: '/w:wordDocument/w:body/w:p/w:r/w:t
[starts-with(., "!")]'
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 900
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 928
ORA-06512: at "SYSTEM.XPATH", line 173
ORA-06512: at "SYSTEM.XPATH", line 179
ORA-06512: at line 38
I really don't know why I got this error message nor how to solve it. If I remove "w:" manually within open xml file, then parsing works well. I guess XML parser for PL/SQL doesn't recognize ":" or maybe doesn't support namespace?
My question is
1. In oracle 10g release2, XML Parser for PL/SQL can recognize ":" in the element name? or does it support namespace? If not, is there any workaround for solving this problem?
2. How can I make XML Parser recognize ":" in the element name in the xml file or How can I declare namespace in the PL/SQL code so that PL/SQL xml parser can recognize namespace like "w:"?
In fact, I don't use XML DB and what I want to do is just to load XML file into the relational table and some parts of whole XML file will be inserted into the CLOB in the table.
Should I really use XML DB to do the above job?
Any comment or suggestions will be greatly appreciated.

This works correctly. I added prefixes to your extract path. (I had to add the xmlns:xsi to your root node also.)
declare
-- Local variables here
   doc_in       dbms_xmldom.DOMDocument;
   aNodeList    dbms_xmldom.DOMNodeList;
begin
-- Test statements here
doc_in := dbms_xmldom.newdomdocument(
'<?xml version="1.0" encoding="UTF-8"?>' ||
'<ap:Collection xmlns:ap="http://www.abc.com/ap" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.abc.com/ap template.xsd"> ' ||
'<ap:info>' ||
'<ap:data name="Barbie" age="3">' ||
'</ap:data>' ||
'</ap:info>' ||
'</ap:Collection>');
aNodeList := dbms_xslprocessor.selectNodes(dbms_xmldom.makeNode(doc_in),
                                             '/ap:Collection/ap:info',
                                             'xmlns:ap="http://www.abc.com/ap"');
dbms_output.put_line('length of aNodeList = '|| dbms_xmldom.getLength(aNodeList) );
end;

Why the oracle XML parser "parses" the DTD comments?

Hi all,
I always use the header
<?xml version = '1.0' encoding='ISO-8859-1' ?>
to be able to use foreign characters in the XML documents.
The oracle xml parser handles this correctly.
My problem is, when I write comments inside the DTD, the
parser reports "Invalid UTF8 encoding".
Why the parser "parse" the comments? (protected by )
How do I say that the DTD encoding is different from UTF, like
ISO-8859-1?
Example of a correct DTD and corresponding XML, reporting
problems, related to the 2nd comment in the DTD specification,
written with ISO-8859-1 characters.
The DTD:

<!ELEMENT valid ( B, C ) >

<!ELEMENT B (#PCDATA) >
<!ELEMENT C (#PCDATA) >
The XML:
<?xml version = '1.0' encoding='ISO-8859-1' ?>
<!DOCTYPE valid SYSTEM 'valid.dtd'>
<valid>
<B>How are you, Conceigco</B>
<C>I'm fine, thank you.</C>
</valid>
The parser output:
[jgr@frontera test-dtd]$ java oracle.xml.parser.v2.oraxml -v
valid.xml
Error while parsing input sourcevalid.xml(Invalid UTF8 encoding.)
Thank you for any help.
Jorge Gustavo Rocha

I was wrong in saying that the attributes are not added to the element.My main aim is to add a array of elements to the root node.
Is there a efficient manner in adding the elements , rather than adding them individually with the help of appendChild method.
Thanks in advance.
null

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

Problem with com.sun.xml.parser.Parser

Hi ,
I am using weblogic 6.01.
In my ejb class, I am parsing a String to create XmlDocument.
I created xml registry in weblogic server.
In my weblogic server's xml registry,
I have com.sun.xml.parser.DocumentBuilderFactoryImpl as
DocumentBuilderFactory
and com.sun.xml.parser.Parser as parser.
I am using jaxp 1.1 for all my xml related processing. All required jars are
in the classpath.
following is my code
protected Document createDocument ( String a_sXmlDocument )
try
ByteArrayInputStream baInputStream = new ByteArrayInputStream
(a_sXmlDocument.getBytes ());
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance ();
DocumentBuilder builder = factory.newDocumentBuilder ();
Document xmlDocument = builder.parse (baInputStream);
return xmlDocument ;
catch (
I get following exception at builder.parse ( baInputStream )
Can't find bundle for base name com.sun.xml.parser.resources.Messages,
locale en
at com.sun.xml.parser.Parser.parseInternal(Parser.java:516)
at com.sun.xml.parser.Parser.parse(Parser.java:284)
at
com.sun.xml.parser.DocumentBuilderImpl.parse(DocumentBuilderImpl.java
:95)
at
weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuild
er.java:98)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:78)
at
com.datamap.arch.datamap.BasicTransportableDelegate.createDocument(Ba
I would appreciate if anyone could help in this exception.
Thank you,
Mahendra

Hi ,
I am using weblogic 6.01.
In my ejb class, I am parsing a String to create XmlDocument.
I created xml registry in weblogic server.
In my weblogic server's xml registry,
I have com.sun.xml.parser.DocumentBuilderFactoryImpl as
DocumentBuilderFactory
and com.sun.xml.parser.Parser as parser.
I am using jaxp 1.1 for all my xml related processing. All required jars are
in the classpath.
following is my code
protected Document createDocument ( String a_sXmlDocument )
try
ByteArrayInputStream baInputStream = new ByteArrayInputStream
(a_sXmlDocument.getBytes ());
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance ();
DocumentBuilder builder = factory.newDocumentBuilder ();
Document xmlDocument = builder.parse (baInputStream);
return xmlDocument ;
catch (
I get following exception at builder.parse ( baInputStream )
Can't find bundle for base name com.sun.xml.parser.resources.Messages,
locale en
at com.sun.xml.parser.Parser.parseInternal(Parser.java:516)
at com.sun.xml.parser.Parser.parse(Parser.java:284)
at
com.sun.xml.parser.DocumentBuilderImpl.parse(DocumentBuilderImpl.java
:95)
at
weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuild
er.java:98)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:78)
at
com.datamap.arch.datamap.BasicTransportableDelegate.createDocument(Ba
I would appreciate if anyone could help in this exception.
Thank you,
Mahendra

Xml parsing innovation

[ANN] VTD-XML Version 1.5 Released
Eight years after the invention of XML, DOM and SAX,
despite their respective issues, are still the mainstays
of application developers.
So is it the end of road for XML parsing innovation?
The VTD-XML project team think not. We are proud to
announce the availability of both C and Java version
1.5 of VTD-XML, the next generation open-source XML
parser that goes beyond DOM and SAX in terms of
performance, memory usage and ease of use.
The technical highlights of VTD-XML are:
* Performance: the world's fastest XML parser,
between 5x~10x faster than DOM
* Memory Usage: 3x to 5x less than DOM, 1.3x~1.5x
XML document size
* Random access with built-in XPath support
* A simple and intuitive API
Other advanced features include:
* Buffer reuse
* Large document support (2GByte)
* Incremental update
* Hardware acceleration
* Native XML indexing.
For demos, latest benchmarks, related articles and software
downloads, please visit http://vtd-xml.sf.net. Also let us
know your thoughts and suggestions and help us improve
VTD-XML.

Don't crosspost.
http://forum.java.sun.com/thread.jspa?threadID=707987&tstart=20
It should be noted that this parser is not a full implementation, and ignores some xml constructs, which perhaps helps it's performance numbers in comparison to compliant parsers.

Losing Line-feed in XML parsing (XMLTRANSFORM) or File output (clob2file)?

Hi all, need some help please!
I'm using a xslt file to transferm a XML file into a txt format file. Within the XSLT file, there is a carriage-return (<xsl:text>
</xsl:text>) (it disappeared already, here is what i'm using "#xD" or "#xA", have to take the '&' and ';' away), but the final output txt file seems to lose this carriage-return/line-feed information. The output data became one-line.
Here are the steps I've used:
1. lv_xml_data = XMLTRANSFORM (a.xml_data, b.f_xslt)
=> output data into XMLTYPE;
2. using XMLTYPE.getclobval to get the output data into CLOB format.
lv_output_clob := XMLTYPE.getclobval (lv_xml_data);
3. using encoding:
lv_output_clob :=
DBMS_XMLGEN.CONVERT (lv_output_clob, DBMS_XMLGEN.entity_decode);
4. using clob2file write to a file with txt format.
DBMS_XSLPROCESSOR.clob2file (lv_output_clob,
lv_output_dir,
lv_filename,
NLS_CHARSET_ID ('UTF8')
Been struggling with these a few days already. Any help is appreciated. I would really like to get some input to see what might cause the carriage-return/line-feed characters lost.
Thanks in advance!
-Jane
Edited by: user9084567 on Feb 1, 2010 1:45 PM
Edited by: user9084567 on Feb 1, 2010 1:47 PM
Edited by: user9084567 on Feb 1, 2010 1:48 PM

A_non,
After a few testing, I can identify the CRLF was lost in XMLTRANSFORM. I had read your other thread related to this, and try to run this sample code:
/* Formatted on 2010/02/03 15:32 (Formatter Plus v4.8.8) */
DECLARE --Local variables here
v_xml XMLTYPE
:= XMLTYPE
('<
offers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="xsd.xsd"><
submit type="DAM" date="2007-03-28" name="MKTPART1" mode="NORMAL"/><
offer name="Jamestown" flag="true" version_no="1.0"><
standing date="2007-03-29" type="WED"/><
identifier external_id="523736560"/><
/offer><
/offers>'
v_xslt XMLTYPE
:= XMLTYPE
('<
xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <
xsl:output method="text"/> <
xsl:variable name="new_line" select="''
''" /> <
xsl:template match="/"> <
xsl:value-of select="/offers/offer/...name"/><
xsl:value-of select="$new_line" /><
xsl:value-of select="/offers/submit/...date"/><
xsl:value-of select="$new_line" /><
xsl:value-of select="/offers/offer/standing/...date"/><
xsl:value-of select="$new_line" /><
xsl:value-of select="/offers/offer/standing/...type"/><
xsl:value-of select="$new_line" /><
/xsl:template><
/xsl:stylesheet>'
BEGIN -- Test statements here
DBMS_OUTPUT.put_line (XMLTYPE.transform (v_xml, v_xslt).getstringval ());
END;
But come out these error:
Error at line 2
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00230: invalid character 10 (U+000A) found in a Name or Nmtoken
Error at line 4
ORA-06512: at "SYS.XMLTYPE", line 310
ORA-06512: at line 2
Can not figure out why. Try to use this <xsl:variable name="new_line" select="''& # x A ;''" /> inside my style sheet, but it seems not taking it. Not too sure what's exactly should be the quotes for "''& # x A ;''" (w/o space). If I used doub quote + two single quotes, it returns error, LPX-00601: Invalid token in: ' '; if I used single quote + double quote, it did not bring in CRLF at all.
Any input?
Thanks in advance.

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

URL in epub results in XML parsing error

Hi
I am using inDesign to create epub ebooks, but stumbling over inserting hyperlinks. Regular hyperlinks to straightforward URLs work OK, but if I add a link to Google maps, like this one...
http://maps.google.co.uk/maps?q=[email protected],0.394&ll=51.443, 0.394&z=17&iwloc=A
... I get problems.
Some ebook readers refuse to load the book, reporting XML parsing error: not well-formed. The red underline points to the second equals symbol. Adobe Digital Editions loads the book, but the hyperlink and everything following it are not displayed.
I have searched for help about this, and gather that XML does not like equals signs. I have tried using percent encoding (%3D) for the second equals sign, but iD appears to insert "25" after the % sign. I even tried using percent encoding for all the reserved characers in the URL (ie :/=@,) but nothing I do seems to fix the problem.
I would really appreciate some help with this. I've run out of ideas.

In fact, I don't use XML DB and what I want to do is just to load XML file into the relational table and some parts of whole XML file will be inserted into the CLOB in the table.Why wouldn't you want to use XML DB in 10gR2 to handle XML? I didn't know there was another way. Anyway, you might want to ask this question in this forum.
XML DB

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

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

Hello,
I was wondering if anybody had any experience in regards to the relative performance (i.e., speed) of the different Java XML parsers out there. Specifically,
javax.xml.parsers.DocumentBuilder.parse() vs. any others.
My goal is to reduce the amount of time needed to parse ~1000 XML files (avg size 3kb) and I have done some tests that lead me to conclude that the rate-limiting step is not the file i/o (surprisingly).
Is there any particular XML parser that people favor?
Thanks,
ckl

I have created a parser with interesting performance result with
files < 100 Ko at http://www.japisoft.com/fastparser
Regards,
A.Brillant

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

XML Parser related.

Similar Messages

Maybe you are looking for