----- Original Message ----- From: "Heitzso" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 14, 2002 7:19 AM Subject: Re: List with HTTP servers on with AXIS installs and runs?
> Just want to flag that this problem gets thrashed on the email > list about once a week, which is probably why others didn't respond > right away. > > Tomcat 4.0.something tries to insure that a war file cannot > run java.blat and javax.blat class files from its WEB-INF/lib and > perhaps circumvent security thereby. > > Axis tries to be on the bleeding edge of standards, and hence > requires the use of jaxrpc et al. You cannot put these files in > WEB-INF/lib because tomcat-trying-to-be-secure ignores them. > > You have a couple of solutions, depending on the JVM you're using. > > With JVM 1.4.x the simplest thing is to use > -Djava.endorsed.dirs=path-to-axis-lib > > Otherwise you need to get these files loaded in a basic way into > the classpath. With tomcat 4.0.3 you typically put a single jar > into the classpath and then, on the way up, tomcat scrounges > around and picks up extra jars from it's lib directories. > > Now the above description may not be quite perfect, but I believe > it's close to reality. Where I get fuzzy is the class ordering > between jre extension library directories, the java.endorsed.dirs > directories, classpath, tomcat common and other lib directories, > et al. > > Note that if you use 1.4.0 jvm I believe you have to use > java.endorsed.dirs because the jvm ships with some standard > extensions that are not up to snuff for bleeding edge axis. > > One other odd maybe-true info point is a rumor that tomcat > 4.0.4 can be configured to use java/javax files in WEB-INF/lib > to make life easier. > > Please don't be harsh on this list. I've been monitoring it > for awhile and I've seen this problem and variations on the > solution mentioned a good dozen times over the past few > months. If you searched the archives you may have missed > the info because it tended to focus on the jvm more than on > the servlet container. I'll start putting together a *Better* install doc; then open it up for contribs for people on this list to flesh out. Remember, even if you dont want contribute to the axis code, you can always help with the docs. Its easy, and your changes are far more likely to be accepted, cos they rarely break anything. The other thing I plan to add to axis is a status JSP page that looks at the system and decides if it is happy or not. I do that with a full happiness taglib here at work, but I will be minimalist and just code inside the JSP for now. So, take the attached JSP page, put in webapps/axis, and fetch it. If it complains, you have a problem. If it doesnt complain, you still may have a problem. we can add more tests and advice here...maybe even print urls to the axis web site with specific config hints. -steve
happyaxis.jsp
Description: Binary data
