Ok, I set the build-tests-tomcat-40.xml stuff identical to yours, didn't change my server.xml from the current checked-in version, modify my web.xml (see below) and everything works for me.
When you say you don't want to change web.xml, what exactly do you mean? Don't change it period or don't change it because it's the same as what Tomcat ships with (almost). When I compared to what Tomcat ships with, they have 4 blocks commented out: SSI definition, CGI definition, SSI mapping, CGI mapping. When I comment these blocks out as well everything works great. As for the missing java classes, I'm pretty sure it's because the jars aren't present in the default Tomcat configuration. In my %TOMCAT_HOME%/server/lib directory, I have "servlets-cgi.renametojar" and "servlets-ssi.renametojar" files which obviously won't get loaded w/o intervention, and if your like me theses were your missing classes when web.xml doesn't have those blocks commented out. Jason -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED]] Sent: Friday, January 18, 2002 3:51 AM To: Robertson, Jason; 'Cactus Developers List' Subject: RE: Problem with Tomcat 4.0 authentication Jason, I have tried yesterday night to use the -Dcatalina.base parameter but my config is still wrong and I'm not sure why. Here is what I have : <java classname="org.apache.catalina.startup.Bootstrap" fork="yes"> <jvmarg value="-Dcatalina.home=${tomcat.home.40}"/> <jvmarg value="-Dcatalina.base=${out.tomcat40.full.dir}"/> <arg value="start"/> <classpath> <!-- This is to allow the use of -Dbuild.sysclasspath=only when starting Ant - Meaning that all jars need to be on the initial classpath --> <pathelement path="${java.class.path}"/> <!-- These are ignore if -Dbuild.sysclasspath=only is used --> <fileset dir="${tomcat.home.40}"> <include name="bin/bootstrap.jar"/> <!--include name="server/catalina.jar"/--> </fileset> </classpath> </java> And server.xml : <Server port="8005" shutdown="SHUTDOWN" debug="0"> <Service name="Tomcat-Standalone"> <Connector className="org.apache.catalina.connector.http.HttpConnector" port="@test.port@" minProcessors="5" maxProcessors="75" acceptCount="10" debug="0"/> <Engine name="Standalone" defaultHost="localhost" debug="0"> <Realm className="org.apache.catalina.realm.MemoryRealm" /> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true"> </Host> </Engine> </Service> </Server> I'm getting a "[java] [java] StandardHost[localhost]: MAPPING configuration error for request URI". It seems this could related to not having a ROOT webapp but I'm not sure and when I create one it is the same. Then there are stack traces saying it cannot find some java classes. This happens for the classes defined in conf/web.xml (invoker servlet, ssi servlet, etc). However, I'd like to keep the web.xml file the same (and even if I remove these servlet definitions, it fails but this times tomcat simply blocks). Any idea ? Have you succeeded on your side ? Thanks -Vincent > -----Original Message----- > From: Robertson, Jason [mailto:[EMAIL PROTECTED]] > Sent: 17 January 2002 20:46 > To: 'Cactus Developers List'; 'Vincent Massol' > Subject: RE: Problem with Tomcat 4.0 authentication > > Ok, the problem is that Tomcat isn't using the tomcat-users.xml file in > the > cactus-specified conf directory, but the one in the %TOMCAT_HOME%/conf > directory. Add the testuser/testpwd entry to that file and things work. > > If I have a chance I'll dig into Tomcat code and see what's up. Looks like > a > Tomcat bug to me. > > Jason > > -----Original Message----- > From: Robertson, Jason > Sent: Thursday, January 17, 2002 2:55 PM > To: 'Vincent Massol'; 'Cactus Developers List' > Subject: RE: Problem with Tomcat 4.0 authentication > > > Ignore previous response. I should completely read and then think and then > email. > > I'm currently running tomcat outside of the cactus tests, and I can > request > the ServletRedirector in IE and it prompts me properly and when I enter > testuser/testpwd I get the good old 'Missing service name parameter' so > I'm > getting as far as I can manually and it seems that Tomcat is working. > > Interestingly, however, from the release notes of Tomcat 4-0-1, under the > "using with Apache" section: > > * With this release, FORM-based authentication will work correctly, but > there is a bug that prevents BASIC authentication from operating. This > will be addressed before final release. > > I also found a handful of mentions in the archives about basic > authentication not working, such as: > > http://www.apachelabs.org/tomcat- > user/200109.mbox/%3C20010914101338.E38404-1 > 00000@localhost%3E > > But I don't know if this applies to using the built in web server or just > the Apache Web Connector. > > Jason > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 16, 2002 6:16 PM > To: 'Cactus Developers List' > Cc: Robertson, Jason > Subject: Problem with Tomcat 4.0 authentication > > > Jason, > > For some reasons, I cannot configure properly Tomcat 4.0 to run with our > basic authentication. It works fine with Tomcat 3.3. I am sure I have a > bad setting somewhere but I can't find where. > > You can find the summary of what I set up either in CVS or in the email > I sent to the Tomcat 4 mailing list (but I got no response ... :-( ), > available at : > http://www.mail-archive.com/tomcat-user%40jakarta.apache.org/msg42173.ht > ml > > The result of the build is : > http://www.mail-archive.com/cactus-dev%40jakarta.apache.org/msg00286.htm > l > > Any idea ? > Thanks > -Vincent > > > > -- > To unsubscribe, e-mail: <mailto:cactus-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:cactus-dev- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
