Apache XML Parser

In WebLogic 6.0, the Apache XML Parser (Xerces) and XSLT engine (Xalan) were contained
in the xmlx.jar file. They are not in this JAR file in the WLS 6.1 beta. Are
these classes no longer shipped with WebLogic Server?

Hi Shannon,
Yes, we include a built-in XML parser closely based on Apache 1.3.1 in WLS.
If you use JAXP without any specific configurations, you will be using this
parser. We also include a Xalan-2.0.1-based XSLT engine which is also
accessed via JAXP.
-Todd
Shannon Schupbach <[email protected]> wrote in message
news:3b1f94dc$[email protected]..
>
In WebLogic 6.0, the Apache XML Parser (Xerces) and XSLT engine (Xalan)were contained
in the xmlx.jar file. They are not in this JAR file in the WLS 6.1 beta.Are
these classes no longer shipped with WebLogic Server?

Similar Messages

Can't get apache to parse xml pages

have installed xmlbean cocoon jdk and still can't get apache to parse the xml pages please help...does any one have a win32 compiled mod_xml?

Ok, first thing, why are you doing anything with WAMP or XAMPP when you're running a Mac? MAMP should be what you want unless you're not explaining part of what you are trying to do.
2nd thing, I haven't used MAMP in a while, but there are two possibilities for not seeing what you want to see once you have MAMP turned on. One possibility is that you already have "Web Sharing" turned on in your Sharing Preference Pane. If that is the case, port 80 will already be taken and you'll be seeing the default Apache install (files are stored at /Library/WebServer/Documents/). This would push MAMP to either not turn on it's web serving capabilities, or to push it to another port. The other possibility is that MAMP defaults to another port anyway. So instead of localhost, you might have to type in localhost:8080 or something similar. I believe the control panel that gets installed can take you to the currently MAMP-served page, and it can also help you change which port your serving on.
80 is the default port for web serving and the ONLY port that will let you get straight to the server without having to type in webaddress.com:port# instead of just webaddress.com.

Namespaces / apache.crimson.parser / BASDA XML / HELP!!

This is probably an easy question but I can't find anyone to help me.
I am using the apache.crimson.parser to parse and validate an Xml doc against the BASDA eBIS-XML purchase order schema but i can't get the Namespaces right.
I have this at present for the Xml doc;
<Order xmlns ="urn:schemas-microsoft-com:xml-data"
xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:schemas-microsoft-com:xml-data
http://www.cs.aston.ac.uk/hillsm/project/eBIS-XML_Order_v3.01.xml">
....and this for the schema;
<Schema name="eBIS-XML_Order_v3.01.xml"
xmlns="urn:schemas-microsoft-com:xml-data"
xmlns:dt="urn:schemas-microsoft-com:datatypes">
Does anyone have any ideas??

Steven,
let me first note that I'm not familiar with the specific Schema you mention here (apparently from M$), and it would have been helpful to see at least part of it in your posting, because it seems abnormal that Microslob uses the conventional xsd namespace for schema declarations (although it wouldn't surprise me).
Anyways, let's do a first version without the xsd name space.
The declarations in your xml file are correct.
In the schema file, the first error is, that schema is misspelled as Schema. Secondly, schema does not allow a name attribute (get rid of it). There is also no reference to the namespace "http://www.w3.org/2001/SMLSchema". So, the default namespace has to be changed to that. The targetNamespace attribute specifies that this schema applies to the specified name space. Putting it all together:
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
 targetNamespace="urn:schemas-microsoft-com:xml-data"
 xmlns:dt="urn:schemas-microsoft-com:datatypes">
 
 <element name="Order" type="string"/>
</schema>So this would validate OK with this xml file (provided that ..../eBIS-XML_Order_v3.01.xml is the above schema file):
<?xml version="1.0"?>
<Order xmlns ="urn:schemas-microsoft-com:xml-data"
 xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:schemas-microsoft-com:xml-data
 http://www.cs.aston.ac.uk/hillsm/project/eBIS-XML_Order_v3.01.xml">
</Order> So, in this example, the default namespace in the schema is set to "http://www.w3.org/2001/XMLSchema" and the targetNamespace attribute points to the xml file's default name space.
However, the standard way of doing things differs. You certainly should not (mis-)set the schema's default name space to "http://www.w3.org/2001/XMLSchema".
I do not know in what way Microsoft limits you, but I strongly recommend something along these lines in order to not have regrets, headache and coffein and nicotine addiction lateron:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns="urn:schemas-microsoft-com:xml-data"
 xmlns:dt="urn:schemas-microsoft-com:datatypes"
 targetNamespace="urn:schemas-microsoft-com:xml-data">
 <xsd:element name="Order" type="xsd:string"/>
</xsd:schema>Also, in order to avoid confusion, Schema files should have the extension xsd - a minor sidepoint.
Hope that helps,
Leo.

Apache Xerces2 XML parser download?

Hello all,
where can i find Apache Xerces2 XML parser download?
Seems not working http://xerces.apache.org/xerces2-j/download.cgi
http://xerces.apache.org/xerces2-j/
thank you.
I really need it.
I am stuck with that bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6551600
Edited by: 811911 on 14 févr. 2011 05:41
Edited by: 811911 on 14 févr. 2011 05:52

http://xerces.apache.org/mirrors.cgi#binary
Also needs to be under Java 1.6

Why Oracle XML parser do not compile this file and Apache does?

Hi:
I am trying to parse this xml file:
http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/documentation/xdocs/userdocs/xsp/logicsheet-concepts.xml?rev=1.2&content-type=text/vnd.viewcvs-markup
and fails with the tag <anchor id="logicsheet"/>, if I change
"logicsheet" to "id_lg" it works fine.
Apache XML parsers do not have this problem.
Best regards, Marcelo.

I tried downloading the file and (after removing the DOCTYPE
since I didn't want to download the whole set of DTD's) it
parses fine with XDK 9.0.2C
Which XDK are you using?
If you remove the <!DOCTYPE> line for a test, does it still fail?

How can I use a 3rd party XML parser such as xerces with OC4J ?

Hi all tech experts,
I am using Oracle Application Server 10g Release 2 (10.1.2) and i have
installed Portal and Wireless and OracleAS Infrastructure on the same
computer.
i tried all the solutions on this thread
Use of Xerces Parser in out application with Oracle App Server 9.0.4
but still fighting.
I have also posted this query on OTN on following thread
How can I use a 3rd party XML parser such as xerces with OC4J?
but no reply....
Please help me on this issue.
Since OC4J is preconfigured to use the Oracle XML parser which is xmlparserv2.jar.
i have read the following article which states that
OC4J is preconfigured to use the Oracle XML parser. The Oracle XML parser is fully JAXP 1.1 compatible and will serve the needs of applications which require JAXP functionality. This approach does not require the download, installation, and configuration of additional XML parsers.
The Oracle XML parser (xmlparserv2.jar) is configured to load as a system level library of OC4J through it's inclusion as an entry in the Class-Path entry of the oc4j.jar Manifest.mf file. This results in the Oracle XML parser being used for all common deployment and packaging situations. You are not permitted to modify the Manifest.mf file of oc4j.jar.
It must be noted that configuring OC4J to run with any additional XML parser or JDBC library is not a supported configuration. We do know customers who have managed to successfully replace the system level XML parser and the Oracle JDBC drivers that ship with the product, but we do not support this type of configuration due to the possibility of unexpected system behavior and system errors that might occur from replacing the tested and certified libraries.
If you absolutely must use an additional XML parser such as xerces, then you have to start OC4J such that the xerces.jar file is loaded at a level above the OC4J system classpath. This can be accomplished using the -Xbootclasspath flag of the JRE.
i have also run the following command
java -Xbootclasspath/a:d:\xerces\xerces.jar -jar oc4j.jar
but no success.
How could i utilize my jar's like xerces.jar and xalan.jar for parsing instead of OC4J in-built parser ?
All reply will be highly appreciated.
Thnx in advance to all.
Neeraj Sidhaye
try_catch_finally @ Y !

Hi Neeraj Sidhaye,
I am trying to deploy a sample xform application to the Oracle Application Server (10.1.3). However, I encountered the class loader issue that is similar to your stuation. I tried all the three solutions but the application is still use the Oracle xml paser class. I am wondering if you have any insight about this?
Thanks for your help.
Xingsheng Qian
iPass Inc.
Here is the error message I got.
Message:
java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
Stack Trace:
org.chiba.xml.xforms.exception.XFormsException: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
     at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
     at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
     at org.chiba.xml.xforms.Container.initModels(Unknown Source)
     at org.chiba.xml.xforms.Container.init(Unknown Source)
     at org.chiba.xml.xforms.ChibaBean.init(Unknown Source)
     at org.chiba.adapter.servlet.ServletAdapter.init(ServletAdapter.java:153)
     at org.chiba.adapter.servlet.ChibaServlet.doGet(ChibaServlet.java:303)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:719)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
     at org.chiba.xml.xforms.Instance.iterateModelItems(Unknown Source)
     at org.chiba.xml.xforms.Bind.initializeModelItems(Unknown Source)
     at org.chiba.xml.xforms.Bind.init(Unknown Source)
     at org.chiba.xml.xforms.Initializer.initializeBindElements(Unknown Source)
     at org.chiba.xml.xforms.Model.modelConstruct(Unknown Source)
     at org.chiba.xml.xforms.Model.performDefault(Unknown Source)
     at org.chiba.xml.xforms.XFormsDocument.performDefault(Unknown Source)
     at org.chiba.xml.xforms.XFormsDocument.dispatchEvent(Unknown Source)
     at org.apache.xerces.dom.NodeImpl.dispatchEvent(Unknown Source)
     ... 18 more

XML parsing error: web-jsptaglibrary_1_1.dtd not found

I'm getting the following Exception while Tomcat is parsing my welcome jsp page:
exception
org.apache.jasper.JasperException: XML parsing error on file /WEB-INF/struts-template.tld: Internal Error: File /javax/servlet/jsp/resources/web-jsptaglibrary_1_1.dtd not found
 at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:227)
 at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:283)
 at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:219)
 at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:174)
 at org.apache.jasper.compiler.JspParseEventListener.processTaglibDirective(JspParseEventListener.java:1170)
 at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java:765)
 at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:125)
 at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:255)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1145)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1103)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1099)
 at org.apache.jasper.compiler.ParserController.parse(ParserController.java:214)
 at org.apache.jasper.compiler.Compiler.compile(Compiler.java:210)
 at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:548)
 at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:176)
 at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:188)
 at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
 at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98)
 at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
 at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
 at java.lang.Thread.run(Thread.java:534)
This is the reference to the dtd its not finding from the tld
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN" "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
Do you think this is a bug with the parser itself or an incompatablilty between it and the tag library?
Or am I missing something?
Thanks for any help..... Andy

Store the web-jsptaglibrary_1_1.dtd to a directory and specify the file url.
<!DOCTYPE taglib SYSTEM "file://C:/dtds/web-jsptaglibrary_1_1.dtd">

Swapping XML Parser and XSLT to Xalan 2.7.0 - Not Working (OC4J 10.1.3)

Hi-
I'm trying to use the latest Xercies/Xalan classes in OC4J 10.1.3 as described in the How-To swap XML Parsers document:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html
What I can see happening is that the oracle.xml shared library is successfully 'turned off', but the xalan libraries are not added. Instead, the default xml classes that are distributed with the JDK become visible. For instance, using a slightly modified version of the index.jsp page from the how-to, I get this result:
------ Output from JSP page ----------------
TransformerFactory Instance: org.apache.xalan.processor.TransformerFactoryImpl
Transformer Instance: org.apache.xalan.transformer.TransformerIdentityImpl
Transformer Version: Xalan Java 2.4.1 (!!)
What I expect is for that last line to say version 2.7.0, which is the version of the xalan.jar included in my shared library (code to add that line to the how-to shown below).
I suspect what is happening is that the class loader is simply not letting a shared library override a system library - to do that you probably need to place the jar files in system endorsed directory.
Has anyone gotten this how-to to work - actually replacing the XML parser/transform classes with the latest Xalan classes? Are you sure it is seeing the current version you placed in the shared library?
Thanks,
Eric Everman
---- My modified getXSLTDetails() method in the index.jsp page of the how-to -------

<%@ page import="org.apache.xalan.Version" %>
public static String getXSLTDetails()
Transformer transformer=null;
TransformerFactory transformerfactory = TransformerFactory.newInstance();
 Version ver = null;
 String br = "<" + "br" + ">"; //otherwise the otn forum chocks on the break.
try
transformer = transformerfactory.newTransformer();
 ver = (Version) transformer.getClass().forName("org.apache.xalan.Version").newInstance();
 String ret_val =
 "TransformerFactory Instance: "+transformerfactory.getClass().getName() + br +
 "Transformer Instance: "+transformer.getClass().getName() + br;
 if (ver != null) {
 ret_val = ret_val + "Transformer Version: " + ver.getVersion() + br;
 } else {
 ret_val = ret_val + "Transformer Version not Available" + br;
 return ret_val;
catch (Exception e)
e.printStackTrace();
return e.getMessage();
}--------------------------------------------------------------------

Steve - Thanks for responding on this.
The Xalan SQL extension is built into Xalan. The most painless way to try it out is to run it via JEdit: www.jedit.org
JEdit a OS Java application with a fairly painless install process (I'm assuming you already have a current JRE installed). Once its installed, you'll need to install the XSLT plugin - in JEdit goto Plugins | Plugin Manager | Install and pick the XSLT plugin. You'll need the Oracle JDBC classes on your classpath - this can be done by copying the oracle_jdbc4.jar into the [JEdit install directory]/jars directory.
Restart to load that jar and you should be all set.
I included a sample XSLT page at the bottom of this post that is somewhat of a template transform for the SQL extension - its more complicated then it needs to be, but it does some nice things with the results of the query. Save it as a file and make the appropriate changes to the 'datasource' parameter near the top of the file.
Then in JEdit, open the file and make sure the XSLT plugin is visible (Plugins | XSLT | XSLT Processor Toggle - or alternately dock it in the window via global prefs). In the XSLT plugin: Allow the current buffer to be used as the source, Add that same file as a stylesheet via the '+' button, and pick a result file at the bottom. Then click the 'Transform XML' button.
Troubleshooting: I seem to remember having some classpath errors when I tried this on windows, but others have had it work w/o issues. I do remeber that the XSLT plugin had a popup window that gave a pretty good explaintion of the problem, if it occurs. Also, for some reason the XSLT plugin will not create a new file for the output, so its often best to create a file first, then choose it as the output. Of course, you can always run a transformation from the command line or w/in an applicatoin. Full docs on the Xalan SQL extension can be found at: http://xml.apache.org/xalan-j/extensionslib.html#sql
Here is my sample XSLT transform using the SQL extension:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 xmlns:sql="http://xml.apache.org/xalan/sql"
 xmlns:str="http://exslt.org/strings"
 xmlns:xalan="http://xml.apache.org/xalan"
 extension-element-prefixes="sql str xalan">
 <xsl:output indent="yes"/>
 <xsl:param name="driver">oracle.jdbc.OracleDriver</xsl:param>
 <xsl:param name="datasource">jdbc:oracle:thin:jqpublic/jqpublic@server_name:1521:dbname</xsl:param>
 <xsl:param name="jndiDatasource"></xsl:param>
 <xsl:param name="debug">true</xsl:param>
 <xsl:variable name="connection" select="sql:new()"/>
 <xsl:variable name="uppercase" select="'ABCDEFGHIJKLMNOPQRSTUVWXYZ'"/>
 <xsl:variable name="lowercase" select="'abcdefghijklmnopqrstuvwxyz'"/>
 
 <xsl:param name="query">
 select * from (
SELECT
 'One' FIELD_1,
 'Two' FIELD_2
 FROM DUAL
 ) where rownum < 100
 </xsl:param>
 
 <xsl:variable name="connection" select="sql:new()"/>
 <xsl:template match="/">
 <xsl:choose>
 <xsl:when test="$jndiDatasource != ''">
 <xsl:if test="not(sql:connect($connection, $jndiDatasource))">
 <xsl:message>Failed to connect to db via jndi connection</xsl:message>
 <xsl:comment>Failed to connect to db via jndi connection</xsl:comment>
 <xsl:if test="$debug = 'true'">
 <xsl:copy-of select="sql:getError($connection)/ext-error"/>
 </xsl:if>
 </xsl:if>
 </xsl:when>
 <xsl:otherwise>
 <xsl:if test="not(sql:connect($connection, $driver, $datasource))">
 <xsl:message>Failed to connect to db via driver/url connection</xsl:message>
 <xsl:comment>Failed to connect to db via driver/url connection</xsl:comment>
 <xsl:if test="$debug = 'true'">
 <xsl:copy-of select="sql:getError($connection)/ext-error"/>
 </xsl:if>
 </xsl:if>
 </xsl:otherwise>
 </xsl:choose>
 
 <xsl:variable name="table" select="sql:query($connection, $query)"/>
 <xsl:if test="not($table)">
 <xsl:message>Error in Query</xsl:message>
 <xsl:copy-of select="sql:getError($connection)/ext-error"/>
 </xsl:if>
 <page>
 
 <xsl:copy-of select="xalan:checkEnvironment()"/>
 
 <meta>
 <cols>
 <xsl:apply-templates select="$table/sql/metadata/column-header"/>
 </cols>
 </meta>
 <rowset>
 
 <xsl:apply-templates select="$table/sql/row-set"/>
 </rowset>
 </page>
 <xsl:value-of select="sql:close($connection)"/>
 </xsl:template>
 <xsl:template match="row">
 <row>
 <xsl:apply-templates select="col"/>
 </row>
 </xsl:template>
 <xsl:template match="column-header">
 <col>
 <xsl:attribute name="type">
 <xsl:value-of select="@column-typename"/>
 </xsl:attribute>
 <xsl:attribute name="display-name">
 <xsl:call-template name="create-display-name"/>
 </xsl:attribute>
 <xsl:value-of select="@column-name"/>
 </col>
 </xsl:template>
 
 <xsl:template name="create-display-name">
 <xsl:variable name="col-name">
 <xsl:for-each select="str:tokenize(@column-name, '_')">
 <xsl:value-of
 select="concat(translate(substring(., 1, 1), $lowercase, $uppercase), translate(substring(.,2), $uppercase, $lowercase), ' ')"/>
 </xsl:for-each>
 </xsl:variable>
 <xsl:value-of select="substring($col-name, 1, string-length($col-name) - 1)"/>
 </xsl:template>
 
 <xsl:template match="col">
 <col>
 <xsl:attribute name="column-name"><xsl:value-of select="@column-name"/></xsl:attribute>
 <xsl:value-of select="."/>
 </col>
 </xsl:template>
</xsl:stylesheet>

IOException thrown in oracle.xml.parser.v2.XMLElement.readExternal() method

Hi,
I have a bpel process which takes in a particular xml format and does some processing asynchronously. I am calling this bpel process from a web application which uses axis web service to call this application.
Everything works fine when the xml is small (around 10 to 15 kb). But once the xml gets huge(around 250 to 400 kb) error is thrown in bpel in the oracle.xml.parser.v2.XMLElement.readExternal() method. It seems like bpel is not able to reconstruct the object that it had written to some stream before. I learnt from some forum posts that this done for optimizing performance but I would like to know whether i have to tweak something here.
Particularly what does this "java.io.IOException: Error in reading Namespace associated with the node" mean. Below is the error log
10/01/05 20:40:51 java.io.IOException: Error in reading Namespace associated with the node
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLElement.readExternal(XMLElement.java:2954)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLNode.readChildNodes(XMLNode.java:2842)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLNode.readChildNodes(XMLNode.java:2843)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLNode.readChildNodes(XMLNode.java:2843)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLNode.readChildNodes(XMLNode.java:2843)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLNode.readChildNodes(XMLNode.java:2843)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLNode.readChildNodes(XMLNode.java:2843)
10/01/05 20:40:51 at oracle.xml.parser.v2.XMLDocument.readExternal(XMLDocument.java:3394)
10/01/05 20:40:51 at com.collaxa.cube.xml.dom.SDOMHelper.loadCompressedNormalDom(SDOMHelper.java:345)
10/01/05 20:40:51 at com.collaxa.cube.xml.dom.SDOMHelper.load(SDOMHelper.java:135)
10/01/05 20:40:51 at com.collaxa.cube.xml.dom.DOMUtil.loadDocument(DOMUtil.java:2266)
10/01/05 20:40:51 at com.collaxa.cube.engine.delivery.DeliveryHelper.loadParts(DeliveryHelper.java:878)
10/01/05 20:40:51 at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:515)
10/01/05 20:40:51 at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:342)
10/01/05 20:40:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10/01/05 20:40:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10/01/05 20:40:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10/01/05 20:40:51 at java.lang.reflect.Method.invoke(Method.java:585)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
10/01/05 20:40:51 at java.security.AccessController.doPrivileged(Native Method)
10/01/05 20:40:51 at javax.security.auth.Subject.doAs(Subject.java:396)
10/01/05 20:40:51 at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
10/01/05 20:40:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
10/01/05 20:40:51 at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
10/01/05 20:40:51 at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
10/01/05 20:40:51 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
10/01/05 20:40:51 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
10/01/05 20:40:51 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
10/01/05 20:40:51 at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
10/01/05 20:40:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10/01/05 20:40:51 at java.lang.reflect.Method.invoke(Method.java:585)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
10/01/05 20:40:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
10/01/05 20:40:51 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
10/01/05 20:40:51 at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
10/01/05 20:40:51 at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
10/01/05 20:40:51 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
10/01/05 20:40:51 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
10/01/05 20:40:51 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
10/01/05 20:40:51 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
10/01/05 20:40:51 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
10/01/05 20:40:51 at java.lang.Thread.run(Thread.java:595)
10/01/05 20:40:51 0 - ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
 at com.collaxa.cube.xml.dom.SDOMHelper.loadCompressedNormalDom(SDOMHelper.java:355)
 at com.collaxa.cube.xml.dom.SDOMHelper.load(SDOMHelper.java:135)
 at com.collaxa.cube.xml.dom.DOMUtil.loadDocument(DOMUtil.java:2266)
 at com.collaxa.cube.engine.delivery.DeliveryHelper.loadParts(DeliveryHelper.java:878)
 at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:515)
 at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:342)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
 at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
 at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
 at java.lang.Thread.run(Thread.java:595)
Exception: ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
Handled As: com.collaxa.cube.CubeException
10/01/05 20:40:51 1 - ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
<2010-01-05 20:40:51,381> <ERROR> <pmf_capability_domain.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": [com.collaxa.cube.CubeException: Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
 at com.collaxa.cube.xml.dom.SDOMHelper.loadCompressedNormalDom(SDOMHelper.java:355)
 at com.collaxa.cube.xml.dom.SDOMHelper.load(SDOMHelper.java:135)
 at com.collaxa.cube.xml.dom.DOMUtil.loadDocument(DOMUtil.java:2266)
 at com.collaxa.cube.engine.delivery.DeliveryHelper.loadParts(DeliveryHelper.java:878)
 at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:515)
 at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:342)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
 at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
 at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
 at java.lang.Thread.run(Thread.java:595)
Exception: ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
Handled As: com.collaxa.cube.CubeException
] -> [com.collaxa.cube.xml.dom.DOMException: Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-09222
Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id 806601993018f2af:-5dd89d4f:125feeefac4:-7fbf. The exception reported is Error in reading Namespace associated with the node
 at com.collaxa.cube.xml.dom.SDOMHelper.loadCompressedNormalDom(SDOMHelper.java:355)
 at com.collaxa.cube.xml.dom.SDOMHelper.load(SDOMHelper.java:135)
 at com.collaxa.cube.xml.dom.DOMUtil.loadDocument(DOMUtil.java:2266)
 at com.collaxa.cube.engine.delivery.DeliveryHelper.loadParts(DeliveryHelper.java:878)
 at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:515)
 at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:342)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
 at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
 at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
 at java.lang.Thread.run(Thread.java:595)
Exception: ORABPEL-09222

I finally found the root cause of the solution. We are using axis serialization/deserialization at the client end to call the bpel service which works well for small xml. But mysteriously for larger xmls the deserialization fails at the server end when the incoming xml is being used. So we used the regular oracle java api to call the web service. This solved the problem.
We could not find whether the problem lies with Oracle SOA suite 10.1.3.1 or Apache axis 2.0. But as of now these two seem to be incompatible for large xmls at the moment.
Any pointers are welcome!

XMl parser version problem for running struts project in jdeveloper 10.1.3

Dear All.
I am trying to run a struts (v 1.2.9) based project in Jdeveloper 10.1.3.1.0.The struts version in Jdeveloper is 1.1.
when i am trying to run the index.jsp i get an error:
org.xml.sax.SAXNotRecognizedException: http://apache.org/xml/features/validation/dynamic
I think the XML parser version is a problem.Jdeveloper has OracleXMLParser v2 and i think the XML Parser apis used in building the project is different.I have placedcustiom xml parser apis and the xerces.jar in the jdevbin/jdev/lib folder and included these jar in the bootclasspath as follows:
AddVMOption -Xbootclasspath/p:../lib/xml-apis.jar
AddVMOption -Xbootclasspath/p:../lib/xerces-2.6.2.jar
But even then the Exception persists.Is the syntax for Xbootclasspath wrong or i need to place these custom api's in some other location of jdev.
I am not being able to figure out the XMl parser problem.
Any help wud be great.
Is it that i cant run the project in jdeveloper.Just to mention the application is deployed in OC4J on the server and runs fine..But its only that i kant run it locally through jdeveloper

I am also facing the same issue on my laptop. I searched for forum but no luck.
appreciate if anybody can throw some light on this.

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

Nls support with oracle xml parser in java

I'm using The JAXP interface to manipulate xml with xsl. the implementation that I use is Oracle xml parser.
My xml contains a lot of hebrew chars, and in the result stream each char translated into 5-6 chars, which makes the result to be 5-6 times bigger than it suppose to be, and harder for me to debug my application.
The client's browser shows the results well.
How can I make the transformator to transform the hebrew chars to hebrew char istead of longer and not readable string ?

Oracle XML Team wrote:
: Stephen Flinter (guest) wrote:
: : Environment: WinNT 4.0/SP4, Apache 1.3.6, JServ 1.0, Oracle
: 8.1.5
: : I have downloaded the new Java v2 XML Parser (2.0.2), and
have
: : replaced the wrapper.classpath entry in my jserv.properties
: file
: : with the path to the new parser.
: : When I rerun the "Employee Page" demo, I get the following
: : exception message:
: : [15/09/1999 11:02:22:974 GMT] java.lang.NoSuchMethodError:
: : oracle.xml.parser.v2.XSLProcessor: method
: : processXSL
: (Loracle/xml/parser/v2/XSLStylesheet;Loracle/xml/parser
: : /v2/XMLDocument;)Lorg/w3c/dom/DocumentFragment; not found
: : at oracle.xml.xsql.XSLHelper.process(XSLHelper.java:34)
: : at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java,
: : Compiled Code)
: : at
: : javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
: : at
: : javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
: : at
: : org.apache.jserv.JServConnection.processRequest
: (JServConnection.j
: : ava)
: : at
: : org.apache.jserv.JServConnection.run(JServConnection.java)
: : at java.lang.Thread.run(Thread.java:479)
: : This demo was works fine with the parser shipped with the
: : xsql_servlet download.
: : Regards,
: : Steve
: Version 2.0.2 uses the August XSLT WD which is incompatible
with
: the April WD on which our previous releases including the demos
: were based.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
Hi,
Can someone from the Oracle XML Team point us to a fix so we can
continue our testing???
Steve...
null

XML Parsing in Java Stored Proc--Oracle XML Support Installation?

I am working with a third party product that is having difficulty running a java stored proc that is parsing a supplied XML file. The proc basically looks like:
import java.io.IOException;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import org.w3c.dom.Document;
import org.xml.sax.SAXException;
InputStream is = getXMLAsInputStream(xml);
try {
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse( is );
... parse the document ....
catch (FactoryConfigurationError e) {
// unable to get a document builder factory
We are running on 9.2.0.6, HP-UX 64-bit. At first, when we would attempt to run the proc, a database hang would occur; now after attempting to install using loadjava jars for xerces2.6: ORA-29532: Java call terminated by uncaught Java exception:
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found)
The vendor says that the errors we are getting when running are not due to any dependency on xerces or jre1.4, and that we need to "install Oracle XML support", but I'm not certain what this means (I cannot find any documentation on what to install). I believe that there are jars that need to be loaded into the database to support the XML parsing, as jre1.3 does not include built-in XML support, and Oracle 9.2.0.6 uses jre1.3.
So...does anyone have any thoughts as to how to resolve the missing references? Is there a way to "install Oracle XML support", or is it to install the necessary jars?
Thanks,
Candi

Candi,
The following resources should be of help:
Oracle9i Database Release 2 (9.2) Documentation Library
In particular, check out the following:
Java Developer's Guide
Java Stored Procedures Developer's Guide
XML API Reference - XDK and Oracle XML DB
XML Database Developer's Guide - Oracle XML DB
XML Developer's Kits Guide - XDK
If that doesn't help, then try the following:
OracleJVM and Java Stored Procedures
XML Technology Center
Good Luck,
Avi.

Problem in IAS Server with generation of PDF with FOP and XML parsing

Dear co.forumers :
We are developing an application that generates a pdf document with FOP Apache utilities, and this PDf is stored in a folder of the server. Firts of all, a DDBB data is retrieved using java ( jdbc) middleware classes ( servlets ), and with these data, the pdf is generated using FOP. In these process, he data retrieved from the DDBB is converted in a XML file , and the with the XSL FOP utility, the pdf is generated.
In the other hand, we have another application that consults data from a java beans, using a JSP, generates a XML with the data of the beans, and with this XML, and with a XSL file generates and html , with the data and fixed text.
Both applications have been deployed as a separated WebApp in the IAS. Both use Xalan as XML parser amb Xerces is used aswell.
So, the problem is , after generating a pdf with the firts application, every html generated via JSP-XML-XSL transformation in the second application is shown completelly bad formated. All fixed text are wrongly composed, and the text that should appear in textFields and ComboBoxes is also bad formated. The XML with the data is well generated, so the problem is in the parsing of these XML and the conversion in html through XSL. We have to re-initiate the server and then everything goes well again. If no pdf is launched, no problem occurs with the other application.
How an a WEB APP pplication can affect to another, installed both in different folders of the IAS ? We tried to change Xalan version and FOP version, but no result.
Is this a Poltergeist ?? and X file , maybe ?
Has anyone had the same problem ?
Pleae, any help will be very wellcomed.

A PDF document may be generated in the JDeveloper OC4J server.
http://www.oracle.com/technology/pub/notes/technote_vohra_fop.html

NullPointerException at org.apache.crimson.parser.Parser2.parseInternal

I've tried to use JavaTM API for XML Processing (JAXP), particulary default SAX parser,
which is embeded into JAXP.
I downloaded jaxp-1_1.zip file from http://java.sun.com/xml/download.html, extacted it
and included crimson.jar, jaxp.jar and xalan.jar to java CLASSPATH.
After that I'd tried to parse XML document
with following code
     // prepare SAX parser
SAXParserFactory factory = SAXParserFactory.newInstance();
DefaultHandler handler = new XMLHandler();
try {
// Create a JAXP SAXParser
SAXParser saxParser = factory.newSAXParser();
// url
File file = new File( fileName );
String url = file.toURL().toString();
System.out.println( "URL: " + url );
// parse
saxParser.parse( url, handler );
} catch (Exception ex) {
ex.printStackTrace();
throw ex;
and obtained the message below
java.lang.NullPointerException
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:523)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:232)
     at com.darout.bot.parser.PObjectsBuilder.parse(PObjectsBuilder.java:54)
     at TestSAXParser.main(TestSAXParser.java:22)
Could you help me?

I've found an error. It was in my handler implementation.
But is it possible to trace a handler exception correctly?

Apache XML Parser

Similar Messages

Maybe you are looking for