Hi,
I have a bit of a problem.
I have a COM+ object that I need to expose via SOAP as part of a
larger application. The COM+ object has previously been published via
the Microsoft SOAP toolkit v3 on Windows 2000 Server and Windows XP
Pro (the development machine).
This now needs to be deployed to a Windows 2003 Server machine, where
the SOAP toolkit is not supported, however I am having no end of
problems.
In order to determine the correct way of doing things, I tried to
configure my local XP Pro machine to serve the SOAP in the 2003
manner.
Firstly, I created a new COM+ Application, and imported my COM+ object
into it, then I checked the "Use SOAP" box following this article:
http://msdn.microsoft.com/library/de...asp?frame=true
This created a virtual directory just fine, however, the Default.aspx
file rendered the source code.
I then added the association between the .aspx file extension and the
aspnet_isapi.dll file and the page now correctly renders links to the
four interfaces the object exports:
http://localhost/soap/object.utilites.soap?WSDL
These links throw 404 errors
My directory looks like
C:\WINDOWS\SYSTEM32\Com\SOAPVRoots\soap\
\Default.aspx
\Default.disco
\Web.config
\bin
\objectsoaplib.dll
\comsvcslib.dll
Web.config appears to my .NET illiterate eye to point mappings to
things in a .NET fasion, and I'm guessing here, is being totaly
ignored.
How would I go about manualy fixing the virtual directory to correctly
serve a .NET powered application? Or is it something else that I'm
getting wrong?
has anyone else solved this?
TIA
Mike Jervis
