It probably works on the other machine because the invoker servlet is turned on.
http://jakarta.apache.org/tomcat/faq/misc.html#invoker

-Tim

dontrango wrote:

Hi Tim,

How does it explain that it works on one machine but not on the others?

Both use the same config and no servlet mapping in both cases.

In any case, do you refer to URI mapping in this?

On Sat, 2004-01-24 at 23:19, Tim Funk wrote:

You declared the servlet but did not map it. I suggest a good servlet book or consulting Sun's web services develpoment tutorial.

-Tim

Bill Trump wrote:


Hi,

I have the error message below whenever I'm calling my servlet:

I run "http://localhost:8080/myApp/servlet/TestingServlet2";

I get :

HTTP Status 404 - /myApp/servlet/TestingServlet2

type Status report

message /myApp/servlet/TestingServlet2

description The requested resource (/myApp/servlet/TestingServlet2) is
not available.
Apache Tomcat/5.0.16

---

I read the thread "RE: Tomcat4.1.29 Requested resource not available" on
this mailing list, I managed to get the same result suggested by BAO
RuiXian on the last thread. So I still don't get the solution.


My settings: ------------

JAVA_HOME=/usr/local/opt/j2sdk1.4.2_01/
"CLASSPATH=/usr/local/opt/tomcat/common/lib/servlet-api.jar:."


Using CATALINA_BASE: /usr/local/opt/tomcat Using CATALINA_HOME: /usr/local/opt/tomcat Using CATALINA_TMPDIR: /usr/local/opt/tomcat/temp Using JAVA_HOME: /usr/local/opt/j2sdk1.4.2_01/

My server.xml
-------------

<Host name="localhost" debug="4" appBase="webapps"
      unpackWARs="true" autoDeploy="true"
      xmlValidation="false" xmlNamespaceAware="false">
       <Logger className="org.apache.catalina.logger.FileLogger"
                directory="logs"  prefix="mandala_log." suffix=".txt"
           timestamp="false"/>
       <Logger className="org.apache.catalina.logger.SystemOutLogger"
                directory="logs" prefix="mandala_sysout_log."
suffix=".txt"
                timestamp="false"/>
       <Logger className="org.apache.catalina.logger.SystemErrLogger"
                directory="logs" prefix="mandala_syserr_log."
suffix=".txt"
                timestamp="false"/>

       <!-- Turn on servlet reloading -->
       <DefaultContext reloadable="true" debug="4"/>

       <!-- Tomcat Root Context -->
       <Context path="/myApp" docBase="myApp" reloadable="true"
debug="4"/>
     </Host>

My web.xml
----------
<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
   PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
   "http://java.sun.com/dtd/web-app_2_3.dtd";>

<web-app>
 <servlet>
   <servlet-name>TestingServlet2</servlet-name>
   <servlet-class>TestingServlet2</servlet-class>
 </servlet>
</web-app>

What I've done:
---------------

I have an instance of tomcat4.1.27 running on another machine (say
hostA) and this tomcat5.0.16 runs on (host B).

1. I compiled 'TestingServlet2' on hostB, brought it to hostA to the
same directory ( I have the same directory structure, *.xml files on
both hosts ) I managed to get the wanted output on host A but not on
host B.

2. I compiled 'TestingServlet2' on host B in
CATALINA_HOME/webapps/myApp/WEB-INF/classes, brought the .java file to
CATALINA_HOME/webapps/jsp-examples/WEB-INF/classes and compiled it
there.

the I revert to the original server.xml:

<Context path="" docBase="ROOT" reloadable="true" debug="4"/>
       <!--
       <Context path="/myApp" docBase="myApp" reloadable="true"
debug="4"/>
       -->


then I run http://localhost:8080/jsp-examples/servlet/TestingServlet2.


I still get the 'HTTP 404' error message. I managed to see the other
examples without any problem.

3. when I run http://localhost:8080/myApp/, I'm able to see the
directory listing there.

It seems that only catalina can't see the servlets I placed in the
WEB-INF/classes directory.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to