entity handling with java extensions

stolte · January 22nd, 2008, 08:34 PM

We are using a java extension to do some more complicated data manipulation.

However, the return from the java function is using entity references instead of <>:

<tr><td class="border_left"&gt

Where as I want:

<tr><td class="border_left">

Any help is greatly appreciated.

The XSL is:

<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"
xmlns:parse="java:ViewEnergyBid"
xmlns:saxon="http://icl.com/saxon"
extension-element-prefixes="saxon">

<xsl:output method="html" encoding="UTF-8" indent="no" saxon:character-representation="native;native"/>

<xsl:template match="/">
<xsl:variable name="input">
<xsl:copy-of select="//Curve"/>
</xsl:variable>

<html>
<head/>
<body>
<table>

<xsl:value-of select="parse:buildAndParseNodeset($input) "/>

</table>
</body>
</html>

</xsl:template>

</xsl:stylesheet>

samjudson · January 23rd, 2008, 05:21 AM

What is the return value of your Java function?

If it is "String" then that is the problem. Change it to NodeSet (or whatever the correct type is) and return the XML as an object, not as its string representation.

/- Sam Judson : Wrox Technical Editor -/

mhkay · January 23rd, 2008, 05:31 AM

I think the Java method must have returned unparsed lexical XML - if it had returned a node, then the xsl:value-of would have flattened the node, and the markup would have disappeared entirely rather than being escaped. So I suspect two changes are needed: (a) return a tree of nodes rather than lexical XML, and (b) use xsl:copy-of rather than xsl:value-of.

But I always wonder with this sort of thing whether escaping into Java is really needed anyway. A lot of people do it because they haven't yet learned what can be achieved in XSLT without extensions.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference