Re^6: Trouble getting started with SOAP (SOAP::Lite, SOAP::WSDL), translating from PHP to Perl

Thanks Tangent

Running "perl wsdl2perl.pl -b base_dir URL" on the wsdl file I'd saved worked fine, but trying it on the server, using the real URL, failed (with a server error - though it didn't specify what the error is).

I suspect that the second argument in the PHP call is the equivalent of a typemap (given the way it is constructed), and the page you pointed to says a few things about a possible need to provide a typemap, but not how to make it. Moreover, either it doesn't say, of I missed, how you provide the typemap in a call to function new when creating a new SOAP object. Can 'wsdl2perl.pl' be used to create the typemap from the wsdl file? If so, how? And then, when you have it, how do you use the typemap produced when you make a new SOAP instance?

Thanks

Comment on Re^6: Trouble getting started with SOAP (SOAP::Lite, SOAP::WSDL), translating from PHP to Perl

Replies are listed 'Best First'.
Re^7: Trouble getting started with SOAP (SOAP::Lite, SOAP::WSDL), translating from PHP to Perl by tangent (Parson) on Feb 21, 2012 at 17:37 UTC
It seems what you are trying to do is credit card payment authorization? Now, I'm wondering if you have tried the PHP code, and does it work? There may be other issues such as authentication or encryption. Can you show the Perl code you are using now - and maybe start a new comment because this thread is getting a bit narrow.	[reply]
Re^8: Trouble getting started with SOAP (SOAP::Lite, SOAP::WSDL), translating from PHP to Perl by Anonymous Monk on Feb 21, 2012 at 18:51 UTC
Actually, one of the things I'd said at the beginning was that the PHP code worked, and the issue I face is translating it into Perl. Further, the point of failure is before authentication can happen. The point of translating it into Perl was so that I could connect to the wsdl server using my own CGI code. I have 'integrations' into a bunch of different credit card processors' servers (so a merchant can simply connect to my cgi API, over SSL/TLS, with his account info including the rocessor ID, and submit his transactions. This way, the merchant need not worry about integrating into a bunch of different processors for their various accounts (many merchants have several accounts with different processors, and that can make managign these accounts in their CRM and shopping carts a nightmare; and my system greatly simplifies that). But all my networking software is written in perl.	[reply]
Re^9: Trouble getting started with SOAP (SOAP::Lite, SOAP::WSDL), translating from PHP to Perl by tangent (Parson) on Feb 21, 2012 at 20:44 UTC
Actually, one of the things I'd said at the beginning was that the PHP code worked, and the issue I face is translating it into Perl. Well, what you said was "The only working example I have for the SOAP sever I need to use is written in PHP". In my experience these services often provide examples written in various languages so my intention was to clarify. I don't know PHP so can't help you with translation. You said too that "SOAP itself looks to be simple enough" but if you have a look at SOAP::Simple it says: Let's face it. SOAP is painful. It's a dumb idea, the only reason you should ever consider using SOAP is if someone holds a gun to your head or pay you a lot of money for it. Maybe that module should be called SOAP::Simple? If you are familiar with XML a better approach may be to use XML::Compile::SOAP and it has lots of examples too. Without being able to see your Perl code and the details of how it fails the only other suggestion I have is to look through the many other nodes here on Perlmonks that mention SOAP and WSDL.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks