C
Chris Bedford
Hello,
I'm using Xalan and I have a bunch of xslt documents that were
constructed to run with another processor that has alot of custom
extension functions. The names of these functions sometimes have
dashes in them:
e.g., a function might be called: do-something
ane might be used like this:
<xsl:value-of select="do-something(.)"/>
My problem is that as far as I can tell with the xalan extension
mechanism
one's java class functions must be identical to the name of the xslt
function you are providing the extension for... Thus I don't see how
could specify that the do-something xslt function is to be implemented
by a java class like this:
public class Something {
public String doSomething(String input) { return input +
"whatever"; }
}
Java naming conventions prevent me from doing this ->
public class Something {
public String do-something(String input) { return input +
"whatever"; }
}
I'm wondering if there is some kind of aliasing trick in the xalan
extensions mechanism to make this work.
Thanks !
- Chris
I'm using Xalan and I have a bunch of xslt documents that were
constructed to run with another processor that has alot of custom
extension functions. The names of these functions sometimes have
dashes in them:
e.g., a function might be called: do-something
ane might be used like this:
<xsl:value-of select="do-something(.)"/>
My problem is that as far as I can tell with the xalan extension
mechanism
one's java class functions must be identical to the name of the xslt
function you are providing the extension for... Thus I don't see how
could specify that the do-something xslt function is to be implemented
by a java class like this:
public class Something {
public String doSomething(String input) { return input +
"whatever"; }
}
Java naming conventions prevent me from doing this ->
public class Something {
public String do-something(String input) { return input +
"whatever"; }
}
I'm wondering if there is some kind of aliasing trick in the xalan
extensions mechanism to make this work.
Thanks !
- Chris