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-26       - By Valeria P.
Reply:     1     2     3     4     5     6  

Hi Henry,

thank you very much for going so deeply into the possible cause of this
error.
I will try re-compiling the class (I have to download the sources because I
only have the jars) and I will let you know what happens.

After trying everything to be sure no other package would override the
TransformerFactory, I thought I had succeeded in that because the error
message came from Xalan, which means the system know that it has to use
Xalan's TransformerFactory, and because the CheckEnvironment() method,
called from within the jsp page, showed that I was using the correct version
of Xalan. But what you says sounds quite convincing and I think I have to go
in that direction.

Thank you very much,

Valeria


----- Original Message -----
From: "Henry Zongaro" <zongaro@(protected)>
To: "Valeria P." <valeriapesce@(protected)>
Cc: "Erin Harris" <eharris@(protected)>; <xalan-j-users@(protected)>
Sent: Tuesday, October 24, 2006 4:59 PM
Subject: Fw: Xalan and jstl 1.1 problem with transform tag


> Hi, Valeria.
>
> Henry Zongaro/Toronto/IBM wrote on 2006-10-24 10:50:05 AM:
>> There's something fishy about the error message in your note.
>>
>> > javax.xml.transform.TransformerFactoryConfigurationError: Provider
>> > org.apache.xalan.transformer.TransformerImpl could not be
> instantiated:
>> > java.lang.InstantiationException:
>> > org.apache.xalan.transformer.TransformerImpl
>>
>> That message would ordinarily be reported when the
>> TransformerFactory.newInstance() method fails to create an instance
>> of the TransformerFactory implementation class, but in this case
>> it's reporting the name of the Transformer implementation class
>> instead.  Perhaps some component is overriding the javax.xml.
>> transform.TransformerFactory system property with this wrong value.
>> I know that probably doesn't help you resolve the problem, but maybe
>> we can narrow it down further.
>
> There is a debug flag in the javax.xml.transform.FactoryFinder class (in
> xml-commons).  If you're inclined to try, one thing you might do is
> recompile that file with the debug flag set to true, and replace the
> version of that class in xml-apis.jar.  That might give a clue as to where
> the faulty setting for javax.xml.transform.TransformerFactory comes from.
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro      XSLT Processors Development
> IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
> mailto:zongaro@(protected)
>