Skip Menu |

This queue is for tickets about the SOAP-Lite CPAN distribution.

Report information
The Basics
Id: 37360
Status: resolved
Priority: 0/
Queue: SOAP-Lite

People
Owner: Nobody in particular
Requestors: toddr [...] cpanel.net
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 0.71
Fixed in: (no value)



Subject: Use of uninitialized variables in SOAP tests
Hi, I'm getting the following errors on Strawberry perl testing for 5.10.0. Here's the output: t/SOAP/Serializer............................1/12 Use of uninitialized value $values[0] in join or string at C:\Projects\perl-soap- lite\branches\0.71\blib\lib/SOAP/Lite.pm line 1376. Use of uninitialized value $values[0] in join or string at C:\Projects\perl-soap-lite\branches\0.71\blib\lib/SOAP/Lite.pm line 1376. Use of uninitialized value $values[0] in join or string at C:\Projects\perl-soap-lite\branches\0.71\blib\lib/SOAP/Lite.pm line 1376. Use of uninitialized value $values[0] in join or string at C:\Projects\perl-soap-lite\branches\0.71\blib\lib/SOAP/Lite.pm line 1376. t/SOAP/Serializer............................ok t/SOAP/Transport/FTP.........................1/7 Use of uninitialized value in split at C:\Projects\perl-soap-lite\branches\0.71 \blib\lib/SOAP/Transport/FTP.pm line 55. substr outside of string at C:\Projects\perl-soap-lite\branches\0.71 \blib\lib/SOAP/Transport/FTP.pm line 56. Use of uninitialized value $_[1] in join or string at C:/STRAWB~1/perl/lib/IO/Socket/INET.pm line 117. Use of uninitialized value $server in concatenation (.) or string at C:\Projects\perl-soap-lite\branches\0.71\blib\lib/SOAP/Transport/FTP.pm line 60. t/SOAP/Transport/FTP.........................ok t/SOAP/Transport/HTTP........................1/? Use of uninitialized value $endpoint in exists at C:\Projects\perl-soap-lite\branches\0.71 \blib\lib/SOAP/Transport/HTTP.pm line 157. Use of uninitialized value $endpoint in exists at C:\Projects\perl-soap- lite\branches\0.71\blib\lib/SOAP/Transport/HTTP.pm line 167. Use of uninitialized value $endpoint in exists at C:\Projects\perl-soap- lite\branches\0.71\blib\lib/SOAP/Transport/HTTP.pm line 169. Use of uninitialized value $_[0] in length at C:\Projects\perl-soap- lite\branches\0.71\blib\lib/SOAP/Lite.pm line 408. Use of uninitialized value $envelope in length at C:\Projects\perl-soap- lite\branches\0.71\blib\lib/SOAP/Transport/HTTP.pm line 186. Use of uninitialized value $content in length at C:/STRAWB~1/perl/site/lib/HTTP/Message.pm line 313. Use of uninitialized value $content in join or string at C:/STRAWB~1/perl/site/lib/HTTP/Message.pm line 313. Called UNIVERSAL::can() as a function, not a method at C:\Projects\perl- soap-lite\branches\0.71\blib\lib/SOAP/ Transport/HTTP.pm line 556
From: todd.e.rinaldo [...] jpmorgan.com
Hi, with the recent branch fix to 0.71, I no longer get errors: C:\Projects\perl-soap-lite\branches\0.71>prove -b -v t\SOAP\Serializer.t t\SOAP\Serializer.... 1..12 ok 1 - use SOAP::Lite; ok 2 ok 3 - serialize <fooxml/> ok 4 - serialize <_xml/> ok 5 - error on <xml:lang/> ok 6 - error on <xmlfoo/> ok 7 - fault escaped OK ok 8 - fault escaped OK ok 9 - response escaped OK ok 10 - response escaped OK ok 11 - response escaped OK ok 12 - response escaped OK ok All tests successful. Files=1, Tests=12, 0 wallclock secs ( 0.03 usr + 0.02 sys = 0.05 CPU) Result: PASS
From: todd.e.rinaldo [...] jpmorgan.com
Hi, I just realized that these errors continue to be present in harness. Prove is not generating errors, but Test::Harness is. Any ideas why this discrepancy would be the case?
From: todd.e.rinaldo [...] jpmorgan.com
I'm going to answer my own question here: I think the reason is that prove is not turning on warnings, whereas harness is. On Mon Jul 07 11:11:59 2008, todd_rinaldo wrote: Show quoted text
> Hi, I just realized that these errors continue to be present in > harness. Prove is not generating errors, but Test::Harness is. Any > ideas why this discrepancy would be the case?
Fixed in SVN. Thanks, Martin
oops, sorry, not fixed yet - got the wrong form... Sorry for any inconvenience, Martin
After some tries, finally sorted out where the warnings came from with the help of Acme::JavaTrace. Never thought a Acme:: module would come in this handy... Fixed in SVN in rev395
Fixed in 0.715 just uploaded to CPAN