On 27/03/2014 11:58, Stadelmann Josef wrote: > Hi Mark > > My comment below ++> > > > > > -----Ursprüngliche Nachricht----- > Von: Mark Thomas [mailto:ma...@apache.org] > Gesendet: Mittwoch, 26. März 2014 20:53 > An: Tomcat Users List > Betreff: Re: tomcat 5.5.26 misses a jar contaning > org.apache.tomcat.core.BaseInterceptor . . . > > On 26/03/2014 19:10, Stadelmann Josef wrote: >> For trouble shooting I am about to build an old version 5.5.26 of >> Apache Jakarta Tomcat > > Why not just download a binary distribution from the ASF archives? > ++> as I said, I have to trouble shoot and look at the code
You still do not need to build from source. If you want to debug a particular version of Tomcat, download the binary and the source bundles. Run the binary in JPDA mode, connect with your IDE and when your IDE asks for source code, point it at the downloaded source. > i.e. debugging it to find what triggers a background process at random > destroying all our contexts? > > ++> Also, why binary? hmmm, our Tomcat runs on OpenVMS 8.4 So? This is Java. You can still use binary distributions from the ASF. >> And I am missing a jar containing at least the following 4 members >> >> import org.apache.tomcat.core.BaseInterceptor; >> import org.apache.tomcat.core.Context; import >> org.apache.tomcat.core.ContextManager; >> import org.apache.tomcat.core.TomcatException; > > None of those classes exist in the 5.5.x branch. Neither will you find them > in 4.0.x, 4.1.x, 5.0.x, 6.0.x, 7.0.x or 8.0.x. > ++> how can you assume that 5.526 will build without this classes either as > source in a sub project or in a jar? > (which one?) It is not an assumption. It is knowledge. That knowledge is based on 10+ years as a Tomcat committer including several years where I was building 5.5.x from source multiple times on a daily basis. > Those classes are from Tomcat 3.3.x (and possibly earlier). > ++> I hope I will get it? > >> using SVN Tourtoise I to download the project; It does not build and > > Sure it does, if you follow the build instructions correctly. > Granted for 5.5.x that is more complicated than it is for 6.0.x onwards but > it is doable. > ++> OK that is motivation to startr over again, Again, you don't need to build Tomcat. > ++> BUT tell me how can it build without the mentioned classes not found by > import? > ++> when do they come down (downloaded somehow external to the sources of > 5.5.26 Again, those classes are not part of Tomcat 5.5.26. I have no interest in helping you understand how you screwed up your build environment so badly that you think you need classes from Tomcat 3.x for a Tomcat 5.5.x build. >> I cannot find the files above with this tags version > > You won't. See explanation above. > >> I have started to maven-ise this project, and are fare almost, > > Why? Why? Why? > > You have downloaded a project that uses Ant and was never structured to work > with Maven. > The chances of you getting a valid 5.5.x build using Maven are close to zero. > ++> OK,would not have done so if the ant build would build; So rather than fix the Ant build you decided to try and get it to build with Maven? Bad decision. > ++> BTW which java jdk was used for 5.5.26 builds? Tomcat is always built with the minimum Java version required by the specifications that it implements so for Java 5.5.x that would be Java 1.4. >> but struggle so far to find this members above, better I like to find >> the jar file with the package org.apache.tomcat.core > > I think you need to decide what version it is you actually want first. > ++> I just want to build tomcat 5.5.26 No you don't. And that is a major part of the problem here. What you want to be able to do is find out why contexts are getting undeployed. You have made a number of poor decisions up to this point. You need to stop and re-focus on the problem you are trying to solve. I strongly encourage you to (re-)start by looking at what triggers the undeployment process. If nothing comes of that then debugging is a possible future step but not one that would require you to build Tomcat from source. Better yet, I'll try and save you some time. Undeployment is triggered when Tomcat thinks that a WAR and/or directory has been deleted. Are all the components of your installation - including the web applications - installed on local disks? Is any form of network storage involved? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
