Oracle XML Parser C++ V2 - BUG

One of the features of the v2 C++ XML parser is support for UTF-8 encoding. However if you create a XML document with the following header
<?xml version="1.0" encoding="UTF-8"?>
then the parser throws out the following error "unsupported encoding". Does this mean that this parser does not support UTF-8 encoding or is there some flag in the parser that needs to be checked?

The xmlparseBuffer() method of class XMLParser accepts an XML buffer in its first oratext * argument.
Though you say xmlparseBuffer() accepts filenames, it works with buffers, I'm using it.
null

Similar Messages

Oracle XML parser and IBM jdk bug

Hello,
From a few messages found in the XML forum it seems that IBM jvm could cause problems with oracle XML parser. ( see http://technet.oracle.com:89/ubb/Forum11/HTML/003823.html )
I am using IBM jvm (jdk 1.3) on a linux box, and problems are starting to arise:
I have
- 1 BC4J based jsp app which works fine.
- 2 XML parsing BC4J apps which cause strange errors (like parsing 40 documents fine and failing on the 41st for no apparent reason)
Hopefully, Steven Muench provided precious advice on this (basically, disabling the JIT), however some issues are still open:
<BLOCKQUOTE>quote:<HR>You should file a bug with IBM to get this fixed, using your stylesheet as a testcase. Lots of people have hit this problem.<HR></BLOCKQUOTE>
Has anyone (from oracle or else) done this yet? I have gone (quickly) through IBM website but I didn't find any bug report utility or the like...
<BLOCKQUOTE>quote:<HR>Disable your JIT compiler (or switch JVM's) and you won't have the error.<HR></BLOCKQUOTE>
Turning off the JIT indeed made the errors vanish, thanks a lot for the tip!
I have a few more questions though :
* As the BC4J framework uses the xml parser, It is fairly possible that the ibm jvm bug will affect it...
I haven't had any problems (yet?) with the BC4J part of my applications, but I'm a bit concerned about having random bugs lurking around (I have more than enough of my own :) )
Has anyone stumbled upon IBM JVM vs oracle parser issues in BC4J? (oracle.xml.parser.v2.XXXXXX exceptions...)
* If BC4J is indeed affected, what's the solution?
- Disable the JIT? (And forget about performance?... hmmm... no)
- Switch parsers? (oracle parser is too tightly integrated in the BC4J Framework isn't it?.. hmm... not possible either)
- Wait for a patch from IBM (and use another one in the meantime) / switch JVM :
In either case, I'd really like to know what is the JVM that oracle people use / would advise.
Thanks for your help
null

For those interested,
last week i reported this bug in the ibm jvm news forum.
They said that the problem had been investigated and would be fixed in their next service release.
FYI: the current release (SR7, labeled "build cx130-20010329) still has various problems wih oracle XML parser.
Remi
null

Oracle XML Parser - "comments" BUG!

hey fellas
I have almost wrapped up my project except for one stupid bug
that am getting. I'm using Oracle XML parser for Java.9.0
I am adding some comments in the output xml file but it is giving trouble.
My code:
====
Comment comment =xmldocument.createComment("mary had a lazy lamb");
xmldocument.appendNode(comment);
=====
Now comments are being added in the output xml file. BUT GUESS what -
Instead of putting the string like -

It is putting it like -
<?#comment mary had a lazy lamb comments?>
This, inadverantly throws an error when I open the file using a browser.
How to over come this.
Thanks

Hey fellas I urgently need a response!!Long-term solution: report it to Oracle as a bug.
Short-term solutions: don't write comments to your document. Or try a different serializer.

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

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

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

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

Bpel-108-UsingXQuery $publisher - oracle.xml.parser.v2.XMLElement@8b8e58

Hello,
I am using Oracle SOA Suite 11.1.1.4.0 While executing the XQuery example bpel-108-UsingXQuery I am facing the following problem/error.
The Xquery in the example is:
xquery version "1.0";
declare namespace ns0 = "http://example.com/bpel/books";
declare namespace ns1 = "http://samples.otn.com/xquerysample";
declare variable $category as node() external;
declare variable $publisher as xs:string external;
<bookReport>
for $b in //ns0:BOOKS/ns0:ITEM
where data($b/ns0:PUBLISHER) = $publisher
order by string-length($b/TITLE) return
<book>
<author> { data($b/ns0:AUTHOR) } </author>
<title> { data($b/ns0:TITLE) } </title>
<price>{ data(doc("pricelist.xml")/ns1:pricelist/ns1:product[1]/ns1:price) }</price>
<publisher>{ $publisher }</publisher>
{ $category }
</book>
</bookReport>
The variable $publisher, declared in 'declare variable $publisher as xs:string external' shall have the value 'Associated Press' as this has been assigned in the BPEL but it has in fact the value 'oracle.xml.parser.v2.XMLElement@8b8e58'.
The variable $category has the correct value.
What is here wrong or is it a bug in 11.1.1.4.0 in the oracle.xml.parser.v2.XMLElement class.

What a mess:
org.w3c.Element element = (org.w3c.Element) payload.get("payload");
private Document writeOraXMLtoDocument(org.w3c.Element payload) throws ParserConfigurationException, SAXException, IOException, TransformerException{
 ByteArrayInputStream inputStream = new ByteArrayInputStream(writeXMLToStream(new DOMSource(payload)).toByteArray());
 DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder =factory.newDocumentBuilder();
 return builder.parse(inputStream);
 private ByteArrayOutputStream writeXMLToStream(Source source) throws TransformerException {
ByteArrayOutputStream out = new ByteArrayOutputStream();
// Prepare the output file
Result result = new StreamResult(out);
// Write the DOM document to the file
TransformerFactory x = TransformerFactory.newInstance();
Transformer xformer = x.newTransformer();
xformer.transform(source, result);
return out;
Note, that you have to use the oracle transformer located in the xmlparserv2.jar
if it is not your default transformer , you have to set it at least for the above code by System.setProperty("javax.xml.transform.TransformerFactory","..classname...");

ANN: Oracle XML Parser for Java v2.0.0.1

A new maintenance release of the Oracle Parser for Java is
available for download. It has the following fixes and changes:
Bug fixes for #920536, i.e. Cannot access element attributes via
XSLT; #898423. i.e. ElementDecl's in DTDs; #774774, i.e. DOM
extensions using XSL pattern matching; #863890 i.e. SAX
IOException not thrown.
New APIs in the following new interface:
1. oracle.xml.parser.v2.NSResolver
- resolveNamespacePrefix( find the namespace definition in scope
for a given namespace prefix )
New APIs in the following classes:
1. oracle.xml.parser.v2.XMLNode
- selectNodes( Selects nodes from the tree which match the given
pattern; client can provide an NSResolver implementation to
resolve namespace prefixes in the pattern ).
2. oracle.xml.parser.v2.ElementDecl
- getParseTree( Returns the root Node of Content Model parse
tree, which could then be traversed node by node using
getFirstChild() and getLastChild(). The Node types are: PLUS,
COMMA, ASTERISK, ELEMENT, QMARK ).
This is the first beta patch release for v2.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

unzip -l appsborg2.zip | grep 9.0.4
0 04-18-03 20:10 .xdkjava_version_9.0.4.0.0_production
do i still need to do that step?No, you do not have to since "XML Parser for Java v9.0.4" is already installed as part of appsborg2.zip

XML parsing problems with Oracle XML parser for PL/SQL

I am using the Oracle XML parser for PL/SQL to transform XML into HTML usign XSL. The parser gives me sporadic errors trying to parse various XML documents. For the same XML source, the XMLPARSER will parse without errors one day and the next day will give me errors such as "invalid char in text", "Expected ';'.", or even Java null pointer exceptions.
I have verified that the XML sources are well formed, so I am pretty certain that the problems I am having are bugs in the XMLPARSER.
Is there going to be a XML parser for PL/SQL version 2 that will fix these bugs? If so, when??? If not, is there anything else I could do to fix these problems?
Thanks!

You can use the latest version.

ANN: Oracle XML Parser for Java v1.0.1.1 Maintenance

The first maintenance release of the Oracle XML Parser for
Java is available for download here.
It has the following fixes and changes since 1.0.1:
Bug Fixes:
#843157, parseDTD(InputSource, rootElement) and
parseDTD(URL, rootelement) then parse(InputSource) bugs;
#843143, parse(InputSource) bug;
#793012, no need to print a trace of an exception which is
rethrown.
Changes: None
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

The first maintenance release of the Oracle XML Parser for
Java is available for download here.
It has the following fixes and changes since 1.0.1:
Bug Fixes:
#843157, parseDTD(InputSource, rootElement) and
parseDTD(URL, rootelement) then parse(InputSource) bugs;
#843143, parse(InputSource) bug;
#793012, no need to print a trace of an exception which is
rethrown.
Changes: None
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Parsing errors with CDATA tags using oracle xml parser v2

I'm using the oracle.xml.parser.v2 parser to combine a
generated xml document from a database with a static
xsl file to produce html. Within the xml document, there
are fairly large CDATA sections (500 lines) which happen
to contain javaScript.
Occasionally, I'm getting xml tags in the final html
document! It seems that the oracle parser pukes
on a certain type of data within a CDATA tag, and then
replaces an angle bracket (<) of a tag with a #60. This
can cause html tags being viewed in the document. At
first, I thought the amount of JavaScript within the
CDATA tag was too large for the parser to handle,
because when I split it up into 2 or more parts the errors
went away. But, re-arranging the JavaScript (String in the CDATA tag)
can make the errors disappear. And, if I
use the Saxon parser to manually combine the xsl with
the xml, the output is fine. If anyone knows that this is
a confirmed bug by Oracle, or any other relevant info on
this, please let me know.

Hi,
Your lucky, i've just finished a project that used the oracle parser extensively.
I think the problem may stem from your xsl. Although your cdata tags may be well formed, in the xsl you might need to escape the text again, this may mean that the xsl needs to print a further cdata tag around the data. This is because the parser (well the version I was using) strips the cdata tags before the transformation happens.
This is the probably the cause of the nasty html output.

Oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'RO

I'm using the oracle.xml.parser.v2. The files (xml, xsl) are:
<?xml version="1.0" ?>
<?xml-stylesheet type="text/xsl" href="king.xsl" ?>
<ROWSET>
<ROW>
<EMPNO>7839</EMPNO>
<ENAME>KING</ENAME>
</ROW>
</ROWSET>
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="/">
<INVITATION>
<TO>
<xsl:value-of select="ROWSET/ROW/ENAME"/>
<xsl:text> &; FAMILY </xsl:text>
</TO>
</INVITATION>
</xsl:template>
</xsl:stylesheet>
The error is: oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'ROWSET'.
The files are well formed (tested with XML Spy 3.5). Can you see what's the problem? or is it a bug with the parser?
help,
Alberto
null

I encountered the same problem. When I change the order of the XML and XSL files, i am the same problem.
Perhaps it's the environment AIX 4.3.3, JDK IBM 1.2.2 with JIT disable (because when JIT is enable some other problems become)??
How can i resolve this bug ?
Thanks.
null

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

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

Oracle.xml.parser.v2.XPathException: Extension functi

Hi all,
When I am trying to call an external java function in XSLT it is throwing the following exception .
Exception in thread "main" oracle.xml.parser.v2.XPathException: Extension functi
on error: Class not found 'pack/XYZ'
at oracle.xml.parser.v2.XSLExtFunctions.getConstructor(XSLExtFunctions.j
ava:166)
at oracle.xml.parser.v2.XPathExtFunction.evaluateMethod(XPathExtFunction
.java:172)
at oracle.xml.parser.v2.XPathExtFunction.getValue(XPathExtFunction.java:
137)
at oracle.xml.parser.v2.XPathExtFunction.getValue(XPathExtFunction.java:
135)
at oracle.xml.parser.v2.XSLExprBase.getStringValue(XSLExprBase.java:369)
at oracle.xml.parser.v2.XSLValueOf.processAction(XSLValueOf.java:99)
at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:369)
at oracle.xml.parser.v2.XSLResultElement.processAction(XSLResultElement.
java:176)
at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:369)
at oracle.xml.parser.v2.XSLResultElement.processAction(XSLResultElement.
java:176)
at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:369)
at oracle.xml.parser.v2.XSLTemplate.processAction(XSLTemplate.java:200)
at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplate
s.java:214)
at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplate
s.java:120)
at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:369)
at oracle.xml.parser.v2.XSLTemplate.processAction(XSLTemplate.java:200)
My small code is of XSL is:
<xsl:stylesheet version = '1.0'
xmlns:xsl='http://www.w3.org/1999/XSL/Transform' xmlns:XYZ="http://www.oracle.com/XSL/Transform/java/pack/XYZ">
<xsl:template match="PatientRecord">
<patientKey>
<LastName>
<xsl:value-of select="XYZ:getValue()"/>
</LastName>
<DOB>
<xsl:value-of select="DOB"/>
</DOB>
</patientKey>
</xsl:template>
</xsl:stylesheet>
My small code of java is :
package pack;
public class XYZ{
public String getValue(){
return "Hello World";
My small piece of XML is:
<PatientRecord>
<RecordType>P</RecordType>
<FirstName>JAVA</FirstName>
<LastName>DEVELOPER</LastName>
<SSN>737747777</SSN>
<DOB>19740310</DOB>
<DoctorID>20874</DoctorID>
<VisitReason>
Programming stress disorders
</VisitReason>
</PatientRecord>
I added the xmlparserv2.jar and xyz.jar file to classpath and XYZ.class file is in xyz.jar file .
Could any body help me if they have encounter or know the answer.
Thanks,
Reddy

This occurs because of a bug in the IBM JVM's JIT compiler. You should file a bug with IBM to get this fixed, using your stylesheet as a testcase. Lots of people have hit this problem.
Disable your JIT compiler (or switch JVM's) and you won't have the error.

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>
How are you, Conceigco
<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

Can't convert oracle.xml.parser.DTD to oracle.xml.parser.v2.DTD.

I am getting the following Error while trying
to compile the SampleMain.java file(Generating an XML document from a given Employee.dtd).
I have set my classpath to use xmlparser.jar.
D:\XMls>javac SampleMain.java
SampleMain.java:65: Can't convert oracle.xml.parser.DTD to oracle.xml.parser.v2.DTD.
main(java.l
ang.String[]).
generator.generate(dtd, doctype_name);

Would you check the java parser version you are using? If using java parser V2, the normal lib name is xmlparserv2.jar.
null

Oracle XML Parser C++ V2 - BUG

Similar Messages

Maybe you are looking for