Morris Kwan wrote:
An alternative would be to add an extension attribute to xsl:param. Something like xsltc:type that a user can set to the runtime type of the parameter. This type would be either an XSLT built-in type or a Java class type. The advantage of this approach is that there's no need for reflection and dynamic lookups. It should be relatively simple to implement too.Supporting this paramter passing scenario requires a runtime method resolving feature in XSLTC. You can also see this note (http://marc.theaimsgroup.com/?l=xalan-dev&m=106250879605900&w=2) for information.
There would be a problem if a stylesheet uses the same parameter to pass objects of different types, but in that case, one could argue that the stylesheet is a bit hacky anyways. Interpretive Xalan can just ignore the XSLTC extension.
-- Santiago
