Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of rashmi.sub@gmail.com
 designates 66.249.82.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=owIQZLC1DuUicLf0JU+gLI95r/Vhue2rOnS1wGWfdBVIT8Fckzb1MrU+YJtbiAyoOoRwL2m7av8geTcH5ORqV5E7fT7vsPSguSyhAQjpmfqu/0101xh6IqKOWSstDFoZr1Rxm+nEPpfhWyvVpm9VEJe8kSRd5d7lnRiDSfWRnU8=
Message-ID: <3ef28230704190703hfcb5e32i8f10108c0f6528c4@mail.gmail.com>
Date: Thu, 19 Apr 2007 10:03:52 -0400
From: "Rashmi Rubdi" <rashmi.sub@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Getting a project deployed
In-Reply-To: <933844870704190648u94d16c6q1776ff7fd03fe34c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <933844870704171529m1aa5f01em354297c745c0e620@mail.gmail.com>
	 <3ef28230704172111s5692dde3v5be2cfef11ec6ebb@mail.gmail.com>
	 <933844870704172204t7fb642b4le7683b2770748da1@mail.gmail.com>
	 <3ef28230704172238v2591c3b6t9fed947ce3b51798@mail.gmail.com>
	 <933844870704181418r4d198af2i6f4c7dba69f57e6e@mail.gmail.com>
	 <3ef28230704181427w73b127besf16ea7adfcba4af0@mail.gmail.com>
	 <933844870704181441k44b75cfekbfe464c7b0419b39@mail.gmail.com>
	 <3ef28230704181604i455a88ebr255ce17ac3479f14@mail.gmail.com>
	 <933844870704190648u94d16c6q1776ff7fd03fe34c@mail.gmail.com>

Ok, if you insist on having an Apache Httpd (even though you may or
may not need it), someone on this list might help you further
configure it.

But I just wanted to say a few things... my reply is below...

On 4/19/07, John Calsbeek <nexuapex@gmail.com> wrote:
> Yeah, this isn't my webserver. I'm not excited about pulling out an
> existing Apache setup...
>
> On 4/18/07, Rashmi Rubdi <rashmi.sub@gmail.com> wrote:
> > It is most likely that the project is not configured properly. We can
> > fix the 404 error by properly configuring your project for Tomcat
> > alone.
> >
> > For starters, what is the absolute path of this index.jsp from the
> > root folder of the Linux machine?
>
> /srv/www/tomcat5/base/webapps/jmarks/index.jsp

Normally in Tomcat a JSP page with the above absolute path is accessible at
http://localhost:8080/jmarks/index.jsp , where jmarks is known as the conte=
xt

As Hassan mentioned earlier you would be able to change the port to 80
, the port configuration is in server.xml , look for where it says
8080 (only in case you want to change it in Tomcat and not through
Apache).

>
> /srv/www/tomcat5/base/webapps/jmarks is aliased with Apache to the
> HTTP path /path/to/jmarks

The above aliasing of paths also works in Tomcat alone with the use of
Filters. The aliasing is commonly known as URL Rewriting - normally
people write their own Filters or download and install a pre-written
one - Google will help here.

>
> When I had this folder directly in /srv/www/htdocs/path/to/jmarks, I
> had the same problem=97*.html works fine, *.jsp does not.

Check the configuration of the above aliasing. Normally URL Rewriting
is done in a sequence, the first matching path pattern is applied, so
it helps to check all patterns and see which is the first one that's
being applied.

-Rashmi

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org