On Mon, 28 Oct 2002, Steve Loughran wrote: > > Another thing I noticed is that if you provide some incorrect path in the > > CLASSPATH variable, even if you correct it by editing it it is likely that > > the new path aren't correctly recognised. > > So it is necessary to startup the machine again or to delete and provide the > > CLASSPATH variable again. Ignoring this (like me in the past) can make > > people waste a lot of time. > > That's why I dont recommend messing with classpaths. I run java > with an empty CLASSPATH variable, and my life is better for it. > > I recommend you put the jars containing javax.* code (jax-rpc, > saaj, xerces) in the CATALINA_HOME/common/lib, where they all > get picked up properly. The happyaxis.jsp page says exactly the > same thing.
Okay, I'm willing to be the idiot that asks the stupid question with the obvious answer that everyone else knows. :) How do you get things to run with an empty CLASSPATH? I thought jar files had to be specifically included in order to make their contents available. There is a hint in happyaxis.jsp that is displayed if there are errors. However, it does not give specific .jar names to move. If jax-rpc and saaj fall in that hinted category, that directly conflicts with the axis setup instructions. For those of us that don't yet have the detailed knowledge of this stuff, we need step by step procedures that work; once that happens we'll start to sort it out in the building. With 26 years writing code from micro and mainframe assembler to C to perl to php and now java, I don't lack experience, but I do lack specific details in this area as it is fairly new to me. Everywhere I turn with axis/tomcat there are non obvious, non documented CLASSPATH problems that are the cause of most of the problems in what I've done so far. For example, I built axis from source last night and found problems there because I did not have servlet.jar included in CLASSPATH when I ran 'ant compile'; the problem only turned up later in run time when the compiled jars blew up with servlet problems. When I recompiled with servlet.jar available to ant the error disappeared. Is that the right solution? I don't really know, but looking at the error it seemed to be a thing to try, and somehow it worked. Sorry if I'm asking stupid questions but these are very real problems that I've run into that have to be sorted out very tediously one by one. It sounds like I'm not the only one having trouble following the given directions. Steve, I'm sure there is some frustration readable here; it is *not* directed at you or anyone else. Lest I be flamed for demanding without giving, I'll be glad to pitch in as I can on the project; I understand open source well as we support our own open source product (fishcart.org). I just have to get to the point where I know what de heck I be doing. Thanks for the ear... -- Michael
