Servlet Mapping Problem -- ???

[Hunter Hillegas <hh...@jacobstern.com>]

I have a strange problem with Tomcat 3.2 that I can't figure out...

I have two servers, a development server and a production server. The
development server is working just fine. I have a servlet called
marketCustomerVendorController that is mapped to
/marketCustomerVendorController as seen here from web.xml:

    <servlet-mapping>
      <servlet-name>marketCustomerVendorController</servlet-name>
      <url-pattern>/marketCustomerVendorController</url-pattern>
    </servlet-mapping>

On the dev box, it works great.

Yesterday I tried to push the WAR (generated by Ant via ./build dist) out to
the production box.

When Tomcat had brought up the new Web app, the mapping doesn't work (404).
If I type in context/servlet/marketCustomerVendorController it does work
however. I double-checked the web.xml file in the
webapps/context_name/WEB-INF/ directory to make sure that it was correct and
it is.

tomcat-apache.conf is the same on both boxes...

I'm sure it's some config option somewhere but I went through it and I can't
find it. Both boxes seem to be setup the same way...

Any ideas?


Hunter Hillegas, MCP
Web Engineer / System Administrator - Jacob Stern & Sons, Inc.
hhillegas@jacobstern.com
805-565-1411 PH * 805-565-8684 FAX

Re: Servlet Mapping Problem -- ???

[Hunter Hillegas <hh...@jacobstern.com>]

Anyone have any more ideas on this one?

I still can't get it figured out and I'm getting desperate.
--
Hunter Hillegas, MCP
Web Engineer / System Administrator - Jacob Stern & Sons, Inc.
hhillegas@jacobstern.com
805-565-1411 PH € 805-565-1415 FAX

> From: "Craig R. McClanahan" <Cr...@eng.sun.com>
> Reply-To: tomcat-user@jakarta.apache.org
> Date: Fri, 9 Feb 2001 12:33:47 -0800
> To: tomcat-user@jakarta.apache.org
> Subject: Re: Servlet Mapping Problem -- ???
> 
> Hunter Hillegas wrote:
> 
>> I have a strange problem with Tomcat 3.2 that I can't figure out...
>> 
>> I have two servers, a development server and a production server. The
>> development server is working just fine. I have a servlet called
>> marketCustomerVendorController that is mapped to
>> /marketCustomerVendorController as seen here from web.xml:
>> 
>>     <servlet-mapping>
>>       <servlet-name>marketCustomerVendorController</servlet-name>
>>       <url-pattern>/marketCustomerVendorController</url-pattern>
>>     </servlet-mapping>
>> 
>> On the dev box, it works great.
>> 
>> Yesterday I tried to push the WAR (generated by Ant via ./build dist)
> out to
>> the production box.
>> 
> 
> Does your dev box run Tomcat standalone and your production box run
> Tomcat
> behind Apache?  If so, the most likely reason for this is that the
> Apache
> connector is totally ignorant of anything you define in web.xml --
> you'll have
> to modify the tomcat-apache.conf file to include any additional
> forwarding you
> want.
> 
> Craig McClanahan
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-user-help@jakarta.apache.org
> 

Re: Servlet Mapping Problem -- ???

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Hunter Hillegas wrote:

> I have a strange problem with Tomcat 3.2 that I can't figure out...
>
> I have two servers, a development server and a production server. The
> development server is working just fine. I have a servlet called
> marketCustomerVendorController that is mapped to
> /marketCustomerVendorController as seen here from web.xml:
>
>     <servlet-mapping>
>       <servlet-name>marketCustomerVendorController</servlet-name>
>       <url-pattern>/marketCustomerVendorController</url-pattern>
>     </servlet-mapping>
>
> On the dev box, it works great.
>
> Yesterday I tried to push the WAR (generated by Ant via ./build dist) out to
> the production box.
>

Does your dev box run Tomcat standalone and your production box run Tomcat
behind Apache?  If so, the most likely reason for this is that the Apache
connector is totally ignorant of anything you define in web.xml -- you'll have
to modify the tomcat-apache.conf file to include any additional forwarding you
want.

Craig McClanahan