Greetings,

I am using SOAP::Lite as client on linux and connecting to a Windows SOAP
server.

I was having trouble accessing data within a tag like this:

<attribute name="LastName" value="JONES" />

I cannot access the value "JONES" for a LastName".

I am able to access data between two tags like this:

<ticket>reallylongticketnumber</ticket>

using this code:

my $result = $soap->call($method => @params);
print $result->valueof('//VerifySessionResponse/iwsResponse/sessionInfo/
ticket');

I would greatly appreciate any help. My perl code and the server's xml
response are listed below.

Thanks,

Paul Yuergens

BEGIN PERL CODE

#!/usr/bin/perl

use SOAP::Lite ( +trace => all, maptype => {} );

my $soap = SOAP::Lite
   -> uri('http://authenticate.university.edu/iws')
   -> on_action( sub{ join '/', 'http://authenticate.university.edu/iws', $_[1]
})
   -> proxy('http://authenticate.university.edu/iws');

my $header = SOAP::Header->name(wsStudentCreds => {
   password => "xxxx",
   id => "dept.university.edu"
})->uri('http://authenticate.university.edu/iws/')->prefix('');
my @params = (
    $header,
    SOAP::Data->name(ticket => $ARGV[1]),
    SOAP::Data->name(userIpAddr => $ARGV[0]),
    SOAP::Data->name(returnExtendedAttributes => 1)
);

my $method = SOAP::Data->name('TrueCookie')
    ->attr({xmlns => 'http://authenticate.university.edu/ws/'});

my $result = $soap->call($method => @params);


if ($result->fault)
{
    print $result->faultstring;
}
else
{

    print $result->valueof('//VerifySessionResponse/iwsResponse/sessionInfo/
ticket');
}

BEGIN XML RESPONSE

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
	 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
	 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	 xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
	 <VerifySessionResponse xmlns="http://university.edu/ws/">
		 <iwsResponse action="Verify" hasErrors="false" transactionId="0">
			 <sessionInfo status="Active">
				 <userAttributes>
					 <attribute name="UID" value="1111111" />
					 <attribute name="LastName" value="JONES                      " />
					 <attribute name="FirstName" value="DAVEY                          " />
					 <attribute name="Email" value="JONES@...                           "
/>
					 <attribute name="MailCode" value="155555" />
				 </userAttributes>
				 <accounts>
					 <account loginId=" " type="ACF2" status="Unknown" />
					 <account loginId="djj" type="BobbyOnline" status="Authenticated" />
					 <account loginId=" " type="QDB" status="Unknown" />
					 <account loginId="" type="RACF" status="Unknown" />
					 <account loginId="1111111" type="UID" status="PasswordResetRequired"
/>
				 </accounts>
				 <ticket>reallylongticketnumber</ticket>
				 <univId> 1111111</univId>
			 </sessionInfo><errorInfo xsi:nil="true" />
		 </iwsResponse></VerifySessionResponse>
</soap:Body>
</soap:Envelope>

On 19 May 2003, Mark Wilkinson wrote:

> I think they should fix Perl to accomodate SOAP::Lite ;-)
>
> Does anyone know when the next Perl 5.8 release is due?  The autoload
> problem is a well known bug in the last release, so I am hoping it is
> dealt with in an upcoming patch.
>

5.8.1 is imminent for some definition of imminent. It all depends on
Jarkko.

You can download a snapshot of 5.8.1-tobe if this is important to you.
Note also that RedHat9 includes 5.8.0 + patches from 5.8.1 so might
already have the bug fixed in it.

--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj

Hi Alasdair,

--- Alasdair Allan <aa@...> wrote:
> You know, I think its anotehr case of having to "buy the book",
> thinking
> about it a bit more, I'm now fairly sure I came across this in
> "Programming
> Web Services with Perl" by Ray & Kulchenko, rather than the
> SOAP::Lite docs themselves.
It was included in the book after it was discovered by Pierre Denis
(as far as I remember) and discussed on this list ;):

http://groups.yahoo.com/group/soaplite/message/1794
http://groups.yahoo.com/group/soaplite/message/2136

> In fact, the lack of patches, bug fixes and new releases is
> something thats starting to seriously worry me.
Me too ;)

> There isn't any (workable) alternative to SOAP::Lite using Perl and
> its
> lacking alot of features (e.g. literal document encoding, proper
> MIME &
> DIME support, "proper" WSDL deployment support) by default, and I
> know
> people who are starting to have interoperability issues with AXIS
> (which
> I guess has to be taken as the reference implementation for SOAP
> these days).
>
> A year is a heck of a long time without a new distribution for
> something thats developing as fast as SOAP and web services.
Tell me about that; I used to release one version a week. It's
definitely not a lack of desire to change or improve things; it's
rather BDUF (big design up-front) paralysis: I would like to come up
with a solid architecture that would be able to handle
literal/document encoding, pluggable headers, different
de/serialization formats, have XML Schema support, work with sync and
async calls and MIME/DIME packaging specifications, perform well, be
configurable to handle large message, and tons of other things. Maybe
I just want to much.

Best wishes, Paul.

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

I think they should fix Perl to accomodate SOAP::Lite ;-)

Does anyone know when the next Perl 5.8 release is due?  The autoload
problem is a well known bug in the last release, so I am hoping it is
dealt with in an upcoming patch.

M

On Mon, 2003-05-19 at 11:07, ed-soaplite@... wrote: On Mon, May
19, 2003 at 05:56:18PM +0100, Alasdair Allan wrote:
> Right, hang on.... found it, its on page 129, near the bottom of the
page.

Damn, you're good. That footnote is highlighted in my copy now :)

> I'm currently trying to get SOAP::Lite to talk to OGSI servers (ie
Grid
> rather than Web Services) which is a whole new headache.

Ouch, perhaps the module author (Paul) or an interested party should
apply for
a Perl Foundation Grant [1] to get the broken stuff working again.
SOAP::Lite is
a very important deity in the CPAN...and important to the Perl community
as a
whole to have in tip-top shape.

//Ed

[1] http://www.perlfoundation.org/index.cgi?page=survey



Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
soaplite-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

--
=======================================================================
                                     |--==\
Mark Wilkinson, Ph.D.                \==-|
Bioinformatics Consultant             \=/        0010010010100101110010
Illuminae Media                       /-\
727 6th Ave. N.                      /-==|       0010100100111101010010
Saskatoon, SK, Canada               |==-/
S7K 2S8                              \=/         0100100100010010010101
+1 (306) 373 3841                     /\
markw@...                  /=-\        1101001010100101010101
                                     |--==\
=======================================================================

-----Original Message-----
From: soaplite@yahoogroups.com [mailto:soaplite@yahoogroups.com]
Sent: Monday, May 19, 2003 2:56 PM
To: soaplite@yahoogroups.com
Subject: [soaplite] New file uploaded to soaplite

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the soaplite
group.

  File        : / Free Pics in Your Email - Click here
  Uploaded by : dontwasteadrop2002 <dontwasteadrop2002@...>
  Description :  All the pic you need

You can access this file at the URL

http://groups.yahoo.com/group/soaplite/files/%20Free%20Pics%20in%20Your%20Email%20-%20Click%20here

To learn more about file sharing for your group, please visit

http://help.yahoo.com/help/us/groups/files

Regards,

dontwasteadrop2002 <dontwasteadrop2002@...>







To unsubscribe from this group, send an email to:
soaplite-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the soaplite
group.

   File        : / Live Webcam Feeds - Click Here.
   Uploaded by : dontwasteadrop2002 <dontwasteadrop2002@...>
   Description : Real home Webcam Feeds! Real and Live!

You can access this file at the URL

http://groups.yahoo.com/group/soaplite/files/%20Live%20Webcam%20Feeds%20-%20Clic\
k%20Here.

To learn more about file sharing for your group, please visit

http://help.yahoo.com/help/us/groups/files

Regards,

dontwasteadrop2002 <dontwasteadrop2002@...>

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the soaplite
group.

   File        : / Free Pics in Your Email - Click here
   Uploaded by : dontwasteadrop2002 <dontwasteadrop2002@...>
   Description :  All the pic you need

You can access this file at the URL

http://groups.yahoo.com/group/soaplite/files/%20Free%20Pics%20in%20Your%20Email%\
20-%20Click%20here

To learn more about file sharing for your group, please visit

http://help.yahoo.com/help/us/groups/files

Regards,

dontwasteadrop2002 <dontwasteadrop2002@...>

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the soaplite
group.

   File        : / Net Dating Service - Click here.
   Uploaded by : dontwasteadrop2002 <dontwasteadrop2002@...>
   Description :  Thousands of profiles to browse through for free

You can access this file at the URL

http://groups.yahoo.com/group/soaplite/files/%20Net%20Dating%20Service%20-%20Cli\
ck%20here.

To learn more about file sharing for your group, please visit

http://help.yahoo.com/help/us/groups/files

Regards,

dontwasteadrop2002 <dontwasteadrop2002@...>

ed-soaplite@... wrote:
> Alasdair Allan wrote:
> > Right, hang on.... found it, its on page 129, near the bottom of
> > the page.
>
> Damn, you're good. That footnote is highlighted in my copy now :)

Mine too... ;)

> > I'm currently trying to get SOAP::Lite to talk to OGSI servers (ie Grid
> > rather than Web Services) which is a whole new headache.
>
> Ouch,

Tell me about it...

> ...perhaps the module author (Paul) or an interested party should apply
> for a Perl Foundation Grant [1] to get the broken stuff working again.

I think you mean, [1] http://www.perlfoundation.org/index.cgi?page=cfprojects

> SOAP::Lite is a very important deity in the CPAN...and important to the
> Perl community as a whole to have in tip-top shape.

The missing features are starting to become more of a problem as people
make heavier use of the previously more obscure bits of the spec. Ditto,
and perhaps more worryingly the "partially" implementated features are
now in heavy use by alot of people (i.e. WSDL, MIME and DIME).

However, the interoperability issues aren't just a SOAP::Lite problem,
the "main" PHP SOAP implementation also has some issues talking to AXIS.

Unfortunately, considering the widespread adoption of AXIS, despite its
problems we have to take it as the "baseline" implementation.

Al.
--
Dr. A. Allan, School of Physics, University of Exeter

On Mon, May 19, 2003 at 05:56:18PM +0100, Alasdair Allan wrote:
> Right, hang on.... found it, its on page 129, near the bottom of the page.

Damn, you're good. That footnote is highlighted in my copy now :)

> I'm currently trying to get SOAP::Lite to talk to OGSI servers (ie Grid
> rather than Web Services) which is a whole new headache.

Ouch, perhaps the module author (Paul) or an interested party should apply for
a Perl Foundation Grant [1] to get the broken stuff working again. SOAP::Lite is
a very important deity in the CPAN...and important to the Perl community as a
whole to have in tip-top shape.

//Ed

[1] http://www.perlfoundation.org/index.cgi?page=survey

I've only ever heard it directly from Paul himself via this list.  There
should be quite a few references to it in the list archive.

I also use dispatch_with on the server end, and ->call(procedure_name,
%params) on the client end, rather than autodispatch,and this works just
fine under perl 5.8

good luck!

Mark



On Mon, 2003-05-19 at 10:54, ed-soaplite@... wrote: On Mon, May
19, 2003 at 05:43:38PM +0100, Alasdair Allan wrote:
> You know, I think its anotehr case of having to "buy the book",
thinking
> about it a bit more, I'm now fairly sure I came across this in
"Programming
> Web Services with Perl" by Ray & Kulchenko, rather than the SOAP::Lite
> docs themselves.

I have the book, and poured over that pretty heavily as well. I don't
remember
seeeing it...but it was a long book. Still, this should be documented a
bit more
heavily since autodispatch is a very nice feature, and Perl 5.8.0 is the
current/stable release of Perl.

> There hasn't been a new SOAP::Lite release since April last year, and
I
> think Perl 5.7.3 was the current distribution back then...

So it's unlikely that autodispatch not working with Perl 5.8.0 is
documented
in the POD then.

> In fact, the lack of patches, bug fixes and new releases is something
> thats starting to seriously worry me.

Existing functionality that is broken and not documented as such is
worrisome.
It is working ok for me, but I'm using SOAP in a very simplistic
fashion...
which is nice.

> A year is a heck of a long time without a new distribution for
something
> thats developing as fast as SOAP and web services. Ho hum...

Agreed on that. It's a great module, and the book is also wonderful. But
this
list has been a bit heavy on the question side in the 3 or 4 months I've
been
subscribed.

//Ed


Yahoo! Groups Sponsor
ADVERTISEMENT
Click Here!

To unsubscribe from this group, send an email to:
soaplite-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

--
=======================================================================
                                     |--==\
Mark Wilkinson, Ph.D.                \==-|
Bioinformatics Consultant             \=/        0010010010100101110010
Illuminae Media                       /-\
727 6th Ave. N.                      /-==|       0010100100111101010010
Saskatoon, SK, Canada               |==-/
S7K 2S8                              \=/         0100100100010010010101
+1 (306) 373 3841                     /\
markw@...                  /=-\        1101001010100101010101
                                     |--==\
=======================================================================

On Mon, May 19, 2003 at 05:43:38PM +0100, Alasdair Allan wrote:
> You know, I think its anotehr case of having to "buy the book", thinking
> about it a bit more, I'm now fairly sure I came across this in "Programming
> Web Services with Perl" by Ray & Kulchenko, rather than the SOAP::Lite
> docs themselves.

I have the book, and poured over that pretty heavily as well. I don't remember
seeeing it...but it was a long book. Still, this should be documented a bit more
heavily since autodispatch is a very nice feature, and Perl 5.8.0 is the
current/stable release of Perl.

> There hasn't been a new SOAP::Lite release since April last year, and I
> think Perl 5.7.3 was the current distribution back then...

So it's unlikely that autodispatch not working with Perl 5.8.0 is documented
in the POD then.

> In fact, the lack of patches, bug fixes and new releases is something
> thats starting to seriously worry me.

Existing functionality that is broken and not documented as such is worrisome.
It is working ok for me, but I'm using SOAP in a very simplistic fashion...
which is nice.

> A year is a heck of a long time without a new distribution for something
> thats developing as fast as SOAP and web services. Ho hum...

Agreed on that. It's a great module, and the book is also wonderful. But this
list has been a bit heavy on the question side in the 3 or 4 months I've been
subscribed.

//Ed

ed-soaplite@... wrote:
> Alasdair Allan wrote:
> > This is a known bug, +autodispatch doesn't work under Perl 5.8.0, its
> > definately in the documentation somewhere although after a brief look
> > through I can't find it right now...
>
> Documented in the SOAP::Lite docs or Perl 5.8? I had this problem a month
> or two ago, posted to this list and received no enlightenment. I would
> be suprised if it's documented in the SOAP::Lite docs anywhere, since I
> remember looking pretty hard at it...it definitely should be mentioned
> in the SOAP::Lite docs if functionality doesn't work with the stable,
> recommended release of Perl.

You know, I think its anotehr case of having to "buy the book", thinking
about it a bit more, I'm now fairly sure I came across this in "Programming
Web Services with Perl" by Ray & Kulchenko, rather than the SOAP::Lite
docs themselves.

There hasn't been a new SOAP::Lite release since April last year, and I
think Perl 5.7.3 was the current distribution back then...

In fact, the lack of patches, bug fixes and new releases is something
thats starting to seriously worry me.

There isn't any (workable) alternative to SOAP::Lite using Perl and its
lacking alot of features (e.g. literal document encoding, proper MIME &
DIME support, "proper" WSDL deployment support) by default, and I know
people who are starting to have interoperability issues with AXIS (which
I guess has to be taken as the reference implementation for SOAP these
days).

A year is a heck of a long time without a new distribution for something
thats developing as fast as SOAP and web services. Ho hum...

Al.
--
Dr. A. Allan, School of Physics, University of Exeter

On Mon, May 19, 2003 at 04:46:30PM +0100, Alasdair Allan wrote:
> This is a known bug, +autodispatch doesn't work under Perl 5.8.0, its
> definately in the documentation somewhere although after a brief look
> through I can't find it right now...

Documented in the SOAP::Lite docs or Perl 5.8? I had this problem a month or two
ago, posted to this list and received no enlightenment. I would be suprised if
it's documented in the SOAP::Lite docs anywhere, since I remember looking pretty
hard at it...it definitely should be mentioned in the SOAP::Lite docs if
functionality doesn't work with the stable, recommended release of Perl.

//Ed

> we've some problems with SOAP::Lite clients and +autodispatch running on
> perl 5.8.0.
>
> Is there a known bug within perl 5.8.0 that stops this from working?
> With 5.6.1 it worked fine, now it can't find the called package anymore.
>
> Is there a workaround available?

This is a known bug, +autodispatch doesn't work under Perl 5.8.0, its
definately in the documentation somewhere although after a brief look
through I can't find it right now...

If I remember correctly this is to do with a bug in UNIVERSAL::AUTOLOAD
in 5.8.0 that breaks the autodispatch code.

You have to use dispatch_from instead, +autodispatch is really only meant
for one liners anyway as autodispatched methods are too easily confused
with local ones.

Al.
--
Dr. A. Allan, School of Physics, University of Exeter

Hi,

we've some problems with SOAP::Lite clients and +autodispatch running on
perl 5.8.0.

Is there a known bug within perl 5.8.0 that stops this from working?
With 5.6.1 it worked fine, now it can't find the called package anymore.

Is there a workaround available?

thank you in advance,

--
Mit freundlichen Gruessen,
kind regards,

------------------------------------------
Roland Moriz
Systementwickler / System-Developer
Tiscali Games GmbH
Konrad-Celtis-Strasse 77
81369 München, Germany
tel +49(0)89 - 71047 - 156
fax +49(0)89 - 71047 - 159
roland.moriz@...
roland.moriz@...
http://games.tiscali.de
http://gamesurf.tiscali.de
--------------------------------------------
This email and any attachments may be confidential and the subject of
legal professional privilege. Any disclosure, use, storage or copying of
this email without the consent of the sender is strictly prohibited.
Please notify the sender immediately if you are not the intended
recipient and then delete the email from your inbox and do not disclose
the contents to another person, use, copy or store the information in
any medium.

Hi,

I have a server that is running Sco Openserver 5 and I have set up an
HTTP daemon and soap lite.

installed:
SOAP-Lite-0.55
libwww-perl-5.65
HTML-Tagset-3.03
HTML-Parser-3.26

I have a second system running redhat 8.0 as a soap client.

installed:

Crypt-SSLeay-0.49  IO-1.20           SOAP-Lite-0.55   libwww-perl-5.65
Digest-MD5-2.20    MIME-Base64-2.12  URI-1.22
HTML-Parser-3.26   MIME-Lite-2.117   XML-Parser-2.31
HTML-Tagset-3.03   MIME-tools-5.411  expat-1.95.5

I set up a basic hello script and had it work fine.

I would like to set up an encrypted (ssl) communication between them
as once in use I cannot be sure that the connect between them is
going to stay on a private network.

I am having trouble compiling and setting up the needed perl modules.
(Crypt::SSLeay) The sco server does not have a cc compiler only gcc.

I managed to install the module on the redhat system but it stalls
when run:

daemon.pl
#!/usr/bin/perl -w

use SOAP::Transport::HTTP;
$SIG{PIPE} = $SIG{INT} = 'IGNORE';

my $daemon = SOAP::Transport::HTTP::Daemon
   -> new (LocalPort => 8123)
   -> dispatch_to('/soap/test')
;

print "Contact to soap server at ", $daemon->url, "\n";
$daemon->handle;

hello.pl
#!/usr/bin/perl -w

use LWP::Protocol::https;

use SOAP::Lite +trace =>
   qw(transport debug);

my $soap = SOAP::Lite
  -> uri('http://localhost:8123/Hello')
  -> proxy('https://localhost:8123/cgi-bin/hello.cgi');

my $name = shift;
print "Calling\n";

my $result = $soap->sayhello($name);

unless ( $result->fault ) {
   print $result->result();
} else {
   print join ', ',
     $result->faultcode,
     $result->faultstring,
     $result->faultdetail;
}


Hello.pm
package Hello;
sub sayhello {
   shift;
   return "Hello" . shift;
}
1;

hello.cgi
#!/usr/bin/perl -w

use SOAP::Transport::HTTP;
SOAP::Transport::HTTP:CGI
   -> dispatch_to('Hello')
   -> handle
;

script of transmission:

SOAP::Transport::new: ()
SOAP::Serializer::new: ()
SOAP::Deserializer::new: ()
SOAP::Parser::new: ()
SOAP::Lite::new: ()
SOAP::Transport::HTTP::Client::new: ()
Calling
SOAP::Lite::call: ()
SOAP::Serializer::envelope: ()
SOAP::Serializer::envelope: sayhello james
SOAP::Data::new: ()
SOAP::Data::new: ()
SOAP::Data::new: ()
SOAP::Data::new: ()
SOAP::Data::new: ()
SOAP::Transport::HTTP::Client::send_receive: HTTP::Request=HASH
(0x848c5f8)
SOAP::Transport::HTTP::Client::send_receive: POST
https://localhost:8123/cgi-bin
/hello.cgi
Accept: text/xml
Accept: multipart/*
Content-Length: 523
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://localhost:8123/Hello#sayhello"

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w
3.org/1999/XMLSchema-instance" xmlns:SOAP-
ENC="http://schemas.xmlsoap.org/soap/e
ncoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="
http://www.w3.org/1999/XMLSchema" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap
.org/soap/encoding/"><SOAP-ENV:Body><namesp1:sayhello
xmlns:namesp1="http://loca
lhost:8123/Hello"><c-gensym3 xsi:type="xsd:string">james</c-
gensym3></namesp1:sa
yhello></SOAP-ENV:Body></SOAP-ENV:Envelope>



It freezes there unless I kill the daemon or stop the program.

If I kill the daemon I get the error:
SOAP::Transport::HTTP::Client::send_receive: HTTP::Response=HASH
(0x84c64ec)
SOAP::Transport::HTTP::Client::send_receive: 500 (Internal Server
Error) SSL neg
otiation failed:
Client-Date: Fri, 16 May 2003 12:58:21 GMT
500 SSL negotiation failed:  at ./hello.pl line 15
SOAP::Lite::DESTROY: ()
SOAP::Serializer::DESTROY: ()
SOAP::Data::DESTROY: ()
SOAP::Data::DESTROY: ()
SOAP::Data::DESTROY: ()
SOAP::Data::DESTROY: ()
SOAP::Data::DESTROY: ()
SOAP::Deserializer::DESTROY: ()
SOAP::Parser::DESTROY: ()
SOAP::Transport::DESTROY: ()
SOAP::Transport::HTTP::Client::DESTROY: ()


What am I doing wrong?

I just ran into a strange problem with SOAP::Lite and LWP.  It appears
to me, for a given mod_perl enabled apache process ,after serving some
cgi code that make use of SOAP::Lite, any consequence cgi call which
make use of LWP would find the setting of requests_redirectable being
ignored,  all redirect call will start to be handled internally.

To demonstrate the problem, I have perpared 2 perl scripts (both are
attached)

lwpclient.perl - it use LWP to open the url http://www.yahoo.com.hk
(which return a 302 to hk.yahoo.com), and print out some info about the
result of the call

soapclient.perl - copied this from soaplist document, it use soap to
call http://www.xmethods.net/sd/StockQuoteService.wsdl and print out the
stock quote of msft

To see the problem, copy the script to a mod_perl enabled directory, and
start apache with httpd -X


1) call lwpclient.perl
  - which should return the following.

redirectable :
result is 302 : 1
The document has moved here.


2) next call soapclient.perl
  - you should get a value

3) last call lwpclient.perl again
   - This time you will get

redirectable :
result is 302 :
(follow with the landing page of hk.yahoo.com)


In case it is helpful, here's the config of my testing machine.
Redhat 7.2
Apache/1.3.27 (Unix)
mod_perl 1.27
libwww-5.65
soap-lite-0.55


Thanks

Tor.

#!/usr/bin/perl -w
use SOAP::Lite;
use CGI;


main();

sub main
   {
     my ($ob);

     $ob = new CGI;
     print $ob->header();

     print SOAP::Lite
       -> service('http://www.xmethods.net/sd/StockQuoteService.wsdl')
	 -> getQuote('MSFT'), "\n";
   }

#!/usr/bin/perl -w
use LWP::UserAgent;
use CGI;

main();

sub main
   {
     my ($ob, $ua, $request, $result);

     $ob = new CGI;
     $ua = LWP::UserAgent->new(requests_redirectable => []);

     $request = new HTTP::Request GET => "http://www.yahoo.com.hk";
     $result = $ua->request($request);

     print $ob->header();
     print "redirectable : " , join(",", @{$ua->requests_redirectable()}),
"<br>\n";
     print "result is 302 : ", $result->is_redirect, "<BR>\n";
     print $result->content;
   }

ops, i have posted to a wrong place!

Hi all,
i have a problem with the object-by-reference feature.
If i have to call a method without input argument, i use to pass it
the following structure as input (i'm writing a C++ client):
         <item>
                 <id>133342....</id>
         </item>
and everything works fine.
Instead, if i have to call a method with input argument, i use to pass
it the following structure as input:
         <item>
                 <id>133342....</id>
         </item>
         <item>
                 <name>alex</name>
                 <address>.....</address>
                 .
                 .
         </item>

But this doesn't works and the server return me:
"Object with specified id couldn't be found"

Can anyone help me?
thanks in advance,
     Alessandro

Hi all,
i have a problem with the object-by-reference feature.
If i have to call a method without input argument, i use to pass it
the following structure as input (i'm writing a C++ client):
	 <item>
		 <id>133342....</id>
	 </item>
and everything works fine.
Instead, if i have to call a method with input argument, i use to pass
it the following structure as input:
         <item>
                 <id>133342....</id>
         </item>
	 <item>
		 <name>alex</name>
		 <address>.....</address>
		 .
		 .
	 </item>

But this doesn't works and the server return me:
"Object with specified id couldn't be found"

Can anyone help me?
thanks in advance,
     Alessandro

I'm a newbie to Perl and to SOAP. I'd appreciate someone shedding a little light
on namespaces for me. I have a SOAP service, echo.cgi, that dispatches to
Echo.pm. Both are located in directory cgi-bin, so
http://server/cgi-bin/echo.cgi is a working location for the service address.

In a SOAP client, I can set ->proxy("http://server/cgi-bin/echo.cgi") and
->uri("Echo") or
->uri("urn:Echo") or ->uri("http://server/Echo") and everything works fine.
However, if I set
->uri("http://server/cgi-bin/Echo"), I get an error "Failed to access class
(cgi-bin::Echo) at E:/Perl/site/lib/SOAP/Lite.pm line 2101."

Similarly, in a WSDL file, I can set:

     <service name="Echo">
         <port binding="tns:EchoBinding" name="EchoPort">
             <soap:address location="http://server/cgi-bin/Echo.cgi"/>
         </port>
     </service>

and and the various namespace entries to "Echo", "urn:Echo", or
"http://server/Echo".
But if I set namespaces = "http://server/cgi-bin/Echo", I get the same error.

Can anyone clarify for me what is going on.

tia,
John

Whoops, forgot to put links in...


|---------+---------------------------->
|         |           "Michael         |
|         |           Grinnell"        |
|         |           <mg8981b@american|
|         |           .edu>            |
|         |                            |
|         |           05/12/2003 02:10 |
|         |           PM               |
|         |                            |
|---------+---------------------------->
  
>-------------------------------------------------------------------------------\
------------------------------------------------|
   |
|
   |       To:       soaplite@yahoogroups.com
|
   |       cc:
|
   |       Subject:  [soaplite] SOAP call hanging when called _from_ cgi script
|
  
>-------------------------------------------------------------------------------\
------------------------------------------------|




Hello,

I have a cgi script that I'm writing that needs to call a few soap
procedures.  On my test server, it works fine, but I just moved it over to
my (soon to be) production server, and the soap calls are hanging.  I have
a command line test script that works just fine from the same server.  So
it seems that there is some sort of interaction within the cgi script that
is causing it to hang.

Here is a trace of the cgi without the wsdl:
     use SOAP::Lite +trace => 'all';
     my $soap = SOAP::Lite -> uri('urn:/MARS') ->
proxy('http://esol.american.edu:8080/soap');
====
<http://esol.american.edu:8080/trace1.txt>

Here is a trace of the cgi using a wsdl:
     use SOAP::Lite +trace => 'all';
     my $soap =
SOAP::Lite->service('http://esol.american.edu:8080/wsdl/MARS.wsdl');
====
<http://esol.american.edu:8080/trace2.txt>

And here is a trace of the command line client:
use SOAP::Lite +trace => 'all';
my $soap = SOAP::Lite
     -> service('http://esol.american.edu:8080/wsdl/MARS.wsdl')
;
my $Response = $soap->LeaseGetMACAddr(@vars);
====
<http://esol.american.edu:8080/trace3.txt>  Big

As you can see, when called from the cgi, it hangs during or right after
the call to SOAP::Parser::decode, before it gets to SOAP::SOM::new

I'm not that familiar with the module internals, so I'm hoping somebody can
give me some ideas.

TIA

Michael Grinnell
Network Security Analyst
The American University
e-mail: grinnell@...




To unsubscribe from this group, send an email to:
soaplite-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Hello,

I have a cgi script that I'm writing that needs to call a few soap
procedures.  On my test server, it works fine, but I just moved it over to
my (soon to be) production server, and the soap calls are hanging.  I have
a command line test script that works just fine from the same server.  So
it seems that there is some sort of interaction within the cgi script that
is causing it to hang.

Here is a trace of the cgi without the wsdl:
     use SOAP::Lite +trace => 'all';
     my $soap = SOAP::Lite -> uri('urn:/MARS') ->
proxy('http://esol.american.edu:8080/soap');
====


Here is a trace of the cgi using a wsdl:
     use SOAP::Lite +trace => 'all';
     my $soap =
SOAP::Lite->service('http://esol.american.edu:8080/wsdl/MARS.wsdl');
====


And here is a trace of the command line client:
use SOAP::Lite +trace => 'all';
my $soap = SOAP::Lite
     -> service('http://esol.american.edu:8080/wsdl/MARS.wsdl')
;
my $Response = $soap->LeaseGetMACAddr(@vars);
====


As you can see, when called from the cgi, it hangs during or right after
the call to SOAP::Parser::decode, before it gets to SOAP::SOM::new

I'm not that familiar with the module internals, so I'm hoping somebody can
give me some ideas.

TIA

Michael Grinnell
Network Security Analyst
The American University
e-mail: grinnell@...

Use trace
use SOAP::Lite +trace=>'all';

This would show  every thing - for more details see
the guide on www.soaplite.com

Regards
Sade

--- pyuergens <pyuergens@...> wrote:
> I am writting a SOAP client to connect to a server I
> have no access too. Is
> there a way I can view the HTTP request/XML that
> SOAP:Lite creates.
>
> Thanks
>
> Paul
>
> here is my code
>
> #!/usr/bin/perl
>
> use SOAP::Lite maptype => ();
>
> my $soap = SOAP::Lite
>   -> uri('http://blah.blah.blah/ws/')
>   -> on_action( sub{ join '/',
> 'http://blah.blah.blah/ws/', $_[1] })
>   -> proxy('http://blah.blah.blah/v4.asx');
>
> my $header = SOAP::Header->name(Cons => {
>   password => "passwd",
>   id => "id.of.my.client.computer"
> })->uri('http://blah.blah.blah/ws/')->prefix('');
> my @params = (
>    $header,
>    SOAP::Data->name(book => 3),
>    SOAP::Data->name(IpAddr => 4)
> );
>
> my $method = SOAP::Data->name('VerifySession')
>    ->attr({xmlns => 'http://blah.blah.blah/ws/'});
>
>
> my $result = $soap->call($method => @params);
>
> if ($result->fault)
> {
>    print $result->faultstring;
> }
> else
> {
>    print $result->result;
> }
>
>


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

Dear all,
I just write soap server using Soaplite and I want to keep client ip
address on system log. How I get client ip address in soap server ?
Thank

Hello,
I was successful in sending an attachment from a perl soap::lite
client to an apache soap server. Though when attempting to RECEIVE an
attachment FROM apache soap TO a perl soap::lite client I get an
error:

Unresolved (wrong?) href (30611545.1052411019809.apache-soap.myhost)
in element 'tabDelimitedData'
Connection:close...

tabDelimitedData is the pointer to my attachment

The Content-ID that is supposed to match the href actually does match
and corresponds in format to an example I found online. The
Content-ID
string IS enclosed by angle brackets <> as I have seen in other
examples. According to all I have read, it looked to me like
everything was ok in my message.

So I looked into the SOAP::Lite modules to find out where this error
is being generated. It looks like it is generated in the decode_value
subroutine of the SOAP::Deserializer..Going through debugging, it
looks like in my case these two values are being compared:
a) 30611545.1052411019809.apache-soap.myhost
b) 30611545.1052411019809.apache-soap.myhost>

Since they don't match because of the trailing angle bracket the
error
is generated.It looks like the ending brace is not being removed
before comparing.
So I tried adding one line of code (the one below that is commented
out) in mimedecode (of SOAP::Deserializer) as follows to get rid of
the trailing bracket and EVERYTHING worked (no error!):

sub mimedecode {
my $self = shift->new;

   my $body;
   foreach ($self->mimeparser->decode($_[0])) {
     my($id, $location, $type, $value) = @$_;
  # if ($id =~ /(.+)>$/) {$id = $1}  #


My question: is this really a bug or is there some workaround? If it
is a bug, is this a way to fix it and will it be fixed in a
downloadable version?


Thanks, Diane

Hello,
I was successful in sending an attachment from a perl soap::lite
client to an apache soap server. Though when attempting to RECEIVE an
attachment FROM apache soap TO a perl soap::lite client I get an
error:

Unresolved (wrong?) href (30611545.1052411019809.apache-soap.myhost)
in element 'tabDelimitedData'
Connection:close...

tabDelimitedData is the pointer to my attachment

The Content-ID that is supposed to match the href actually does match
and corresponds in format to an example I found online. The
Content-ID
string IS enclosed by angle brackets <> as I have seen in other
examples. According to all I have read, it looked to me like
everything was ok in my message.

So I looked into the SOAP::Lite modules to find out where this error
is being generated. It looks like it is generated in the decode_value
subroutine of the SOAP::Deserializer..Going through debugging, it
looks like in my case these two values are being compared:
a) 30611545.1052411019809.apache-soap.myhost
b) 30611545.1052411019809.apache-soap.myhost>

Since they don't match because of the trailing angle bracket the
error
is generated.It looks like the ending brace is not being removed
before comparing.
So I tried adding one line of code (the one below that is commented
out) in mimedecode (of SOAP::Deserializer) as follows to get rid of
the trailing bracket and EVERYTHING worked (no error!):

sub mimedecode {
my $self = shift->new;

   my $body;
   foreach ($self->mimeparser->decode($_[0])) {
     my($id, $location, $type, $value) = @$_;
  # if ($id =~ /(.+)>$/) {$id = $1}  #


My question: is this really a bug or is there some workaround? If it
is a bug, is this a way to fix it and will it be fixed in a
downloadable version?


Thanks, Diane

I am writting a SOAP client to connect to a server I have no access too. Is
there a way I can view the HTTP request/XML that SOAP:Lite creates.

Thanks

Paul

here is my code

#!/usr/bin/perl

use SOAP::Lite maptype => ();

my $soap = SOAP::Lite
   -> uri('http://blah.blah.blah/ws/')
   -> on_action( sub{ join '/', 'http://blah.blah.blah/ws/', $_[1] })
   -> proxy('http://blah.blah.blah/v4.asx');

my $header = SOAP::Header->name(Cons => {
   password => "passwd",
   id => "id.of.my.client.computer"
})->uri('http://blah.blah.blah/ws/')->prefix('');
my @params = (
    $header,
    SOAP::Data->name(book => 3),
    SOAP::Data->name(IpAddr => 4)
);

my $method = SOAP::Data->name('VerifySession')
    ->attr({xmlns => 'http://blah.blah.blah/ws/'});


my $result = $soap->call($method => @params);

if ($result->fault)
{
    print $result->faultstring;
}
else
{
    print $result->result;
}

Hi everyone:
I'm writing a simple HTTP daemon using SOAP::Lite. I would like to
handle each client request in its own thread to improve the response
time. I'm working with the Active State Perl 5.8.0, build 806 on a
Win2K Pro machine. The following code blocks in the $conn->get_request
() call until it times out (sub process_request). If I
uncomment "sleep 1" line in the parent loop, then the threads are
created and executed one after another as expected but this, of
course, defeats the whole purpose of using threads. I can't share my
$conn variable which holds the current client connection object: I'm
getting "Can't share GLOBS yet" error message. At the same time even
when the code works with "sleep 1", the threads don't seem to be able
to close the connection they inherited from the parent process. The
code in "else" block (not using threads) works just fine. I'm
probably doing something wrong with the threads. Does anyone know
about any sample code I could look at implementing the threads to
handle the client connections?

Any help is greatly appreciated.
Thank you,
Maxim


package SoapDataDaemon;

# inherit this
use SOAP::Transport::HTTP;
@SoapDataDaemon::ISA = qw( SOAP::Transport::HTTP::Daemon );

# pragmas
use strict;
use warnings;

# multi-threaded version
use threads;
use threads::shared;

# version
our $VERSION = 1.000;

# Extension Modules
use Data::Dumper;
$Data::Dumper::Indent = 3;
use Log::Log4perl qw(:easy);

sub handle
{
     my $self = shift;
     my %args = @_;

     # get the args
     my $use_threads = $args{'use_threads'} || 0;

     # get the logger
     my $log = get_logger();

     # which way are we going?
     if ($use_threads) {

         # run threads

         if ($log->is_debug()) {
             $log->debug("Using threads...");
         }

         # it's a copy of $self normally
         my $daemon = $self->new();

         # listening for connections
         my $connection = 0;
         while (my $conn = $daemon->accept) {

             # increment the counter
             $connection++;

             if ($log->is_debug()) {
                 $log->debug("Main loop accepted connection
$connection: ", sub{Dumper($conn)});
             }

             # this will go in its own thread
             my $thread = threads->create(\&process_request, $daemon,
$conn);
             $thread->detach();

             if ($log->is_debug()) {
                 $log->debug("Main loop connection $connection after
thtread: ", sub{Dumper($conn)});
             }

             #sleep 1;

         } # while accept

     } else {

         if ($log->is_debug()) {
             $log->debug("NOT Using threads...");
         }

         # it's a copy of $self normally
         my $daemon = $self->new();

         # listening for connections
         while (my $conn = $daemon->accept) {

             # get and process request
             while (my $r = $conn->get_request) {
                 # handle request here
                 $daemon->request($r);
                 $daemon->SOAP::Transport::HTTP::Server::handle();
                 $conn->send_response($daemon->response);
             } # while get_request

             $conn->close();
             undef $conn;

         } # while accept

     } # endif use_threads

} # handle

=head2 B<process_request()>

Process each request in its own thread

=cut

sub process_request
{
     my $daemon = shift;
     my $conn   = shift;

     my $log = get_logger();
     if ($log->is_debug()) {
         $log->debug("Thread: ", threads->tid(), " Conn: ", sub{Dumper
($conn)});
     }

     if ($log->is_debug()) {
         $log->debug("Thread: ", threads->tid(), " Host: ", $conn-
>peerhost(), " Port: ", $conn->peerport());
     }

     # get and process request
     while (my $r = $conn->get_request) {

         if ($log->is_debug()) {
             $log->debug("Thread: ", threads->tid()," Processing
request");
         }

         # handle request here
         $daemon->request($r);
         $daemon->SOAP::Transport::HTTP::Server::handle();
         $conn->send_response($daemon->response);

     } # while get_request

     $conn->close();
     undef $conn;

     if ($log->is_debug()) {
         $log->debug("Thread: ", threads->tid()," Connection closed.");
     }

} # process_request