Vincent Massol wrote:
From: Christopher Lenz [mailto:[EMAIL PROTECTED]]
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 ;-) ).
cool

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
I'm ok provided it will also work exactly as is for existing users (100%
backward-compatible), i.e. it will continue to work even if the
xalan/trax jars are not in the CP
I've got that now by factoring out the XSLT stuff into a separate class (XMLTransformer), and using reflection from the ServletTestRunner class to load the XMLTransformer class. Pretty ugly, but seems to work quite well.

> and the ServletTestRunner is still
able to output an XML file.
>
Something like a new "transform=true" HTTP parameter (or any better name
;-)) would be good I think.
Hmm, I'll add that then.

--
Christopher Lenz
/=/ cmlenz at gmx.de


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to