RE: Classpath Conundrum (2nd try)

2003-07-18 Thread Thomas Davis
For the sake of argument, I moved all the classes from /native into /WEB-INF/classes and I moved all the classes from /foreign into /WEB-INF/lib. Also, for the sake of being extra careful, I packaged up everthing in /WEB-INF/lib into classes.jar (so there's two copies there, the raw directory tree

RE: Classpath Conundrum (2nd try)

2003-07-17 Thread Thomas Davis
--- "Cox, Charlie" <[EMAIL PROTECTED]> wrote: > can't you just set up an ant script to (also)copy the files to the > tomcat directory each time they are updated? Unfortunately, I cannot. I must, if possible, get it working with the existing directory structure. I realize this is not an optimal

RE: Classpath Conundrum (2nd try)

2003-07-17 Thread Thomas Davis
--- "Shapira, Yoav" <[EMAIL PROTECTED]> wrote: > > Searching the list archives reveals that every now and then someone > comes along with your situation Could you please refer me to one of those threads? I checked the archives before posting here and was unable to find any discussions that res

RE: Classpath Conundrum (2nd try)

2003-07-17 Thread Thomas Davis
--- Norris Shelton <[EMAIL PROTECTED]> wrote: > Remember, these changes were for W2K PRO, should work on other > environments but YMMV. > > setclasspath.bat > set CLASSPATH=%CLASSPATH%;%JAVA_HOME%\lib\tools.jar > I added %CLASSPATH% after the = sign Thanks for the tip. I tried that (which

RE: Classpath Conundrum (2nd try)

2003-07-17 Thread Thomas Davis
--- Norris Shelton <[EMAIL PROTECTED]> wrote: > > To start our Tomcat's on W2K, we modify setclasspath.bat to > include %CLASSPATH% when it constructs it's classpath. I tried that but could not get it to work. I'm apparently putting it in the wrong place. Could you please detail the change(s)

Classpath Conundrum (2nd try)

2003-07-17 Thread Thomas Davis
[I apologize is this message is a dupe. I had trouble sending messages to this group from a hotmail account.] I have been tasked with trying to get a legacy Java Servlet based application running under Tomcat 4.1.24 -- The application currently runs on JRun 2.3.3 On of the requirements imposed u