-
It seems that upgrading Perl and the rest of the modules revealed a bug in my test program. My apologies.
2009-11-06 15:07:35 UTC by tpc1095
-
Did SOAP::Lite version 0.710.08 regress?
I have a small SOAP::Lite client I've been running for about a week, and in the process of trying to get attachments working, I upgraded to SOAP:Lite 0.710.08 and Perl 5.10.1 (ActiveState ppm, Windows XP) . Now my program has stopped working and I get a bunch of errors in the console. I have tried several variations of ppms for SOAP::Lite. I am...
2009-11-06 14:24:34 UTC by tpc1095
-
XMLRPC::Lite does not maintain data type for datetime.
Ie something like:
my $date = $server->call('getDate');
$server->call('sendDate', $date);
Fails because $date gets converted from datetime type to string type.
Frontier::Client is an example of a module without this bug. It's implementation choice was to return dates as objects rather than base perl types.
2009-10-23 20:55:24 UTC by vmpdemo
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-10-14 02:21:31 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-10-14 02:21:31 UTC by sf-robot
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-10-14 02:21:30 UTC by sf-robot
-
I faced this issue initially in my LOCAL PC and when I installled Crypt::SSleay in my machine it worked fine. But even though in the server this module is installed the error is still there. My guess are
1) due to some perl version
2) any missing modules which is causing this issue or the version of any modules.
3) Some setting is missing in IIS.
2009-10-12 16:20:41 UTC by anishkpillai
-
Hi
I have a SOAP call over the CGI and I get an error like
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.
I tried the same script by running from the command prompt I see that the script works fine. I made sure that Crypt::SSleay module is installed as well. Did any one face similair kind of issue. I am not able to get any much...
2009-10-12 15:44:41 UTC by nobody
-
kutterma committed revision 341 to the SOAP::Lite SVN repository, changing 23 files.
2009-09-30 18:34:58 UTC by kutterma
-
I am unable to comment on my bug report because you close it, so i open a new one.
The problem is that utf8 string are serialized as base64 binary data - so
the deserialize data never sets the uft8 flag.
One solution is to provide a separtate serializer for utf8 strings,
something like:
$self->{_typelookup}->{'utf8string'} =
[5, sub { Encode::is_utf8($_[0]) }, 'as_utf8string']...
2009-09-30 06:42:37 UTC by dietmarmaurer
