You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Stuart Morse <st...@excelsystems.com> on 2003/04/07 20:20:43 UTC

ROOT Web Application difficulties

Hi All,

I just upgraded from Tomcat 3.2 to 4.1.24. Under 3.2 I could just drop a
class file in the ROOT web application's "classes" directory, and it was
immediately accessible without further configuration. This does not seem to
be the case under 4.1.24.

Can someone please verify that I am correct in the assumption above? Do I
really have to manually edit the web.xml file for the ROOT application for
every servlet that I want to deploy to the that webapp?

Regards,

Stuart Morse



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: ROOT Web Application difficulties

Posted by John Turner <to...@johnturner.com>.

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/appdev/index.html

John

On Wed, 9 Apr 2003 15:23:16 -0700, Stuart Morse <st...@excelsystems.com> 
wrote:

> Hi John,
>
> Could you please direct me to the Application Developer's Guide?
>
> Regards,
>
> Stuart
>
> -----Original Message-----
> From: John Turner [mailto:tomcat-user@johnturner.com]
> Sent: April 9, 2003 1:33 PM
> To: Tomcat Users List
> Subject: Re: ROOT Web Application difficulties
>
>
>
> There's also this:
>
> <filter-mapping>
> <filter-name>Path Mapped Filter</filter-name>
> 	<url-pattern>/servlet/*</url-pattern>
> </filter-mapping>
>
> Do you have the right directory structure?  Are your servlets in the
> correct location?  Have you consulted the Application Developer's Guide?  
> I
> don't use the Invoker, so I'm probably not the best person to help.
>
> John
>
>
> On Wed, 9 Apr 2003 13:00:42 -0700, Stuart Morse <st...@excelsystems.com>
> wrote:
>
>> Hi,
>>
>> I checked out the /example web.xml file for any entries that mention
>> "invoker"
>> and found the following:
>>
>> <filter-mapping>
>> <filter-name>Servlet Mapped Filter</filter-name>
>> 	<servlet-name>invoker</servlet-name>
>> </filter-mapping>
>>
>> <servlet-mapping>
>> <servlet-name>invoker</servlet-name>
>> <url-pattern>/servlet/*</url-pattern>
>> </servlet-mapping>
>>
>> I've attached the whole web.xml file in case I've got something in the
>> wrong
>> order. I still can't access servlets in the ROOT web app. I own the
>> latest
>> edition of "Java Servlet Programming" by Jason Hunter, but "invoker" is
>> not
>> in the index and I can't find any info on it anywhere else. My ROOT
>> context
>> in the server.xml file looks like this:
>>
>> <Context path="/" docBase="ROOT" debug="0"/>
>>
>> The default had no slash in the path entry, but it doesn't work with or
>> without
>> the slash. What else do I need to do/fix?
>>
>> Regards,
>>
>> Stuart
>>
>> -----Original Message-----
>> From: John Turner [mailto:tomcat-user@johnturner.com]
>> Sent: April 7, 2003 11:24 AM
>> To: Tomcat Users List
>> Subject: Re: ROOT Web Application difficulties
>>
>>
>>
>> You are correct.
>>
>> The Invoker servlet is disabled by default in recent versions of 4.1.x
>> for
>> everything except the /examples webapp, for security reasons.  Running 
>> in
>> production with the Invoker servlet is possible but not recommended.  To
>> do
>> so, you will need to setup the Invoker servlet in your web.xml file (see
>> the /example web.xml file for guidance).
>>
>> John
>>
>> On Mon, 7 Apr 2003 11:20:43 -0700, Stuart Morse 
>> <st...@excelsystems.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> I just upgraded from Tomcat 3.2 to 4.1.24. Under 3.2 I could just drop 
>>> a
>>> class file in the ROOT web application's "classes" directory, and it 
>>> was
>>> immediately accessible without further configuration. This does not 
>>> seem
>>> to
>>> be the case under 4.1.24.
>>>
>>> Can someone please verify that I am correct in the assumption above? Do
>>> I
>>> really have to manually edit the web.xml file for the ROOT application
>>> for
>>> every servlet that I want to deploy to the that webapp?
>>>
>>> Regards,
>>>
>>> Stuart Morse
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>>
>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: Block Displaying Directory of JSP

Posted by Erik Price <ep...@ptc.com>.


Tim Funk wrote:

> I wanted to make sure anyone reading this thread did not start to add 
> their own servlet declarations and mappings to conf/web.xml instead of 
> WEB-INF/web.xml. While someone can add their mappings to conf/web.xml, 
> doing  so will eventually result in something kludgy that supporting 
> will be tricky because everyone else expects mapping to be declared in 
> WEB-INF/web.xml.

Thank you for posting this.


Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org