> From: Srinivas Ivaturi [mailto:[EMAIL PROTECTED]
> It is not that it wont work , It is by design.
OK. So, to summarise:
- You have a set of jars that is too large to name on the classpath in
Windows;
- The jars are required for one webapp only, not for the whole of Tomcat
(so one could argue that a classpath-based solution is a poor solution
as it might interfere with other webapps deployed in the same
container);
- The jars would work if placed in the webapp's lib directory.
You don't wish to place the jars into the webapp's lib directory "by
design", which prevents a simple solution that would apparently work.
If it doesn't work, I can't help much more unless you can give some more
information about why it doesn't work or why you'd prefer not to do
this.
I'm not aware of another solution that would work without amending the
Tomcat source and recompiling. I don't think you can extend the
classpath in conf/server.xml or in web.xml (although I could be wrong;
this is from a fairly quick check). So the only alternative I can think
of is to deploy an entire custom version of Tomcat.
Anyone else?
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
