You are viewing a plain text version of this content. The canonical link for it is here.

Posted to j-users@xalan.apache.org by Christopher Ebert <ce...@pocketthis.com> on 2003/08/13 18:41:13 UTC

RE: Different behavior when transformation is run in servlet


	You should check the version of Xalan in both environments (servlet and non-servlet) just to be sure. The servlet runner may be loading its own version of Xalan (it's likely it uses it's own ClassLoader, which would make this possible).
	Hope that helps,
		Chris

-----Original Message-----
From: Ben Ryan [mailto:b.ryan@hud.ac.uk]
Sent: Wednesday, August 13, 2003 7:53 AM
To: xalan-j-users
Subject: Different behaviour when transformation is run in servlet


Hi,
	I have developed a number of XSLT transformations that have worked fine when I run them in a standard Java application using JDK 1.4.2. I have now implemented another XSLT that is used by a servlet. The problem that I have is that when create a new Transformer using the factory method newTransformer I receive an exception stating that the call to the setMethod failed. I have traced this to the use of <xsl:output> in the XSLT file, if I remove this element then everything works.
	I have tried putting the Xalan libs I have used in the standard Java application in the common/endorsed directory to ensure that those are used and not the ones from JDK 1.4.2 but still receive the same error.
	Any help would be appreciated.

	Tech info:

	JDK 1.4.2
	Xalan 2.5.1

Regards,
	Ben 

-----------------------------------------------
Dr Ben Ryan
HLSI Software Development Manager
University of Huddersfield
Tel: 01484 473587
E-mail: b.ryan@hud.ac.uk <ma...@hud.ac.uk> 
-----------------------------------------------