BorlandTalk.com

Guest

Hello,

I'm creating an ISAPI dll and I need to be able to debug the
application. I've tried hooking into iis and have had some success
with that but have also had problems with it. If I am forced to I may
go back to that set up.

Right now I'm trying to set up the Web Application Debugger and it
seems as though there are some major differences between the ISAPI and
the WAD. I started with blank project group and then created an ISAPI
project then the WAD executable project. I added the Webmodule from
the ISAPI to the WAD. I set up a default WebActionItem (mtAny) and an
associated event handler. In the event handler I return some text for
testing. Up to this point everything works fine.

But I noticed that when I call the dll from IIS the WebModule does not
get initialized but when I run the WAD it does. My test goes something
like this:

procedure TWebModule1.WebModule1WebActionItem1Action(Sender: TObject;
Request: TWebRequest; Response: TWebResponse; var Handled: Boolean);
begin
if (WebModule1 = nil) then begin
Response.Content := ' WebModule not available ';
Handled := true;
end else begin
Response.Content := ' WebModule is available ';
Handled := true;
end;
end;

Eventually, I need to have a global database connection pool and a
local XML document (one for each request). The XML document will be
part of the WebModule because as far as I know a new WebModule is
instantiated for each web request.

Am I on the right track here? Has anyone had much luck using the Web
Application Debugger?

Thanks in advance,
Neil