I thought I solved it...byt,,,. If you can run
http://www.saphea.com/echotest2.cfm
successfully, then I could have marked this as the answer except
for the troubling issue I ran into (below).
Before I detail my solution for any who may find this post, I
need to add one more tidbit that, in retrospect, may have been
important to mention sooner. My CF Mapping of "/" is pointing to
c:\inetpub\wwwroot, but all of my web sites are actually contained
in a directory on another drive.
So, here's how I have almost resolved this on my CF7 server.
I need to go try it on the CF8 server yet.
1. Created directory "C:\Inetpub\wwwroot\cfwebservices". This
is where the CFC is placed.
2. In CF Admin, I mapped "/cfwebservices" to
"C:\inetpub\wwwroot\cfwebservices" (same directory as step #1).
3. Used the default web site name as the access to the cfc.
And that is the echotest2.cfm that you see above.
However, I then added the subdomain of
"webservices.saphea.com" to the Default web server so that I wasn't
releasing my internal server name when I published the services.
Trouble rose again!
http://www.saphea.com/echotest3.cfm
does not work. I can go to the ?wsdl file and view it, and it looks
just like the one I can see that echotest2 accesses, but for some
reason it doesn't want to work with the webservices subdomain. Did
I misspell something here? I don't think so!
Back to the drawing board.
RLS