----- Original Message ----- From: <[EMAIL PROTECTED]> > > In earlier off-line conversations, I've expressed support for the idea > of having XSLTC (Xalan-J Compiled) generate Java source code, rather than > byte code. However, at that time I didn't realize that there is no Java > API for compiling Java source code to byte code, and that this change would > necessarily entail a separate compilation step outside of the framework of > JAXP, until such a Java API becomes available. >
There is one in progress: http://www.jcp.org/en/jsr/detail?id=199 However, there's still the issue of backward compatibility with older implementations of Java that do not implement JSR 199. This is a serious drawback of this approach. > I'm worried about cutting off support for users who need the > performance of XSLTC but who can't precompile their stylesheets. So am I. We need to evaluate the pros and the cons and perhaps get some feedback from the Xalan community before making this decision final. -- Santiago
