Me again...

For the records xsl works fine with jakarta-taglibs-standard-1.1.0-B1 and Tomcat 4.1.27! However, B1 is of course a beta, and generates some suspicious error messages when starting tomcat.

Now, I still wonder if I really am the only one to experience these problems? A simple xsl transformation such as this should be fairly commonplace. However, I can't find any information about pecularities or bugs on the web or on this list.

cheers

/Petter



Petter Karlstr�m wrote:

Hi,

The problem quoted below is still driving me up the walls!

Now, I've also tried installing the taglibs in /common/lib/ (instead of the app's lib) and fixed some presumably unrelated differences between the server.xml files.

Am I the only one to have this problem?

I want to try installing version 4.1.12 on my Windows machine, but I fail to find any old versions for download. Anyone know where I can find one?


Petter Karlstr�m wrote:


Hi all,

I'm trying to get a simple <x:transform> to work after moving to a new version of Tomcat. The old version was 4.1.12 and the new one is 4.1.27.

The JSTL .jars are installed in my application's /WEB-INF/lib/ I've tried version 1.0.3 of the taglibs as well as older ones with the new tomcat.

Here's a code snippet:

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

<c:import url="test.xml" var="xmlfile" />
<c:import url="test.xsl" var="stylesheet" />

<x:transform xslt="${stylesheet}" xml="${xmlfile}" />


This works fine on my 4.1.12 on Solaris. However, 4.1.27 on Windows and Linux generates
org.apache.jasper.JasperException: The output format must have a '{http://xml.apache.org/xalan}content-handler' property!


Any clues?

/Petter Karlstrom






--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to