Hi!

I am newbie to SOAP::Lite and hence the question.

I was able to generate the following response from my SOAP::Lite server :

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

   <soap:Body>
     <pollDeviceByIDResponse xmlns="urn:ENIRA_Soap">
       <xsd1:pollDeviceParamOut
         xmlns:xsd1="http://support.enira.com/ENIRA-SOAP.xsd"
         xsi:type="xsd1:pollDeviceParamOut">
     <integration_queue_id_seq
  xsi:type="xsd:int">249</integration_queue_id_seq>
<description xsi:type="xsd:string">...description...</description>
<result xsi:type="xsd:string">success</result> </xsd1:pollDeviceParamOut>
</pollDeviceByIDResponse></soap:Body></soap:Envelope>

Now I am not sure what is wrong with the above. However, JAX-WS is
expecting something like this :

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope
  xmlns:xsd1="http://support.enira.com/ENIRA-SOAP.xsd"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

   <soap:Body>
     <pollDeviceByIDResponse xmlns="urn:ENIRA_Soap">
       <xsd1:pollDeviceParamOut        xsi:type="xsd1:pollDeviceParamOut">
     <integration_queue_id_seq
  xsi:type="xsd:int">249</integration_queue_id_seq>
<description xsi:type="xsd:string">...description...</description>
<result xsi:type="xsd:string">success</result> </pollDeviceParamOut>
</pollDeviceByIDResponse></soap:Body></soap:Envelope>

So the question is how do I coax SOAP::Lite to emit "xmlns:xsd1=<uri>"
as part of the soap:Envelope attribute?

Any pointers in this regard is appreciated.

Not really sure about this but in your server try something like:

$SOAP::Constants::NS_SL_PERLTYPE =
"http://support.enira.com/ENIRA-SOAP.xsd";

On Tue, 2006-09-19 at 02:04, dhaval_shah_m wrote:
> Hi!
>
> I am newbie to SOAP::Lite and hence the question.
>
> I was able to generate the following response from my SOAP::Lite server :
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soap:Envelope
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
>
>   <soap:Body>
>     <pollDeviceByIDResponse xmlns="urn:ENIRA_Soap">
>       <xsd1:pollDeviceParamOut
>         xmlns:xsd1="http://support.enira.com/ENIRA-SOAP.xsd"
>         xsi:type="xsd1:pollDeviceParamOut">
>     <integration_queue_id_seq
>  xsi:type="xsd:int">249</integration_queue_id_seq>
> <description xsi:type="xsd:string">...description...</description>
> <result xsi:type="xsd:string">success</result> </xsd1:pollDeviceParamOut>
> </pollDeviceByIDResponse></soap:Body></soap:Envelope>
>
> Now I am not sure what is wrong with the above. However, JAX-WS is
> expecting something like this :
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soap:Envelope
>  xmlns:xsd1="http://support.enira.com/ENIRA-SOAP.xsd"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
>
>   <soap:Body>
>     <pollDeviceByIDResponse xmlns="urn:ENIRA_Soap">
>       <xsd1:pollDeviceParamOut        xsi:type="xsd1:pollDeviceParamOut">
>     <integration_queue_id_seq
>  xsi:type="xsd:int">249</integration_queue_id_seq>
> <description xsi:type="xsd:string">...description...</description>
> <result xsi:type="xsd:string">success</result> </pollDeviceParamOut>
> </pollDeviceByIDResponse></soap:Body></soap:Envelope>
>
> So the question is how do I coax SOAP::Lite to emit "xmlns:xsd1=<uri>"
> as part of the soap:Envelope attribute?
>
> Any pointers in this regard is appreciated.
>
>
>
>

The suggestion below worked. However my JAX-WS 2.0.1 client is unable
to parse it. Worse still it is failing to even throw a parse exception.

Thanks
Dhaval

--- In soaplite@yahoogroups.com, Eric Bridger <eric@...> wrote:
>
> Not really sure about this but in your server try something like:
>
> $SOAP::Constants::NS_SL_PERLTYPE =
> "http://support.enira.com/ENIRA-SOAP.xsd";
>
> On Tue, 2006-09-19 at 02:04, dhaval_shah_m wrote:
> > Hi!
> >
> > I am newbie to SOAP::Lite and hence the question.
> >
> > I was able to generate the following response from my SOAP::Lite
server :
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <soap:Envelope
> >  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> >  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> >  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> >  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> >
> >   <soap:Body>
> >     <pollDeviceByIDResponse xmlns="urn:ENIRA_Soap">
> >       <xsd1:pollDeviceParamOut
> >         xmlns:xsd1="http://support.enira.com/ENIRA-SOAP.xsd"
> >         xsi:type="xsd1:pollDeviceParamOut">
> >     <integration_queue_id_seq
> >  xsi:type="xsd:int">249</integration_queue_id_seq>
> > <description xsi:type="xsd:string">...description...</description>
> > <result xsi:type="xsd:string">success</result>
</xsd1:pollDeviceParamOut>
> > </pollDeviceByIDResponse></soap:Body></soap:Envelope>
> >
> > Now I am not sure what is wrong with the above. However, JAX-WS is
> > expecting something like this :
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <soap:Envelope
> >  xmlns:xsd1="http://support.enira.com/ENIRA-SOAP.xsd"
> >  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
> >  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> >  soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> >  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> >
> >   <soap:Body>
> >     <pollDeviceByIDResponse xmlns="urn:ENIRA_Soap">
> >       <xsd1:pollDeviceParamOut
xsi:type="xsd1:pollDeviceParamOut">
> >     <integration_queue_id_seq
> >  xsi:type="xsd:int">249</integration_queue_id_seq>
> > <description xsi:type="xsd:string">...description...</description>
> > <result xsi:type="xsd:string">success</result> </pollDeviceParamOut>
> > </pollDeviceByIDResponse></soap:Body></soap:Envelope>
> >
> > So the question is how do I coax SOAP::Lite to emit "xmlns:xsd1=<uri>"
> > as part of the soap:Envelope attribute?
> >
> > Any pointers in this regard is appreciated.
> >
> >
> >
> >
>

I have in the past written soaplite clients for Axis
1.2 services, and access then via wsdl:
$service =
SOAP::Lite->service(http://xxxx.yyyy.edu:9020/axis/services/GenesByLocationServi\
ce?wsdl");

axis2 is very different from axis1.x. What are the
issues/limitations/differences to be aware of when
trying soaplite clients on axis2 services?

Specifically I need to access a service implemented in
axis2 using the OMElement class for the input and
output (xml document). I guess I need access to the
wsdl, which in axis is not that simple to generate
from the code... Any ideas?

Thanks
Cristina

Hello,

     Objects I pass from client to the server using SOAP::Lite seem to
lose their blessings. They are received at the server as hashrefs or
arrayrefs depending on the underlying structure.

     Knowing the class of the expected object, I am reblessing them. Is
there a cleaner way of doing it or I am doing it all wrong.

Thank You,
Himanshu.

My SOAP::Lite service works perfectly using a SOAP::Lite client or
when I manually put the SOAP XML together from my C# client.  When I
try to use my WSDL file so that I can just make a web reference, it is
imported with no errors but the object does not have the method I have
defined.

When I use the validator at
http://www.mgateway.com/php/wsdlValidator/home.php I get the error
"Denied access to method (getDietInfo) in class (main) at
/usr/lib/perl5/site_perl/5.8.0/SOAP/Lite.pm line 2509."

Some searching suggests to me that the problem is something with my
namespace or soapaction, but I can't figure out what I might have
incorrect in the WSDL.

<a href="http://diet.bash-shell.net/diet.wsdl">Here is my wsdl</a>

The method takes 2 string inputs, both in the form of yyyy/mm/dd


One thing I am noticing, though.  My SOAP::Lite client is passing the
following SOAPAction header, SOAPAction:
"http://diet.bash-shell.net/diet#getDietInfo", yet if I specify that
full header with uri in the SOAPAction in my WSDL, SOAP::Lite returns
an error to the client stating that the SOAPAction header should not
have a uri, just "#getDietInfo"

Any ideas what is wrong?  Any WSDL gurus here that can tell me what is
wrong with my WSDL (that seems the most likely place of the problem).

Hi,

I recently encountered a problem using SOAP::Lite in PERL 5.6 and I'm
having trouble understanding exactly what caused this issue.  We're
using version 0.50 of SOAP::Lite (yes, old!).

I'm running a web service that returns Japanese characters.  Normally
when I read the characters into PERL from a database or file
everything works fine.  I then add the value to the SOAP response as
follows:

my $temp = SOAP::Data->name('MyString')
             ->type("string")
             ->value($str);

However, recently I made a modification where the string I am
inserting does not come from a database, but the characters are in the
code as literals:
my $literals = "\x{767a}\x{9001}";

I am then inserting into the response the same way as before.
However, the actual response from the service comes out garbled.  The
value assigned by literals shows up as expected, but all other values
pulled from other sources is unreadable.  If I do a pack("C*",
unpack("U*", $literals)), then everything else is readable but (of
course), the literal string is garbled.

I have this working properly in a PERL 5.8 environment with a newer
version of SOAP::Lite, but I'd like to understand what is going on
here.  Anyone have any ideas?

Thanks!!
--Steve

Is it possible to use gSOAP (http://www.cs.fsu.edu/~engelen/soap.html)
as a client with a SOAP::Lite (Apache, mod_perl, mod_soap) server?  If
so, are there any examples out on the web?

Hi

I've generated the WSDL stub for SugarCRM using stubmaker.pl. In most
cases the data types are simple, but there are a few complex types
that I'd like to edit by hand, but I'm not sure of the syntax. For
example, here is the "login" method

login => {
     endpoint => 'http://server/soap.php',
     soapaction => 'http://server/soap.php/login',
     namespace => 'http://www.sugarcrm.com/sugarcrm',
     parameters => [
       SOAP::Data->new(name => 'user_auth', type => 'tns:user_auth',
attr => {}),
       SOAP::Data->new(name => 'application_name', type =>
'xsd:string', attr => {}),
     ], # end parameters
   }, # end login

the user_auth complex type is defined as:

<xsd:complexType name="user_auth">
         <xsd:all>
                 <xsd:element name="user_name" type="xsd:string"/>
                 <xsd:element name="password" type="xsd:string"/>
                 <xsd:element name="version" type="xsd:string"/>
         </xsd:all>
</xsd:complexType>

My mangled attempt is:

login => {
     endpoint => 'http://server/soap.php',
     soapaction => 'http://server/soap.php/login',
     namespace => 'http://www.sugarcrm.com/sugarcrm',
     parameters => [
       SOAP::Data->new(name => 'user_auth', type => \SOAP::Data->value(
	 SOAP::Data->new(name => 'user_name', type => 'xsd:string', attr => {}),
	 SOAP::Data->new(name => 'password',  type => 'xsd:string', attr => {}),
	 SOAP::Data->new(name => 'version',  type => 'xsd:string', attr => {})
       ), attr => {}),
       SOAP::Data->new(name => 'application_name', type =>
'xsd:string', attr => {}),
     ], # end parameters
   }, # end login

but alas, it's all wrong. Any ideas are appreciated...

Thanks

Dan

-----Original Message-----
From: soaplite@yahoogroups.com [mailto:soaplite@yahoogroups.com] On Behalf Of dan.horne
Sent: Tuesday, September 26, 2006 9:48 PM
To: soaplite@yahoogroups.com
Subject: [soaplite] Editing stubmaker output

Hi

I've generated the WSDL stub for SugarCRM using stubmaker.pl. In most
cases the data types are simple, but there are a few complex types
that I'd like to edit by hand, but I'm not sure of the syntax. For
example, here is the "login" method

login => {
endpoint => 'http://server/soap.php',
soapaction => 'http://server/soap.php/login',
namespace => 'http://www.sugarcrm.com/sugarcrm',
parameters => [
SOAP::Data->new(name => 'user_auth', type => 'tns:user_auth',
attr => {}),
SOAP::Data->new(name => 'application_name', type =>
'xsd:string', attr => {}),
], # end parameters
}, # end login

the user_auth complex type is defined as:

<xsd:complexType name="user_auth">
<xsd:all>
<xsd:element name="user_name" type="xsd:string"/>
<xsd:element name="password" type="xsd:string"/>
<xsd:element name="version" type="xsd:string"/>
</xsd:all>
</xsd:complexType>

My mangled attempt is:

login => {
endpoint => 'http://server/soap.php',
soapaction => 'http://server/soap.php/login',
namespace => 'http://www.sugarcrm.com/sugarcrm',
parameters => [
SOAP::Data->new(name => 'user_auth', type => \SOAP::Data->value(
SOAP::Data->new(name => 'user_name', type => 'xsd:string', attr => {}),
SOAP::Data->new(name => 'password', type => 'xsd:string', attr => {}),
SOAP::Data->new(name => 'version', type => 'xsd:string', attr => {})
), attr => {}),
SOAP::Data->new(name => 'application_name', type =>
'xsd:string', attr => {}),
], # end parameters
}, # end login

but alas, it's all wrong. Any ideas are appreciated...

Thanks

Dan

I am trying to return some UTF-8 encoded data from a
SOAP::Transport::HTTP::CGI based server and I am getting the following
message in the SOAP fault:

"Wide character in subroutine entry at
/usr/lib/perl5/site_perl/5.8.3/SOAP/Lite.pm line 250."

The data I am returning is marked as UTF-8 from Perl's point of view
(i.e. the UTF-8 flag is on, as reported by Encode::is_utf8()) and the
problem seems to be related to serialization in some way. The server
itself is very simple:

SOAP::Transport::HTTP::CGI->dispatch_to('MDP::UserAPIDispatch')
                           ->handle;

but I'm baffled as to why I'm getting wide character problems here -
as far as I understood it, SOAP::Lite assumed by default that the data
returned by the server is UTF-8 and would handle it appropriately.

Does anyone know what I'm doing wrong here, and how I can fix it ?

Thanks.

Hi

I have tried or the various examples in the archive of this list but
haven't had any luck getting the client IP within a handler when using
SOAP::Transport::HTTP::Daemon.

I am using a static mapping using an external file.

I need to be able to retrieve the client IP as I need to use the IP
for authorisation and authentication (the messages are signed using a
shared secret and the IP address)

ANy pointers welcome

matt

SOAP Lite responses to some of my services fail the "WS-I 1.1 + SOAP
Binding Profile 1.0" tests.

Specifically R2113:
An ENVELOPE MUST NOT include the soapenc:arrayType attribute

It is seen in my response in arrays (like below.) Can I fix this
behavior to be compliant with this WS-I test?

Thank you
Mike



   <cpe soapenc:arrayType="namesp2:arrayCpes[5]"
xsi:type="namesp2:cpes">
             <arrayCpe xsi:type="namesp2:arrayCpes">
                <addressMacCpe
xsi:type="xsd:string">112233445567</addressMacCpe>
                <addressIpV4
xsi:type="xsd:string">24.237.59.254</addressIpV4>
             </arrayCpe>
             <arrayCpe xsi:type="namesp2:arrayCpes">
                <addressMacCpe
xsi:type="xsd:string">112233445568</addressMacCpe>
                <addressIpV4
xsi:type="xsd:string">24.237.59.252</addressIpV4>
             </arrayCpe>

Using SOAP-Lite versions 0.67 and 0.69 on Solaris and Linux platforms, I
consistently get this error using the Google API example from

http://search.cpan.org/src/BYRNE/SOAP-Lite-0.69/examples/google.pl

Use of uninitialized value in pattern match (m//) at
/home/fmccown/lib/perl5/site_perl/5.8.3/SOAP/Lite.pm line 427.
Use of uninitialized value in pattern match (m//) at
/home/fmccown/lib/perl5/site_perl/5.8.3/SOAP/Lite.pm line 427.

The error messages are caused by the line:

die $google->call->faultstring if $google->call->fault;

after calling $google->doGoogleSearch(...).  The code works perfectly
under SOAP-Lite version 0.60.

Any idea as to what is going on?

Thanks,
Frank

I forgot to include the complete error message in my previous post:

v 0.67:

Use of uninitialized value in pattern match (m//) at
/home/fmccown/lib/site_perl/5.8.0/SOAP/Lite.pm line 413.
Use of uninitialized value in pattern match (m//) at
/home/fmccown/lib/site_perl/5.8.0/SOAP/Lite.pm line 413.
0 >= 0 at ./test.pl line 13.

v. 0.69:

Use of uninitialized value in pattern match (m//) at
/home/fmccown/lib/perl5/site_perl/5.8.3/SOAP/Lite.pm line 427.
Use of uninitialized value in pattern match (m//) at
/home/fmccown/lib/perl5/site_perl/5.8.3/SOAP/Lite.pm line 427.
0 >= 0 at test.pl line 13.


For both versions, the error is on the same line of code:

sub splitqname { local($1,$2); $_[0] =~ /^(?:([^:]+):)?(.+)$/ ; return
($1,$2) }


Thanks,
Frank

Hello,

Is it possible to select the compression method ?

Thanks in advance.


_____________________________________________________________________
Mensaje analizado y protegido, tecnologia antivirus www.trendmicro.es

On Fri, 29 Sep 2006, JuanFco Rodriguez wrote:

> Hello,
>
> Is it possible to select the compression method ?
>
> Thanks in advance.


I ask this question because I've been struggling with an
interop problem between a SOAP::Lite server and a NuSOAP client.

The client sends "Accept-Encoding: deflate", but the SOAP::Lite
server uses the "compress()" zlib function to compress the content,
which is the right thing to do, as you can see in the following
FAQ (http://www.zlib.net/zlib_faq.html#faq39):

"gzip" is the gzip format, and "deflate" is the zlib format. They should
probably have
called the second one "zlib" instead to avoid confusion with the raw deflate
compressed
data format. While the HTTP 1.1 RFC 2616 correctly points to the zlib
specification in
RFC 1950 for the "deflate" transfer encoding, there have been reports of servers
and
browsers that incorrectly produce or expect raw deflate data per the deflate
specficiation
in RFC 1951, most notably Microsoft. So even though the "deflate" transfer
encoding
using the zlib format would be the more efficient approach (and in fact exactly
what the
zlib format was designed for), using the "gzip" transfer encoding is probably
more reliable
due to an unfortunate choice of name on the part of the HTTP 1.1 authors.

Im quite newbie to all these things about compression algorithms, but as far as
I
can understand it, "Accept-Encoding: deflate" should use "compress/uncompress"
functions.
The problem is that a lot of Microsoft implementations out there are using
"deflate/inflate" when
they see "Accept-Enconding: deflate". So to sum it up, "deflate" seems not to be
a
standard way of doing HTTP compression any more.  That's the reason I would like
to use "Accept-Encoding: gzip" with SOAP::Lite (at least on the server side, and
if
the client accepts both compression methods, to use "gzip" as default).

The NuSOAP client was using "gzdeflate" to uncompress the content sent by
SOAP::Lite,
after changing that function to "uncompress", everything went well.

do you agree with what I've said ? I might be wrong, so please correct me in
that case.

Thanks in advace.

_____________________________________________________________________
Mensaje analizado y protegido, tecnologia antivirus www.trendmicro.es

When I run the applications with the -w switch enabled, I get the following
warning:

	 Cannot marshall CODE reference at /usr/lib/perl5/site_perl/5.8.0/SOAP/Lite.pm
line 3404

I looked at the source, but couldn't make much out of it. Can someone tell me
what this is about?

Thank you.

--
Sherzod Ruzmetov

Hello,

I have the following Perl client (fragments):
use SOAP::Lite + trace => qw(debug);
my $client = SOAP::Lite
	 ->uri('http://localhost:8888/sc')
	 ->proxy('http://localhost:8888')
	 ->encoding('UTF-8')
	 ->readable(1);
my $response = $client->deleteUser( ... );

The server (server.pl):
...
my $daemon = SOAP::Transport::HTTP::Daemon->new(
	 LocalAddr => '127.0.0.1',
	 LocalPort => 8888,
	 Listen => 5,
	 Reuse => 1
);
$daemon->dispatch_to( ... );
$daemon->handle;

Package with functions (sc.pm):
...
sub deleteUser() {
  ...
}

Everytime the client is started the soap request is printed via "+
trace" and deleteUser is doing what is expected. But when it
terminates an automated response is sent to the client containg the
return value of the function.

How can i disable this response? (it should be a one-way communication)

Thank you,
Griesse

It's no cake walk, that's for sure. I've been fooling with it this
past week. Basically, as soon as a complex type is involved in a
method call, you're pretty much on your own to serialize the request
body properly. The best bet I've seen so far is to go lower level with
SOAP::Data::ComplexType, but I can't get it to work quite right, either.

Frank

--- In soaplite@yahoogroups.com, "Mike South" <msouth@...> wrote:
>
> Also, how about using a SOAP::Lite client to talk to a gSOAP server?
> Someone told me they tried this and it wouldn't work.
>
> I'd like to know if anyone has experience in that direction.
>
> mike

I have a program that uses SOAP::Lite. It works fine with version .60,
but has problems with versions .66 and newer.

This is the error I am recieving:

A service address has not been specified either by using
SOAP::Lite->proxy() or a service description)

Does anyone know what changes have occured in SOAP::Lite to make this
error occur?

Here are the sections of code that I think are relevant:
--------------------------------------------------------
use SOAP::Lite +autodispatch =>
service => 'https://ccuapi.akamai.com/ccuapi.wsdl';

# -------------------------------
# Get URLs from input file
# -------------------------------
open(FILE, $file) || die "Cannot open: $!\n";
my $cnt=0;
print "Reading URLs ...\n";
while (<FILE>) {
     chomp;
     print "$cnt: $_\n";
     my $u = SOAP::Data->type('string')->value($_);

--------------------------------------------------------

Thanks

I developed a client server application. Now I use a fixed endpoint to
the cgi, but I need to switch to a load balancer, in order to address
the call to the proper web server....is that possible with soap? Won't
the SOAP message be braoken by the load balancer?
Thanks anybody for the help!!!