Use of Extension functions makes the XSL less portable as non-java stylesheet processors won't be able to invoke Java extensions. Besides this, I don't think there is too much of overhead in invoking an extension function( thru reflection?) from XSL, assuming extension functions do not have too much resource consuming functionality.
-----Original Message----- From: Pramodh Peddi [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 5:16 PM To: [EMAIL PROTECTED] Subject: Using Extensions Functions - its efficiency I am using JDK1.4 API for Transformation, which uses Xalan-Java internally. Is it a good idea using Extensions functions in Java language. I found myself very uncomfortable when I have complicated string processing in xsl. So, I am implementing those in Java language and calling them from XSLs. I also use Xalan's built in functions, like tokenize(), when ever available. Is that a bad practice? Does it add any performance hit? And is it bad memory-wise? Any suggestions would be appreciated! Thanks, Pramodh.
