----- Original Message ----- From: "Michael Brennen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 29, 2002 12:07 PM Subject: Re: Axis 1.0 Tomcat 4.1.12 Java 1.4.0_02 Installation tips
> > 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. well, there are classpaths and then there is the CLASSPATH env variable. Plus there is java/ext, but we wont go there for various reasons to do with serious classpath trouble. Adding stuff to CLASSPATH is generally dangerous because although it gets into every app, it gets into every app. Which stops you versioning things. > 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. we need to fix the install docs. saaj.jar, jaxp,jar are the specials. any xml parser if you add it. I'd also treat happyaxis.jar as more definative than the docs, as its the only one that is self testing. Plus I wrote a fair bit of it :) > 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. java1.4 has to take half the blame here -on java1.3 things 'just work' out the webapp, but java1.4 tried to "fix something" by only allowing special endorsed directories to implement javax.* and java.* classes, as they felt we idiot developers didnt know what we were doing. But in doing so they broke so many things, and axis on catalina is one of them. At least on some versons of catalina > 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. anything you add to ant_home\lib gets pulled into the classpath of all ant builds, to axis\java\lib in axis builds. So you can have stuff to hand without editing CLASSPATH. > > 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. no, not all, classpaths are a mess. Axis is a troublespot as it is banging up against java1.4/tomcat issues, and there is no one place to point the finger at to say 'its your fault'. Its our fault that the docs arent perfect, its catalinas fault for not having perfect workarounds for java1.4 funnies, and its suns fault for the endorsed dir thing in the first place. note that Suns web service dev pack is a zip of tomcat with all the stuff in the appropriate places, which is their workaround.
