Thank you very much Henry, that works nicely. I was solving the problem
by generating a key and access my data through a singleton but now I can
get rid of it.
BTW, I use the extension to access external content because implementing
an URIResolver did not work for me. So I return my content as a w3c DOM.
Would be using an URIResolver faster (as I may be able to return the
content as SAX stream)?
Can I also return the content as a DTM or any other internal XSLTC
structure - or does this work for Xalan only?
Thx,
Nils
Henry Zongaro schrieb:
The documentation on using Java extensions in XSLTC is poor. Reading
the code, the processor tries to use static information about the types of
arguments to determine which method to invoke. In the case of a
stylesheet parameter, it has no static information about the type, so it's
only able to match the argument to java.lang.Object.
You could try making a static method on your class that accepts a
java.lang.Object. Assuming all the instance methods derive from a common
base class, you could then cast the Object to the base class, and invoke
the method you really want to use.
I hope that helps.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
