The specific problem I am having with IIS and Tomcat is... I'm trying to run a Statistics Program I wrote in java. It seems there is a problem that if I specify a default file ie http://www.mywebsite.com/index.jsp in IIS while pointing to the home directory of tomcat\webapps\mywebsite\index.jsp
THE CATCH IS ... I cant use any type of redirector because I am trying to get the REFERER URL from the default file index.jsp . Otherwise I could just use a meta tag to redirect to the jsp file.
If I use http://www.mywebsite.com/mywebsite/index.jsp the JSP functionality works.
If I use http://www.mywebsite.com - with a top file set as index.jsp and the home directory of /mywebsites in IIS the JSP functionality is gone.
EVEN THOUGH THEY ARE BOTH POINTING TO THE SAME PLACE ???? I've been TOLD it can't be done and to use tomcat and apache.
You don't need to use Tomcat and Apache. The easiest way I know of to do this is to create an index.html file as your default IIS file. Add a small snippet of ASP to that file that reads the referrer URL and redirects to your webapp's main page with this URL as a parameter (or sets a cookie, or submits a form, or whatever).
BTW, this will also work for Apache if it's running the asp support mod.
I don't understand if they are both pointing to the same place why jsp does not work ?
It doesn't work because the IIS redirector (that works with Tomcat) doesn't know how to map http://www.mywebsite.com/index.jsp to http://www.mywebsite.com/mywebsite/index.jsp. You've told IIS about it, but the Tomcat redirector doesn't know anything about this.
You may also be able to get the same functionality if you setup your webapp as the ROOT webapp, but I'm not 100% sure about that. It depends on how IIS generates the URL and when IISRedirect gets its hands on it. This suggestion carries no warranty, implied or otherwise. ;)
justin
-wiley
This issue of Tomcat and Apache comes up over and over and over again on
the list here because everyone tells everyone else that they should run Apache in front of Tomcat without understanding what the person is doing. There are definitely reasons for this (which have been discussed
more than many times), but I have *never* seen anyone give _conclusive_ *performance-centric* proof for this.
I agree -- conceptually it gives you performance boost after some activity threshold, but I surmise that the *large majority* of people out there aren't even close to this threshold. It seems to me that it's more of a
"common knowledge" thing than anything. The more often something is repeated, the more likely it will become defacto truth.
In fact, our app supports connections both through a proxy (IIS or Apache) *and* directly to Tomcat because response times are very important to us
and the turnaround going through Apache is ~100ms while the turnaround directly to Tomcat is ~20ms. Tomcat is an excellent HTTP server. It easily supports the requirements of most projects out there. IMHO, using Tomcat as Http server should be the default and Apache should only be used if you have a specific reason to use it (of which there are many very real, very valid ones, some of which Jeffrey Peloquin, amongst others, have mentioned in this thread).
My point in writing this is that we should all be careful what we suggest before understanding what exactly the person needs. And, quite frankly,
those asking should find these threads *easily* with a little effort. ;)
justin
____________________________________ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential See http://www.nextengine.com/confidentiality.php ____________________________________
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
