Rather, server-side transformation adds a runtime-dependancy to the ServletTestRunner. Due to it's usage of the TraX API, it can't be instantiated if xml-apis.jar (or JDK > 1.4) isn't available on the classpath.
I might try to factor the transformation code out into a separate class (would probably be better anyway), and let the servlet fall back to its current behaviour if TraX isn't available.
Christopher Lenz wrote:
Hi all,
I've decided to tackle the implementation of performing the XSLT transformation in the ServletTestRunner on the server, and have been successful (i.e. it works ;-) ).
However, that adds a dependancy on the TraX API (javax.xml.transform.*) and a decent implementation (aka Xalan). In JDK > 1.4 that comes for free, but not in earlier Java versions.
So, question is, is it okay for me to commit that code and add a dependancy on Xalan for the framework build? I guess it is, but want to make sure I'm not messing up on my first day as a Cactus committer :-P
-- Christopher Lenz /=/ cmlenz at gmx.de
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
