I assume you're attempting to implement an HTTPS+SOAP server rather than a client? You could use Apache2+mod_perl+mod_ssl in conjunction with SOAP::WSDL::Server::Mod_Perl2 to accomplish this.

--n

No, /WebService is the virtual URL created by mod_perl; browsing to that URL will trigger SOAP::WSDL::Server::Mod_Perl2's response handler.

SOAP::WSDL needs to be installed somewhere that mod_perl can find it; this means it needs to be in a path in the @INC that mod_perl uses. As a matter of general principle, I'd suggest not installing it in your DocumentRoot. Note that @INC can be modified; see http://perl.apache.org/docs/2.0/user/intro/start_fast.html#Configuration for a quick start on mod_perl. I'd suggest familiarizing yourself with mod_perl's basic operation a bit. The basics aren't too hard, and learning them will save you some headaches later. Coding under mod_perl is *almost* like writing a script, but you need to be a little careful since the perl interpreter doesn't exist between requests.

--n

Thank you for the explanation, especially the link was helpful, Noah!
I also want to thank Martin for his support and effort in writing SOAP::WSDL.
I have set now the include dir by using:

PerlRequire /XXX/example/startup.pl

I have one more question (possibly again with an easy answer):
How is it possible to get a valid response when browsing for my web service, from the browser?
I ask because since I moved to Mod_Perl2, I just get:

Length Required

A request of the requested method GET requires a valid Content-length.

instead of the default page showing the methods.

Thanks again,
Andreas

Yes, Thank you, Noah!

Maybe I try then to implement the browsing myself, like it is possible with Mono or IIS, although I am a Perl newbie.

Thanks again,
Andreas