Yeah, this isn't my webserver. I'm not excited about pulling out an
existing Apache setup...
On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] 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
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 [EMAIL PROTECTED] wrote:
Yeah, this isn't my webserver. I'm
On 4/19/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:
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.
The alias looks like
On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:
That's it, you can then start Tomcat with startup.sh and access it at
http://localhost:8080/ by default, and remember to shut it down with
shutdown.sh and not CtrlC
Then, to see a simple JSP application, create a new folder under
Tomcat's
I personally haven't worked with mod_jk , I'm sure there's someone on
this list who could help you with mod_jk config.
A lot of info is available in the docs also:
http://tomcat.apache.org/connectors-doc/index.html
But simply running JSPs doesn't require any connection with Apache Httpd.
On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:
I personally haven't worked with mod_jk , I'm sure there's someone on
this list who could help you with mod_jk config.
A lot of info is available in the docs also:
http://tomcat.apache.org/connectors-doc/index.html
But simply running JSPs
On 4/18/07, John Calsbeek [EMAIL PROTECTED] wrote:
Yeah, it's just nicer to have a port 80 connection…
So run Tomcat on port 80 -- is there any aspect of Apache httpd you
actually /require/? PHP, proxy to Mongrel, whatever?
If not, simplify your life and run Tomcat standalone :-)
FWIW,
--
On 4/18/07, John Calsbeek [EMAIL PROTECTED] wrote:
For anyone tuning in, my problem is this message displayed in the browser:
I just want to add that the following error message is not related to
mod_jk or Apache, this error commonly occurs on Tomcat alone if the
project is not configured
I'm trying to manually deploy a JSP website that I didn't make on a
web server that I didn't set up, so I'm kind of in strange territory
here (first time using Tomcat). Here's what I have/know:
Linux webserver using Apache 2 and Tomcat 5, mod_jk. Tomcat is
working—the default base URL of
On 4/17/07, John Calsbeek [EMAIL PROTECTED] wrote:
I'm trying to manually deploy a JSP website that I didn't make on a
web server that I didn't set up, so I'm kind of in strange territory
here (first time using Tomcat).
If I was in this situation, I would first try to run a webapp with a JSP
If I was in this situation, I would first try to run a webapp with a JSP on a
standalone Tomcat (independent of any IDEs) and without mod_jk.
The simple setup eliminates a lot of confusion :-)
I've never done this before. I haven't the first idea how to go about that. :)
It is very simple to set-up, you just need to install the most recent
compatible JDK (you probably have this already)
then get the tar.gz file for the version of your choice from here:
http://tomcat.apache.org/
Set the JAVA_HOME the environment variable, it point's to JDK
installation's root
12 matches
Mail list logo
