Currently trying to reproduce this and... had to move the installation to another computer so... of course... the classpath had to be reconfigured, as guessed, it was DOM-4j-dev-7 that I was using. I'll dig more when I'm through with this test...

The general question of classpath is a slight (or a big?) trouble: I'd like to keep the dependencies as small as possible so I am just using a file to store all the jars that I want to use (and not make "all jars in repository" like in the maven-generated build.xml, it includes several versions of, e.g. DOM 4j !!).
This file is hand produced when I need it. But I realize now that I will not get an update of the classpath (I did not get it in my case).

How to maintain an up-to-date classpath for Jelly ?
I fear this is closer to a maven debate.

Thanks.

Paul


From: "Paul Libbrecht" <[EMAIL PROTECTED]>
To: "Jakarta Commons Users List" <[EMAIL PROTECTED]>
 (how generic is the transform tag ? I got surprised to be required to
 put xalan in, I would have expected TRaX to be used...).
The transform tag uses TRaX so it should work equally well with Saxon too.

 Yet another option could be to pass values into the stylesheet as a
 parameter.
 That sounds a bit fuzzy to me but would be definitely elegant!
 How would you do this ?
<x:transform xml="foo.xml" xslt="foo.xsl">
    <x:param name="a" value="${something}"/>
    <x:param name="b" value="${anotherThing}"/>
</x:transform>
--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to