Murray Altheim wrote:
James Deegan wrote:
Vadim,
Belated but sincere thanks to you for helping me get Xindice 1.1b3 running! (I sent e-mail 1/20 subject "Problem Initializing Xindice.") Your instructions were precise and took care not to berate the ignorance of a newbie such as myself.
I do have another question: As my projects in Java grow in number and size, I'm finding it difficult to manage JARs, especially in a Windows environment. As you explained, Tomcat ignores the CLASSPATH. But for applications that require JARs in the CLASSPATH, and that may need to run concurrently, can batch file(s) prevent JARs logjams and/or running out of environment space? I've maxed out the latter in Windows/DOS; is this also a problem for Linux, Solaris, et al.? Putting required JARs in the %JAVA_HOME%/jre/lib/extcan folder is a workaround, but can you recommend a better, possibly programmatic, solution to this problem?
Highest Regards, Jim Deegan [EMAIL PROTECTED]
Jim,
I've found that managing classpaths, potentially complex classpaths even, is manageable using ant. I used to keep my classpaths in my .cshrc file, but now I do everything Java-related in ant's build.xml files. Well, everything except mention in .cshrc where the binaries for Java are.
In addition to Ant, there are two more ways to long classpath problem:
1. Use Class-Path entry in the MANIFEST.MF. For example, see batik-rasterizer.jar from the Batik.
2. Use small utility class to create classloader with all libraries in a given directory. See
cocoon-2.1/tools/src/loader/Loader.java
Vadim
