Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Xalan and jstl 1.1 problem with transform tag

Xalan and jstl 1.1 problem with transform tag

2006-10-23       - By Valeria P.
Reply:     1     2     3     4     5     6  

Hallo,
I have this problem that I could not solve although I tried all the
suggestions I could find in manuals and in forums/lists archives.

I developed a simple XML based document repository using JSTL xml tags 1.0
under Tomcat 4.0.
Now I am trying to do the same with Tomcat 5 using JSTL 1.1 but I keep
receiving an error message about the instantiation of the transformer:

javax.xml.transform.TransformerFactoryConfigurationError: Provider
org.apache.xalan.transformer.TransformerImpl could not be instantiated:
java.lang.InstantiationException:
org.apache.xalan.transformer.TransformerImpl

I did the following to overcome the problem:
1) download the latest versions of xalan.jar, xercesImpl.jar and
xml-apis.jar and place them under the WEB-inf directory of my application
2) (just to be sure to override any existing old package including the same
classes) place the same files under TOMCAT_HOME/common/endorsed and
JAVA_HOME/lib/endorsed
3) add:
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp
.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor
.TransformerFactoryImpl
both to JAVA_OPTS and CATALINA_OPTS

I also tried the CheckEnvironment method and it appears I am running the
correct version of Xalan.

Other details about my test environment:
- Windows XP
- JRE 1.5.0
- Tomcat 5.5.12
- A CMS compliant with Tomcat 5 and coming with JSTL 1.1 libraries
(InfoGlue: www.infoglue.org)

This is my very simple transformer page (very very basic as you can see):

<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>

<c:import var="xmlText" url="${requestScope.xmlUrl}" />
<c:import var="xslText" url="${requestScope.xslUrl}" />
<c:catch var="ex">
 <x:transform xslt="${xslText}" doc="${xmlText}"></x:transform>
</c:catch>
<c:if test="${not empty ex}">
 <c:out value="${ex}" />
</c:if>

The request-scoped variables contain what they should (I tested them
importing directly to the page without storing the imported contents in
variables).

I really don't know what else to try.

Thank you to those who had the patience to read and to those who will be so
kind to reply.

Valeria