XML parser Xalan

hello
I have downloded the XML parser Xalan
how can one instal xalan with tomcat ??
danke

Xalan is not an XML parser, it's an XSL-T engine. Xerces is the XML parser.
Tomcat has Xerces installed in TOMCAT_HOME/common/endorsed. If you need Xalan, download it and put it in that directory. - MOD

Similar Messages

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>

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

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!

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

XML parser for Java setup

I download the XML Parser for Java 3.2.1 Release from the IBM site and I have JDK1.3 installed on my Windows 2000 PC. I've placed the files "xerces.jar" and "xalan.jar" in the location specified by the extensions mechanism (i.e "C:\JDK1.3\jre\lib\ext\").
I downloaded an example where java uses XML but I get an error because it fails to import the following class:
import com.ibm.xml.parser.Parser;
Also in another application the same thing happens with this class:
import com.ibm.xml.parser.TXDocument;
If I remove the xerces and xalan JAR files from the directory mentioned above I get move errors so I presume I have the files in the right location. Do I need to place any other files in that DIR other than the xerces and xalan JAR files?
Any help greatly appreciated!

Not sure if you solved your problem.
I think Xerces was handed over to the Apache organisation by IBM and the package names were then changed so that com.ibm would have become org.apache or whatever. At a guess nobody got round to changing the examples.

XML Parser and Content-type/encoding problem

I've write a little and simple XML parser and a simple "trasformer" that recive an XML file and an XSL one and return HTML, here is the code:
public static String toHTML(Document doc, String xslSource){
 ByteArrayOutputStream testo = new ByteArrayOutputStream();
 try{
 DOMSource source = new DOMSource(doc);
 TransformerFactory tFactory = TransformerFactory.newInstance();
 System.out.println("----> " + xslSource);
 Transformer transformer = tFactory.newTransformer(new StreamSource(xslSource));
 transformer.setOutputProperty(OutputKeys.INDENT, "yes");
 transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
 transformer.setOutputProperty(OutputKeys.METHOD, "html");
 transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
 transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
 transformer.transform(source, new StreamResult(testo));
 }catch(Exception ioe){
 System.out.println("2 XMLTool.toHTML " + new java.util.Date());
 System.out.println(ioe);
 return testo.toString();
 }the problem is that I would like to put the HTML code its return into a JEditorPane; now I'm trying with this code:
JEditorPane jep1 = new JEditorPane();
jep1.setContentType("text/html");
jep1.setText(v);
// 'v' is the string returned by the code posted up (the XML/XSL transformer)but I can't see anything in my JEditorPane.
I think that the problem is this line of code that the transformer add automaticaly ad HTML code:
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">Infact if I try to delete this line from the code I can see what I want but is'n good delete a line of code without understend where is the problem.
So, can anyone help me?

good.
when u set ur output properties to html , transformer
searches for all entity references and converts accordingly.
if u r using xalan these files will be used for conversion of
Character entity references for markup-significant
output_html.properties
(this should be in templates package)
and HTMLEntities.res(should be in serialize package)
vasanth-ct

XML parser Problem in Oracle 9iAS

Dear All,
I am trying to parse a xml file by using a SAX Parser.
I am getting error "oracle.xml.parser.v2.XMLParseException: Invalid InputSource.'. I have already included 'xerces.jar' in the classpath.
But it is always taking oracle xml parser.
How to change the default XML parser in Oracle 9ias.
This is my report.jsp File
<%@ page import="java.io.*,java.util.*,java.sql.*,javax.sql.*,javax.naming.*,javax.jms.*,iims.util.*,javax.xml.parsers.*,org.xml.sax.*,org.xml.sax.helpers.*, org.w3c.dom.*"%>
<%
generateTree();
%>
<%!
 //This method is to be called during startup. It will generate the template and rule nodes.
 public static void generateTree() throws Exception
 //Proceed with this method if the template and rule trees are not built already.
 //if (nodeTemplate != null && nodeRule != null) return;
 // Validate
 Node nodeRule = parseXml("d:\\ora9ias\\j2ee\\home\\Reports\\IIMSReportsTemplate1.xml");
 }//generateTree
%>
<%!
 //parse the input file and return a node.
 private static Node parseXml(String fileName) throws Exception
 //Parse the input file
 Document objDocument = null;
 DocumentBuilder objDocumentBuilder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
 objDocument = objDocumentBuilder.parse(fileName);
 Node nodeRet = objDocument;
 return nodeRet;
 }//parseXml
%>
Report template:
<ROOT>
 <HEADINGS>
 <HEADING1>H1</HEADING1>
 <HEADING2>H2</HEADING2>
 <HEADING3>H3</HEADING3>
 <HEADING4>H4</HEADING4>
 <HEADING5>H5</HEADING5>
 <HEADING6>H6</HEADING6>
 </HEADINGS>
 <ROWSETS>
 <ROWSET>
 <COLHDRS>
 </COLHDRS>
 <ROWS>
 </ROWS>
 </ROWSET>
 </ROWSETS>
 <Footer>
 <PageNo>Generate</PageNo>
 <Date>SystemDate</Date>
 </Footer>
</ROOT>
Stack Trace:
strRuleFileD:\ora9ias\j2ee\home\Reports\IIMSReportsRules.xml
oracle.xml.parser.v2.XMLParseException: Invalid InputSource.
at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:145)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:208)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:140)
at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:96)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:165)
at iims.REPORTS.IIMSGenerateReport.parseXml(IIMSGenerateReport.java:115)
at iims.REPORTS.IIMSGenerateReport.generateTree(IIMSGenerateReport.java:
100)
at iims.REPORTS.IIMSGenerateReport.buildXML(IIMSGenerateReport.java:147)
at PCREPORT_PROCESS.processBody(PCREPORT_PROCESS.java:3248)
at PCREPORT_PROCESS.doPost(PCREPORT_PROCESS.java:100)
at PCREPORT_PROCESS.doGet(PCREPORT_PROCESS.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:244)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterC
hain.java:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:523)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:269)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpReques
tHandler.java:735)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java
:151)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
Please advise.
Thanks
Siva Kishor Rao U

Adding Xerces XML parser is not enough to make it work. Since some version of JDK (I think 1.4.X) XML parser is included and for older version it can be setup like a runtime option. And this is probably how ORACLE is using its XML parser. If you want to use different parser, you have to pass runtime option to JVM - for Xalan it looks like this:
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
...this way it becomes default parser factory used by javax interface functions. Look for documentation on xml.apache.org
Myrra

XML Parse issues when using Network Data Model LOD with Springframework 3

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

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

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?

Custom xml parser for EAR

I am trying to specify a custom XML parser for my application to use as the default BEA one does not work with Apache Axis.
I added the following to my weblogic-application.xml file:
<xml>
<parser-factory>
<saxparser-factory>org.apache.xerces.jaxp.SAXParserFactoryImpl</saxparser-factory>
<document-builder-factory>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</document-builder-factory>
<transformer-factory>org.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
</parser-factory>
</xml>
I also updated the Manifest file for my EAR to include the following:
Class-Path: APP-INF/lib/xercesImpl.jar;APP-INF/lib/xml-apis.jar
This is not working. Any ideas?
Here is the docs i am following: http://edocs.beasys.com/wls/docs81/xml/xml_appscop.html#1075700

Augie (guest) wrote:
: XML Team --
: I am a true beginner on XML, besides the basics, I am having
: problem understanding how to use the parser. We have a
project
: that requires us to form XML docs using PL/SQL (print
statements)
: and send them via FTP to our clients. Our clients will then
: parse the XML code that we put together and input the data
into
: their database. We are using XML as an EDI form.
: I downloaded the parser, and tested, but cannot understand how
to
: actually do a parse on a .xml file. Something ran and
returned,
: but I cannot get a head/tail out of them.
: My question is:
: 1. How do I parse .xml files?
I am not sure what parser or interface you are trying to use.
Our command line ones will print the output of the parse to the
screen. Our class files allow you to construct an in-memory DOM
Tree representation that can be programaticly accessed. Review
our samples to see how to do it.
: 2. After parsing, is there a flatfile with all the data? where
is
: the parsed results?
Not unless you use our print methods or pipe our commandline
versions to the screen.
: 3. Our client has Oracle 8.0.5, can the XML: Parser for C work
: independently? How do you get parsed data into the database?
All of our XML Parsers for C, C++, and Java can work
independenmt of the database. However, only the Java version is
currently configured to work with the XML SQL Utility (also
available here) to get parsed data in and out of the database.
Download it and take a look.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
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.

XML parser clashes with WL 5.1

Hello,
I see that this question has been asked before but I've seen no answer so
far. We have code that requires an XML parser. We currently us
jaxp/xerces/xalan. The version we use is more recent than the one
included in WL5.1.9. Because of this, we are getting NoClassDefFound
exceptions when deploying our apps. Or sometimes we get "No such method"
exceptions. Is there a way, short of getting the sources to all our
packages and changing the package name, to have more recent XMP parser
coexist with those of WL?
If not, what are the versions of the third-party jars bundled with WL
5.1.9? Is that information documented somewhere? We may also try to
back-port our code so it confirms to whatever version is included in WL.
Thanks,
L
Laurent Duperval <mailto:[email protected]>
La situation se cornélise à vue d'oeil!
-Alambic Talon

I have seen and dealt with this before.
I had three versions of Xerces in my classpath. I find that I have to put
the newest jar file in the front of the classpath. I had Xalan.jar and
Xerces.jar followed by XML4J followed at the end by weblogicaux.jar and my
application worked well. You can also make use of the WEB-INF/lib directory
of your application though I didn't get down to that details and solved my
methodNotFound problem by modifing the main Classpath.
Hope that helps.
IH
"Laurent Duperval" <[email protected]> wrote in message
news:3b1e30b6$[email protected]..
Hello,
I see that this question has been asked before but I've seen no answer so
far. We have code that requires an XML parser. We currently us
jaxp/xerces/xalan. The version we use is more recent than the one
included in WL5.1.9. Because of this, we are getting NoClassDefFound
exceptions when deploying our apps. Or sometimes we get "No such method"
exceptions. Is there a way, short of getting the sources to all our
packages and changing the package name, to have more recent XMP parser
coexist with those of WL?
If not, what are the versions of the third-party jars bundled with WL
5.1.9? Is that information documented somewhere? We may also try to
back-port our code so it confirms to whatever version is included in WL.
Thanks,
L
Laurent Duperval <mailto:[email protected]>
La situation se cornélise à vue d'oeil!
-Alambic Talon

Does Java have a built in XML parser?

Hi, does the JDK come with a built in XML parser? If so, from what version onwards is this available?
I'm looking at this article here:
http://www.devx.com/xml/Article/16921/0/page/3
So, I presume the answer is yes, Java comes with JAXP. I'm using JDK 1.6, does that come packaged with JAXP?
Thanks.
Rupert

rupertlssmith wrote:
Hi, does the JDK come with a built in XML parser? If so, from what version onwards is this available?
I'm looking at this article here:
http://www.devx.com/xml/Article/16921/0/page/3
You need to add three jar files--jaxp.jar, crimson.jar, and xalan.jar--to your CLASSPATH.xalan and jaxp have been in the Sun Java SDK since at least 1.4.
crimson existed in the Sun Java 1.4 SDK apparently replaced by xerces from Sun Java 1.5 SDK.

Sun ProjectX XML parser

Hi,
I need to download the Sun ProjectX XML parser. Someone know where I can find It?
The reason is that I'm using a package: com.sun.xml.tree
Thanks for any information
Amine

I don't know where I can find the file xml.jar.
I've been informed that this file is in the Sun ProjectX XML.
Does Sun ProjectX correspond to JAXP
I've foud only xerces.jar et xalan.jar in JAXP but no xml.jar.
I need this file because I'm using the package com.sun.xml.tree.
Someone have an idea?
thanks for any help!
Amine

XML parser Xalan

Similar Messages

Maybe you are looking for