Hi, I'm trying to port XSLTC maps with Java extensions from Saxon to XSLTC 2.4.1. I'm running into trouble with DOM use inside the extension java code. After receiving a NodeList as a parameter of the java extension method, I use item(0) to extract an Element object, but all I get is an org.apache.xalan.xsltc.dom.DOMImpl$NodeImpl object with node type ELEMENT_NODE. This class implements Node, but I need Element.
Is this as expected/designed or am I doing something wrong? I am using xsltc.jar of Xalan 2.4.1 with xalan.jar of Xalan 2.0.1; could this be the cause? I heard that XSLTC is generally independent of Xalan, but extensions could be an issue. Can anybody elaborate on this? Is there a workaround to get an Element object? I need access to various methods in the DOM interface because we do quite a bit of navigating the DOM tree inside the extension. I am already thinking of writing a wrapper around the NodeImpl class implementing the Element interface, but that would get ugly. Thanks for any hints, zak :-) __________________________________________________________________ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
