Skip Menu |

This queue is for tickets about the POE-Component-Server-SOAP CPAN distribution.

Report information
The Basics
Id: 4439
Status: resolved
Priority: 0/
Queue: POE-Component-Server-SOAP

People
Owner: APOCAL [...] cpan.org
Requestors: kar [...] kakidata.dk
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.03
Fixed in: (no value)

Attachments


Subject: Parameter passing
I've attached an example because I would think that POE-Component-Server-SOAP should pass parameters as well as SOAP_lite. The SOAP::Lite example uses client.pl, fmserver.pl and DBIx.pm The POE Component example uses test-client.pl and test-server.pl The first problem is that passing a hash with keys like '!Table' will fail. The second problem is that all passed parameters are stored in a hash and not just passed by position. The key names are strange; something like c-gensym6, c-gensym8 or c-gensym14. Not easy to figure out which parameter is which This is POE-Component-Server-SOAP-0.03 Perl 5.8.1 w/ Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL_IMPLICIT_CONTEXT Locally applied patches: RC5 O/S is from SuSE 9.0, Linux 2.4.21.
Download example.tar.gz
application/x-tgz 1.2k

Message body not shown because it is not plain text.

Date: Thu, 20 Nov 2003 22:11:02 -0500
From: Rocco Caputo <rcaputo [...] pobox.com>
To: Guest via RT <bug-POE-Component-Server-SOAP [...] rt.cpan.org>
Subject: Re: [cpan #4439] Parameter passing
RT-Send-Cc:
These problems stem from the use of SOAP::Parser to parse SOAP requests. Apparently it isn't up to the task. Unfortunately, the much nicer SOAP::Parser that is included with SOAP::Lite is so badly intertwined with SOAP::Lite as to make it virtually useless by itself. It appears that SOAP::Parser may be extended through SOAP::TypeMapper, but it is marked "experimental" and its documentation is "Forthcoming..." My options seem to be: - Dig very deeply into SOAP::Parser, and make it work at any cost. - Write my own SOAP parser. I currently don't have the resources to do either. This task will remain open, and I will periodically revisit it to see if the situation changes. I welcome assistance on it from someone who's more familiar with SOAP and/or SOAP parser modules. -- Rocco Caputo - rcaputo@pobox.com - http://poe.perl.org/
I believe this is fixed by the latest release, let me know if the problem still persists... -- ~Apocalypse