Ulrich,
I did. It is there because I need to be able to construct a real classpath (i.e. c:\...jsplibs\jasper-compiler.jar;c:\...\jsplibs\....) to hand to the JSP compiling subsystem. I cannot leavethe jars in the SAR-INF/lib dir as they location of that is hidden from phoenix users.Joerg Buchberger wrote:Ulrich,
do you mean jasper-compiler.jar is included in the sevak-jetty-demo.sar?Exactly.How come your jasper-compiler.jar / jasper-runtime.jar is within jsplibs (don't know this dir)?
I don't know who made the decision to build it this way. I am just reporting it here.
In order to have the jars needed for jetty in the classpath, I recommend to copy the above mentioned jars to sevak/lib/jetty-jars.
Then build the sevak-jetty-sar again using ant.
I have no need of this manual copy as the distro works for me*
* I have done a fresh CVS get of servk, and 'ant -f sevak.xml sar' to make the sevak-jetty-demo.sar SAR file and then deployed that to phoenix 4.0.2. (and HEAD revision). I can confirm that *everything* works fine for me. I need not copy any other jars anywhere.
Yes, that is a possibility. But I think it would be much better to fix the Sevak distribution :)
I'm running JDK1.4.1. I did copy the tools.jar to phoenix/lib.
Enjoy,
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>