Wrox Programmer Forums
Go Back   Wrox Programmer Forums > XML > XSLT
XSLT General questions and answers about XSLT. For issues strictly specific to the book XSLT 1.1 Programmers Reference, please post to that forum instead.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the XSLT section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old May 15th, 2007, 10:48 AM
Authorized User
Join Date: May 2007
Posts: 19
Thanks: 0
Thanked 0 Times in 0 Posts
Default <xsl:output method=”xhtml”> problem

Hi. everyone
I’m using Tomcat server to develop a web application which requires developing an xslt stylesheet to transform xml doc into xhtml doc.
In addition, xslt version 2.0 allows us to use
<xsl:output method=”xhtml”>. However, when I run my application the Tomcat is crashed and I get this error message.

Error: ‘jndi:/localhost/WEB-INF/classes/xslt/xxx.xslt: line 8: The method attribute of an <xsl:output> element had the value ‘xhtml’. The value must be one of xml, html, text, or qname-but-not-ncname’
FATAL ERROR: ‘Could not compile stylesheet’

Any clue?

Old May 16th, 2007, 05:22 AM
Friend of Wrox
Join Date: Jul 2006
Posts: 430
Thanks: 28
Thanked 5 Times in 5 Posts
Send a message via Yahoo to bonekrusher

Hi Did you try "html"?

Old May 16th, 2007, 08:46 AM
Authorized User
Join Date: May 2007
Posts: 19
Thanks: 0
Thanked 0 Times in 0 Posts

thanks bonekrusher 4 ur reply.

html is working fine, but i need to convert my xml doc into xhtml.

it is possible by replacing html by xml, but it comes with JavaScript problems.

Old May 16th, 2007, 09:09 AM
Authorized User
Join Date: Apr 2007
Posts: 38
Thanks: 0
Thanked 0 Times in 0 Posts

Are you sure the html output isn't already xhtml?

I'm using the following:
<xsl:output method="html" indent="no" encoding="iso-8859-1"
  doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
  omit-xml-declaration="yes" />

...and my resulting page validates as xhtml 1.0 strict:


Old May 16th, 2007, 10:00 AM
Authorized User
Join Date: May 2007
Posts: 19
Thanks: 0
Thanked 0 Times in 0 Posts

Yes it is. But the reason behind my question is that when I use <xsl:output method="html"> I faced no problem with parsing JavaScript which embedded in xslt file. However, using <xsl:output method="xml"> instead, results in parsing problem of JavaScript. Despite the fact that I placed all JavaScript code between <[!CDATA[[ and ]]>.
I tried another way by placing all JavaScript in an external JavaScript file and import it to xslt file like this
<script src="validation.js" type="text/javascript"></script>
 but xslt failed to import this file even though they are in same directory.

Please help

Old May 16th, 2007, 10:45 AM
mhkay's Avatar
Wrox Author
Join Date: Apr 2004
Posts: 4,962
Thanks: 0
Thanked 292 Times in 287 Posts

This element

<script src="validation.js" type="text/javascript"></script>

will be copied by the XSLT processor to the result document just like any other. What makes you think the XSLT processor will treat it specially by "importing the script"? As with all other elements in the result tree, it only acquires a meaning when the browser takes over.

Michael Kay
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

Similar Threads
Thread Thread Starter Forum Replies Last Post
embedded <xsl:element> into <xsl:with-param> petergoodman XSLT 2 July 9th, 2008 06:36 AM
Performance for <xsl:import> and <xsl:include> vikkiefd XSLT 2 April 16th, 2008 08:06 AM
<xsl:output method=”xhtml”> crashes Tomcat li72 XSLT 1 August 13th, 2007 07:30 AM
<xsl:choose> and <xsl:otherwise> problem djmarquette XSLT 4 January 21st, 2005 01:56 PM
problem using <xsl:attribute> arvin XSLT 2 July 21st, 2003 03:13 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.