I did add the repository and when i used the GUI for PPM i verified that the repository was added but when i search for the perl module it still shows version 0.55 for SOAP::Lite and for SOAP::WSDL it shows 1.23 i went further to check the website manually and verified that it does have the latest packages.It seems quite unlikely that PPM would pick up the latest version of SOAP::WSDL from trouchelle.com but not SOAP::Lite. Are you sure you weren't just looking at the installed version number of SOAP::Lite?
I tried to manually install the packages but it gives the following errors:Firstly, it's not a good idea to fight the package management system ;) If you don't know why it won't let you install something, you're not equipped to forcefully install it.
C:\SoapTest>ppm install http://trouchelle.com/ppm/SOAP-Lite.ppd ppm install failed: Can't find any package that provide Crypt-SSLeay f +or SOAP-Li te
Looking at build status for 'C' packages on trouchelle.com, it's apparent that they don't have a building version of Crypt::SSLeay, which is a dependency of SOAP::Lite. ActiveState also don't seem to have it, so you'll need another repository:
ppm rep add UofWinnipeg http://theoryx5.uwinnipeg.ca/ppms
Once done, have the GUI install Crypt-SSLeay, and then try again to install SOAP-Lite through the GUI. Don't worry to much about mixing and matching packages from different repos... just make sure they're for Perl 5.8 (not 5.6).
I verified that trouchelle.com does host the SOAP-WSDL ppd file (and zip file) exactly where it advertises... that error message looks weird, perhaps related to connectivity? Definitely try again after you get the newer version of SOAP::Lite.C:\SoapTest>ppm install http://trouchelle.com/ppm/SOAP-WSDL.ppd ppm install failed: No PPD found at http://trouchelle.com/ppm/SOAP-WSD +L.ppd
Secondly, using the older packages that i was able to get from before i am getting another error. Initially it complained about using the <import> tag for XML Schema definition, which was a problem i knew as SOAP::WSDL doesnt support XML Schema definition imports. ... I am thinking maybe it has to do with my App.config file and the settings i use there. Would you be able to guide me on this?Ok, now we're entering territory I'm not totally read-up on ;) Are you definitely feeding SOAP::WSDL a file/url that contains only a valid WSDL description of your webservice? If so, I imagine the problem is that SOAP::WSDL can't handle some of the WCF-generated WSDL constructs. I've found a few links for you to read:
A google search for '+WCF +WSDL' finds many more.
(Update: I think that second link describes exactly what's going on and what you need to do to fix it.)
Lastly, can you suggest a tool that i can use to A) view the expected SOAP request that my WCF web service expects, B) the actual request sent from my perl script and the C) response sent from the web service.For A), I've no idea. Usually, I find that manually reading the WSDL is enough to figure out what I'm doing wrong. It's mainly up to the remote webservice as to how strictly it complies with the WSDL specification it publishes.
For B) & C), just turn on the 'trace' option in SOAP::Lite.
Unfortunately, SOAP interoperability is known industry-wide to be a joke. Developers fight these battles all the time. Doing google search for 'SOAP interoperability' is enlightening.
-David
In reply to Re^5: SOAP::WSDL Installation
by erroneousBollock
in thread SOAP::WSDL Installation
by Khurrum
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |