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.
Problem using compiled translets with Xalan !!

Problem using compiled translets with Xalan !!

2006-09-01       - By Henry Zongaro
Reply:     1     2     3     4     5     6  

Hi, Ambika.

<Ambika.Das@(protected)> wrote on 2006-09-01 04:26:44 AM:
> 1.   Compile the XSL files into .class files using XSLTC API and put
> in the WEB-INF/classes directory of the web application.
> 2.   For each transformation, construct a transformer factory and set
> use-classpath attribute to true.
> 3.   Construct a StreamSource object out of the translet name.
> 4.   Construct a transformer object out of the transformer factory by
> passing the StreamSource object.
> 5.   Call transformer.transform() to perform the transformation.
>
> JDK 1.4.2 ships with a default JAXP implementation which conflicts with
> Xalan 2.7.0. For this we have put the latest built jar files in
> $JAJA_HOME/jre/endorsed directory.
>
> Please let us know if this approach is correct for multiple
> transformations.

That approach seems reasonable, and wouldn't constitute a usage error, so
far as I can tell.

> The stack trace is as follows.
>
>         ... 15 more
> ERROR:  'Content is not allowed in prolog.'
> ERROR:  'org.apache.xml.utils.WrappedRuntimeException: Content is not
> allowed in
>  prolog.'
> javax.xml.transform.TransformerException:
> javax.xml.transform.TransformerExcepti
> on: org.apache.xml.utils.WrappedRuntimeException: Content is not allowed
> in prol
> og.
>         at
> org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl
> .java:640)

The error message that you're seeing is a Xerces error message.  How is
the input to the transform step being constructed?  What kind of Source
object is involved:  StreamSource, SAXSource or DOMSource?

> Some times we are also getting ArrayIndexOutOfBoundsException.

We would need to see at least the traceback, if not a complete test case
to be able to determine what is going on here.

Thanks,

Henry
------------------------------------------------------------------
Henry Zongaro      XSLT Processors Development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@(protected)