ISAPI applications are called only on demand, if a request explicitly points
to the DLL. Hence, in the most common case - of processing all normal
requests, the additional overhead of a filter will not be incurred.
ISAPI Filters provide call backs at each stage of the processing. Realize
that what is being installed is a filter, not an application and therefore
IIS doesn't "know" (or even need to know) how to start Tomcat.
The ISAPI filter simply forwards items to Tomcat for processing.
At least, this is what I am told...=P
Darrell
-----Original Message-----
From: Steve Holmlund [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 3:08 PM
To: [EMAIL PROTECTED]
Subject: Tomcat/IIS 5 /examples solution?
Ok, it was a trip to jGuru and a post by Eric M. from December that may have
provided the answer to my problem. Eric reiterated the isapi_redirect.dll
install procedure in 28 steps. Step #26 was to "start Tomcat".
I didn't think this was necessary as I thought that IIS "started Tomcat" by
having it installed as a filter. Then I re-read the tomcat-iis-howto and lo
and behold, after "Configuring the ISAPI Redirector" Step 9, there is the
following:
"That's all, you should now start Tomcat and ask IIS to serve you the
/examples context."
So I fire up the Jakarta NT Service on the server and test from another
machine.
With IIS running, this works:
http://192.168.1.2/examples/jsp/index.html (192.168.1.2 is server IP)
If I stop IIS, that URL no longer works and I must enter:
http://192.168.1.2:8080/examples/jsp/index.html
which I presume is the standalone Tomcat working???
Can someone confirm that this is correct? If you know and have the time, I
would appreciate understanding why you must both add the filter and start
Tomcat separately. I don't really understand the theory of operation.
Thanks!
Steve
