soaplite-devel — SOAP::Lite developers

[Soaplite-devel] SOAP::Lite::Simple Version 1.2 on CPAN

[Leo L. <ran...@gm...>]

Hi list,

Several updates on SOAP::Lite::Simple 1.2, just hit CPAN:

http://search.cpan.org/dist/SOAP-Lite-Simple/

SOAP::Lite::Simple                          Simple frame work for  
talking with web services
SOAP::Lite::Simple::DotNet       talk with .net webservices
SOAP::Lite::Simple::Real             talk with 'real' webservices,  
e.g. not .net

As usual feedback welcome.

Leo

Changes:

1.2 Sat 6th Aug 2005
     - Updated docs - replacing soap:Fault with Fault/faultstring
     - Updated docs - lots of minor things and reorganise packages
     - added 'filename' option, instead of 'xml' for fetch()
     - fetch() now returns 1 or undef
         - use $obj->results() or $obj->results_xml() to get data

1.1 Mon 1st Aug 2005
     - Updated documentation
     - Added XML wrapper so can parse several top level nodes,
       removed before converting to SOAP Data structure.
     - Switched to check for Fault/faultstring, any Namespace
     - Added strip_default_xmlns which defaults to true
       makes parsing results easier
     - Added t/02_dotnet.pl

[Soaplite-devel] SOAP::Lite::Simple - version 1

[Leo L. <ran...@gm...>]

Hi,

SOAP::Lite::Simple version 1 hit CPAN last night:

SOAP::Lite::Simple
Simple frame work for talking with web services

SOAP::Lite::Simple::DotNet
talk with .net webservices

SOAP::Lite::Simple::Real
talk with 'real' webservices, e.g. not .net

1.0 Sat 23rd July 2005
     - Added in validation of the XML responce
         - check it is valid XML
         - check for soap:Fault/faultstring
         - check for soapenv:Fault/faultstring
     - Updated documentation to mention
         - results()
         - results_xml()

Feedback welcome.

Leo

Re: [Soaplite-devel] SOAP::Lite::Simple

[Mark F. <mar...@ea...>]

From: "Byrne Reese" <by...@ma...>
> Can you tell the group what it does and how it is different from
> SOAP::Lite::Complicated? :)

That made me laugh. But, I do feel that S::L has a problem in the area of
over-complication. Too many ways to do things. Is it just me who thinks this
is a problem? It seems like it makes it difficult to document how to use
S::L. Difficult for newbies to figure out where to start?

I've mentioned on the user list that I have a quick-start of examples. I've
sent them to quite a few people and everyone says it helped them get up and
running quickly, understand the syntax, and have a working client and server
they could begin to experiment with. Is this something you guys would want
to put on one of the web sites you manage? Or, in the distribution? I can
email it to you if you want to have a look.

Mark

Re: [Soaplite-devel] SOAP::Lite::Simple

[Byrne R. <by...@ma...>]

I downloaded it, but there is no README file. Can you tell the group 
what it does and how it is different from SOAP::Lite::Complicated? :)

Byrne

Leo Lapworth wrote:

> Hi,
>
> I thought I'd give you a heads up that I just put SOAP::Lite::Simple  
> on CPAN.
>
> It's very rudimentary, but from the feedback I've have from the  
> London.pm list it
> seems to be useful.
>
> Enjoy.
>
> Leo
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted 
> by HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> Soaplite-devel mailing list
> Soa...@li...
> https://lists.sourceforge.net/lists/listinfo/soaplite-devel

[Soaplite-devel] SOAP::Lite::Simple

[Leo L. <ran...@gm...>]

Hi,

I thought I'd give you a heads up that I just put SOAP::Lite::Simple  
on CPAN.

It's very rudimentary, but from the feedback I've have from the  
London.pm list it
seems to be useful.

Enjoy.

Leo

[Soaplite-devel] Can anyone help with a document/literal example please

[Arun R. <ar...@ao...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
<font size="2"><font face="Arial,sans-serif">Hi,<br>
<br>
I am trying to find an exmaple that uses document/liternal instead of
RPC style. Can anyone help with an example please.<br>
<br>
Thanks<br>
--Aron<br>
</font></font>
</body>
</html>

[Soaplite-devel] BUG: Multiple calls of the same method on same object don't work

[Jason B. <ja...@sh...>]

Multiple calls of the same method on same object don't work Using 0.65_6,
after creating a module for eBay's SOAP interface doing:

my $ebay = new eBayAPIInterfaceService();
$ebay->GeteBayOfficialTime(@params, @headers);
$ebay->GeteBayOfficialTime(@params, @headers);

Does not work. The first GeteBayOfficialTime() call works but the second
generates a fault. Looking at the HTTP headers and XML generated shows the
problem the first call's HTTP headers are:

POST
https://api.sandbox.ebay.com/wsapi?callname=GeteBayOfficialTime&siteid=0&version=413&Routing=default
HTTP/1.1
Accept: text/xml
Accept: multipart/*
Accept: application/soap
Content-Length: 1828
Content-Type: text/xml; charset=utf-8
SOAPAction: ""

while the seconds's is:

POST
https://api.sandbox.ebay.com/wsapi?callname=GeteBayOfficialTime&siteid=0&version=413&Routing=default
HTTP/1.1
Accept: text/xml
Accept: multipart/*
Accept: application/soap
User-Agent: SOAP::Lite/Perl/0.65_6
Content-Length: 1828
Content-Type: text/xml; charset=utf-8; charset=utf-8
SOAPAction: ""

The User-Agent header is added, as well as a second "charset=utf8" to the
Content-Type. I'm not sure which is causing the problem.

0.60 creates identical headers and does not have this problem.

--
Jason Bodnar
ja...@sh...
http://www.shakabuku.org

"You want free speech? Let's see you acknowledge a man whose words make
your blood boil who is standing center stage advocating at the top of
his lungs that which you would spend a lifetime opposing at the top of
yours." -- President Andrew Shephard, "The American President"

[Soaplite-devel] Minimal Install Patch

[Matthew W. <mw...@re...>]

Hi,

I noticed that there wasn't an option to just install the minimal set of
prerequisites during a Soap::Lite build. I have attached a patch that
enables this option if anyone is interested (just pass --minimal as a
build option to use it).

This patch is useful as it allows for automated reproducible builds on
any system regardless of what perl modules are already installed.

If you have any questions please let me know.

Thanks

Matt Wringe 

[Soaplite-devel] Basic Help

[Shane F. <fu...@ci...>]

I've got a web service that is deployed in Weblogic 8.1 that comes with a
TestSoap interface through WebLogic Integration. When I use the interface
there it works fine but now I'm trying to figure out how to access it from a
script using SOAP::Lite and I'm stuck.  The address for the weblogic server
is:

 

http://hostname:7001/sample_app/test/GetCustomer.jpd and the method I'm
calling is clientRequest. When I run it in the Workshop Test Browser it
gives this for the SOAP message:

 

<SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 

<SOAP-ENV:Header> 

<StartHeader xmlns="http://www.openuri.org/2002/04/soap/conversation/"> 

<callbackLocation>http://TESTUI</callbackLocation>

</StartHeader>

</SOAP-ENV:Header>

<SOAP-ENV:Body> 

<clientRequest xmlns="http://www.openuri.org/"> 

<Cim_Customer xmlns=""> 

<CustAcctID> 

<integKeyCommon>1380</integKeyCommon>

<integKeyRef>1</integKeyRef>

</CustAcctID>

<custCompanyName>string</custCompanyName>

<CustAddress> 

<custAddrCompanyName>string</custAddrCompanyName>

<custAddrFloor>2</custAddrFloor>

<custAddrBldgName>string</custAddrBldgName>

<custAddrBlockNum>2</custAddrBlockNum>

<custAddrLotNum>2</custAddrLotNum>

<custAddrBldgNum>2</custAddrBldgNum>

<custAddrTown>string</custAddrTown>

<custAddrCity>string</custAddrCity>

<custAddrPrefecture>string</custAddrPrefecture>

<custAddrCountry>string</custAddrCountry>

<custAddrZip>string</custAddrZip>

</CustAddress>

<CustAcctTransaction> 

<transVerifTransactionID>1</transVerifTransactionID>

</CustAcctTransaction>

</Cim_Customer>

</clientRequest>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

 

 

What is the syntax in a perl script using SOAP::Lite to access this. I can't
seem to get this right. It keeps coming back with what appear to be
namespace problems because it won't access clientRequest and it says that it
can't recognize the method in that namespace. Thanks for any help.

 

Shane

[Soaplite-devel] mod_perl-2 support

[Randy K. <ra...@th...>]

mod_perl-2 underwent a namespace change recently -
see http://perl.apache.org/docs/2.0/rename.html for
details, and the reasons why. This new namespace is
incorporated into the official mod_perl-2 release, which
is just now on CPAN.

The following patch works for me in getting SOAP::Lite to
work for a simple mod_perl Apache::SOAP handler with the
current CPAN mod_perl-2 - this is against the CPAN
Soap-Lite-0.65_5 version, as I couldn't get a cvs diff
working (an error about not being able to create a
/tmp/some_dir arose):

============================================================
--- lib/SOAP/Transport/HTTP.pm.orig	Wed Mar 30 02:58:34 2005
+++ lib/SOAP/Transport/HTTP.pm	Sat May 21 20:26:26 2005
@@ -505,23 +505,22 @@
     $self = $class->SUPER::new(@_);
     SOAP::Trace::objects('()');
   }
-  die "Could not find or load mod_perl"
-      unless (eval "require mod_perl");
-  die "Could not detect your version of mod_perl"
-      if (!defined($mod_perl::VERSION));
-  if ($mod_perl::VERSION < 1.99) {
-      require Apache;
+ MOD_PERL: {
+    (eval { require Apache;} ) and do {
       require Apache::Constants;
       Apache::Constants->import('OK');
       $self->{'MOD_PERL_VERSION'} = 1;
-  } elsif ($mod_perl::VERSION < 3) {
-      require Apache::RequestRec;
-      require Apache::RequestIO;
-      require Apache::Const;
-      Apache::Const->import(-compile => 'OK');
+      last MOD_PERL;
+    };
+    (eval { require Apache2::RequestRec;} ) and do {
+      require Apache2::RequestUtil;
+      require Apache2::RequestIO;
+      require Apache2::Const;
+      Apache2::Const->import(-compile => 'OK');
       $self->{'MOD_PERL_VERSION'} = 2;
-  } else {
-      die "Unsupported version of mod_perl";
+      last MOD_PERL;
+    };
+    die "Unsupported version of mod_perl";
   }
   return $self;
 }
@@ -529,12 +528,17 @@
 sub handler {
   my $self = shift->new;
   my $r = shift;
-  $r = Apache->request if (!$r && $self->{'MOD_PERL_VERSION'} == 1);
+  unless ($r) {
+    $r = ($self->{'MOD_PERL_VERSION'} == 1) ?
+      Apache->request : Apache2::RequestUtil->request();
+  }

+  my $cl = ($self->{'MOD_PERL_VERSION'} == 1) ?
+    $r->header_in('Content-length') : $r->headers_in->{'Content-length'};
   $self->request(HTTP::Request->new(
     $r->method() => $r->uri,
     HTTP::Headers->new($r->headers_in),
-    do { my ($c,$buf); while ($r->read($buf,$r->header_in('Content-length'))) { $c.=$buf; } $c; }
+    do { my ($c,$buf); while ($r->read($buf,$cl)) { $c.=$buf; } $c; }
   ));
   $self->SUPER::handle;

@@ -545,10 +549,23 @@
   # will emulate normal response, but with custom status code
   # which could also be 500.
   $r->status($self->response->code);
-  $self->response->headers->scan(sub { $r->header_out(@_) });
-  $r->send_http_header(join '; ', $self->response->content_type);
-  $r->print($self->response->content);
-  return $self->{'MOD_PERL_VERSION'} == 2 ? &Apache::OK : &Apache::Constants::OK;
+  if ($self->{'MOD_PERL_VERSION'} == 1 ) {
+    $self->response->headers->scan(sub { $r->header_out(@_) });
+    $r->send_http_header(join '; ', $self->response->content_type);
+    $r->print($self->response->content);
+    return &Apache::Constants::OK;
+  }
+  else {
+    $self->response->headers->scan(sub {
+                                     my %h = @_;
+                                     for (keys %h) {
+                                       $r->headers_out->{$_} = $h{$_};
+                                     }
+                                   });
+    $r->content_type(join '; ', $self->response->content_type);
+    $r->print($self->response->content);
+    return &Apache2::Const::OK;
+  }
 }

 sub configure {

=================================================================

Also, the following diff:

================================================================
--- Makefile.PL.orig	Sun Nov 14 13:30:46 2004
+++ Makefile.PL	Sat May 21 21:23:28 2005
@@ -13,7 +13,8 @@
   ["Client SMTP/sendmail support","SOAP::Transport::MAILTO::Client",{"MIME::Lite" => 0},1],
   ["Client FTP support","SOAP::Transport::FTP::Client",{"Net::FTP" => 0,"IO::File" => 0},0],
   ["Standalone HTTP server","SOAP::Transport::HTTP::Daemon",{"HTTP::Daemon" => 0},1],
-  ["Apache/mod_perl server","SOAP::Transport::HTTP::Apache",{"Apache" => 0},0],
+  ["Apache-1.3/mod_perl server","SOAP::Transport::HTTP::Apache",{"Apache" => 0},0],
+  ["Apache-2.0/mod_perl server","SOAP::Transport::HTTP::Apache",{"Apache2::RequestRec" => 0},0],
   ["FastCGI server","SOAP::Transport::HTTP::FCGI",{"FCGI" => 0},0],
   ["POP3 server","SOAP::Transport::POP3::Server",{"Net::POP3" => 0,"MIME::Parser" => 0},1],
   ["IO server","SOAP::Transport::IO::Server",{"IO::File" => 0},0],

=======================================================================

alters the Makefile.PL prerequisites to enquire about
adding either mod_perl-1 or mod_perl-2 support.

-- 
best regards,
randy kobes

[Soaplite-devel] Undeliverable Mail

[Postmaster <pos...@ge...>]

User mailbox exceeds allowed message count: inf...@ge...
User mailbox exceeds allowed message count: jm...@ge...
User mailbox exceeds allowed message count: ma...@ge...


Original message follows.

Received: from petsjdnje.net [24.163.120.240] by geo.net.co
  (SMTPD32-8.13) id AFDBA171014C; Tue, 17 May 2005 02:40:11 -0500
From: soa...@li...
To: Fre...@ge...
Date: Tue, 17 May 2005 07:18:05 UTC
Subject: Auslaenderpolitik
Importance: Normal
X-Priority: 3 (Normal)
MIME-Version: 1.0
Message-ID: <70d...@li...>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-IMAIL-SPAM-DNSBL: (Spamhaus-SBL+XBL,9fdba171014c728b,127.0.0.4)
X-IMAIL-SPAM-DNSBL: (Composite-Blocking-List,9fdba171014c728b,127.0.0.2)
X-IMAIL-SPAM-DNSBL: (SORBS,9fdba171014c728b,127.0.0.10)

Lese selbst:
http://www.mjoelnirsseite.de/2100.htm

Re: [Soaplite-devel] use_prefix on SOAP::Transport::HTTP::CGI

[Delfim M. <db...@co...>]

ok, i forgot that ones.

but do i need to hack SOAP::Transport::HTTP::CGI to pass the  
default_ns like i did to use_prefix?

On May 7, 2005, at 16:51, Byrne Reese wrote:

> In 0.65_4 and 0.65_5, I might suggest you investigate using  
> default_ns() and ns() to turn on and off default namespacing.  
> use_prefix is now deprecated.
>
> Delfim Machado wrote:
>
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> hi again, this is my first, ugly, approach ... since i'm just   
>> focused, for now, on the use_prefix option
>>
>> - --- lib/SOAP/Transport/HTTP.pm  2005-05-06 18:43:05.000000000 +0100
>> +++ /usr/local/share/perl/5.8.0/SOAP/Transport/HTTP.pm   
>> 2005-05-06  18:42:00.000000000 +0100
>> @@ -391,6 +391,9 @@
>> sub handle {
>>    my $self = shift->new;
>> +  $self->serializer->use_prefix($self->options->{'use_prefix'})
>> +    if exists($self->options->{'use_prefix'});
>> +
>>    my $length = $ENV{'CONTENT_LENGTH'} || 0;
>>    if (!$length) {
>>
>>
>> in your cgi server
>>
>>   SOAP::Transport::HTTP::CGI
>>     -> dispatch_to (
>>       '/home/PERLWEBSERVICES/WS/SPAM/lib',
>>       'WS::SPAM'
>>     )
>>     -> options (
>>       {
>>         'use_prefix' => undef
>>       }
>>     )
>>     -> handle
>>   ;
>>
>>
>> i'm using 0.65-beta4
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.1 (Darwin)
>>
>> iD8DBQFCe7Gr6XDsmUqBS/QRAqZyAJ9/bLVjBtpORb5Cyv0otZQI5Ylh5QCfYeHD
>> fz751DoWS9Xe9nuwtVnPClQ=
>> =/WQr
>> -----END PGP SIGNATURE-----
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: NEC IT Guy Games.
>> Get your fingers limbered up and give it your best shot. 4 great  
>> events, 4
>> opportunities to win big! Highest score wins.NEC IT Guy Games.  
>> Play to
>> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
>> _______________________________________________
>> Soaplite-devel mailing list
>> Soa...@li...
>> https://lists.sourceforge.net/lists/listinfo/soaplite-devel
>>
>
>
>

Re: [Soaplite-devel] use_prefix on SOAP::Transport::HTTP::CGI

[Byrne R. <by...@ma...>]

In 0.65_4 and 0.65_5, I might suggest you investigate using default_ns() 
and ns() to turn on and off default namespacing. use_prefix is now 
deprecated.

Delfim Machado wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hi again, this is my first, ugly, approach ... since i'm just  
> focused, for now, on the use_prefix option
>
> - --- lib/SOAP/Transport/HTTP.pm  2005-05-06 18:43:05.000000000 +0100
> +++ /usr/local/share/perl/5.8.0/SOAP/Transport/HTTP.pm  2005-05-06  
> 18:42:00.000000000 +0100
> @@ -391,6 +391,9 @@
> sub handle {
>    my $self = shift->new;
> +  $self->serializer->use_prefix($self->options->{'use_prefix'})
> +    if exists($self->options->{'use_prefix'});
> +
>    my $length = $ENV{'CONTENT_LENGTH'} || 0;
>    if (!$length) {
>
>
> in your cgi server
>
>   SOAP::Transport::HTTP::CGI
>     -> dispatch_to (
>       '/home/PERLWEBSERVICES/WS/SPAM/lib',
>       'WS::SPAM'
>     )
>     -> options (
>       {
>         'use_prefix' => undef
>       }
>     )
>     -> handle
>   ;
>
>
> i'm using 0.65-beta4
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
>
> iD8DBQFCe7Gr6XDsmUqBS/QRAqZyAJ9/bLVjBtpORb5Cyv0otZQI5Ylh5QCfYeHD
> fz751DoWS9Xe9nuwtVnPClQ=
> =/WQr
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great 
> events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Soaplite-devel mailing list
> Soa...@li...
> https://lists.sourceforge.net/lists/listinfo/soaplite-devel

Re: [Soaplite-devel] use_prefix on SOAP::Transport::HTTP::CGI

[Delfim M. <db...@co...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi again, this is my first, ugly, approach ... since i'm just  
focused, for now, on the use_prefix option

- --- lib/SOAP/Transport/HTTP.pm  2005-05-06 18:43:05.000000000 +0100
+++ /usr/local/share/perl/5.8.0/SOAP/Transport/HTTP.pm  2005-05-06  
18:42:00.000000000 +0100
@@ -391,6 +391,9 @@
sub handle {
    my $self = shift->new;
+  $self->serializer->use_prefix($self->options->{'use_prefix'})
+    if exists($self->options->{'use_prefix'});
+
    my $length = $ENV{'CONTENT_LENGTH'} || 0;
    if (!$length) {


in your cgi server

   SOAP::Transport::HTTP::CGI
     -> dispatch_to (
       '/home/PERLWEBSERVICES/WS/SPAM/lib',
       'WS::SPAM'
     )
     -> options (
       {
         'use_prefix' => undef
       }
     )
     -> handle
   ;


i'm using 0.65-beta4

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFCe7Gr6XDsmUqBS/QRAqZyAJ9/bLVjBtpORb5Cyv0otZQI5Ylh5QCfYeHD
fz751DoWS9Xe9nuwtVnPClQ=
=/WQr
-----END PGP SIGNATURE-----

[Soaplite-devel] use_prefix on SOAP::Transport::HTTP::CGI

[Delfim M. <db...@pr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

it is planned to put this option here?

i'm developing a web service to interop with some other languages and  
the "namesp1" is killing them :)

Is there a workaround?

- --
Delfim Machado
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFCe5f+6XDsmUqBS/QRAnPYAJ9Nc1GDABFfMg8iKDsp8bU4YU3OMQCfYJe/
Xd+I/UkVd/u4CFuxkUAL/WY=
=i1Sz
-----END PGP SIGNATURE-----

[Soaplite-devel] Javascript SOAP

[Anish K. K <an...@vi...>]

Hi

I use the perl to do the SOAP services and in the client side I am
using javascript...Unfortunately I am getting errors. I tried
different combinations and end result is :(

the sample perl code...
#######################
use SOAP::Transport::HTTP;

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

package RegisterUser;
sub createUser
{
my ($firstName,$lastName,$clientName,$email)=3D@_;
.....
return $result;
}
#############################

The javascript code I used to invoke is...Only pasting the relevant
one...
#########################
var soapCall =3D new SOAPCall();
soapCall.transportURI =3D"http://aaa.cc.com/cgi-
bin/user/RegisterUser.pl"
soapCall.actionURI =3D "RegisterUser";
var fname =3D new SOAPParameter(firstname,"firstname");
var lname =3D new SOAPParameter(lastname,"lastname");
var paramsArray =3D new Array(fname,lname);

soapCall.encode
(0,"createUser","RegisterUser",0,null,paramsArray.length,paramsArray);
var soapResponse =3D soapCall.invoke();
var soapFault =3D soapResponse.fault;
alert ("Failed: "+soapFault.faultCode);
alert ("Reason: "+soapFault.faultString);

#########################

For the First alert I am getting as

Failed: Client

and for the second one..

Reason: SoapAction shall match 'uri#method' if present
(got 'RegisterUser', expected RegisterUser#createUser

I tried the variuos combination.. Please help to proceed

Thanks
Anish

[Soaplite-devel] [SOAP::Lite 0.60] SOAP::Schema::WDSL patch

[Razvan-Daniel M. <raz...@me...>]

Hi list,

when using stubmaker.pl I stumbled over a small typo in SOAP::Schema::WDSL.

Attached is the patch to correct it.

Regards,

Razvan

Re: [Soaplite-devel] Apache2/mod_perl2

[Byrne R. <by...@ma...>]

It is supposed to work in the next release. I believe code is available 
in the beta version. At least one more Beta version will be released 
soon (Beta 3) - I just need to get around to it.

Byrne

Lai Zit Seng wrote:

> Hi,
>
> I'm wondering if SOAP::Lite is supposed to work with Apache2/mod_perl2?
>
> The 'perl Makefile.PL' step doesn't seem to find the prerequisite 
> support for Apache/mod_perl server.
>
> Regards,
>
> .lzs
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Soaplite-devel mailing list
> Soa...@li...
> https://lists.sourceforge.net/lists/listinfo/soaplite-devel

[Soaplite-devel] Apache2/mod_perl2

[Lai Z. S. <la...@co...>]

Hi,

I'm wondering if SOAP::Lite is supposed to work with Apache2/mod_perl2?

The 'perl Makefile.PL' step doesn't seem to find the prerequisite support 
for Apache/mod_perl server.

Regards,

.lzs

[Soaplite-devel] changelog: SSL (and CPAN)

[Kees C. <ke...@os...>]

Hi!  Just noticed the code changes for HTTP::Server::Daemon in SSL mode 
are in 0.65 (but not in 0.60), yet the 0.65 changelog doesn't list it.
I'm very happy to see this in the code now.  :)

Also, is it possible to upload the 0.65 (or earlier iterations) to CPAN?  
0.60 is ancient when compared to 0.65.  :)

Take care!

-- 
Kees Cook
Open Source Development Lab
ke...@os...

Re: [Soaplite-devel] SOAP::Lite 0.60, Axis and attachments

[Byrne R. <by...@ma...>]

FYI - this change has been integrated in to SOAP::Lite 0.65 Beta 1

Peter Kaas wrote:

>Hi There,
>
>I'm trying SOAP::Lite and Axis with attachments. I had to change one
>thing to get it to work, see the patch below.  It has to do with the
>local-ization of the BOUNDARY_DELIMITER inside of a block where it is
>not being used.
>
>Furthermore, you may want to update your examples and show that one can
>use a:
>
>   SOAP::Data->name(...)->attr({ href => 'cid:...' })
>
>object to refer to a specific MIME part.
>
>regards,
>
>---
> Peter...
>
>
>Patch:
>
>--- /export/home/prkas/temp/SOAP-Lite-0.60/lib/SOAP/Lite.pm     2003-08-18 20:44:18.000000000 +0200
>+++ /usr/share/perl5/SOAP/Lite.pm       2004-05-10 13:01:33.000000000 +0200
>@@ -2985,6 +2985,7 @@
>     $headers->header('Content-Type' => 'Multipart/Related; type="text/xml"; start="<main_envelope>"; boundary="'.$top->head->multipart_boundary.'"');
>   }
> 
>+    local $MIME::Entity::BOUNDARY_DELIMITER = "\r\n";
>   $serializer->on_nonserialized($self->on_nonserialized);
>   my $response = $self->transport->send_receive(
>     endpoint => $self->endpoint,
>
>
>--
>   "History teaches that grave threats to liberty often come in times of
>    urgency, when constitutional rights seem too extravagant to endure."
>            - Justice Thurgood Marshall, 1989
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Sleepycat Software
>Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
>deliver higher performing products faster, at low TCO.
>http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
>_______________________________________________
>Soaplite-devel mailing list
>Soa...@li...
>https://lists.sourceforge.net/lists/listinfo/soaplite-devel
>
>  
>

Re: [Soaplite-devel] accessing WSDL file with NTLM authentication

[Andrew P. <an...@pi...>]

On Tue, Oct 19, 2004 at 05:51:03PM -0700, Byrne Reese wrote:
> Thank you so much for pointing this out to the development team. I know 
> it has been a while since you wrote this, but you and your input is not 
> forgotten.

Thanks.  FWIW, I've been doing basically what I described before in the
meantime (the goal again was to use NTLM to authenticate to the SOAP
server).

    1.  Download the WSDL file "by hand", and passing it to
        SOAP::Lite->service as a file:// URL.

    2.  Tell the LWP used for real SOAP calls to use NTLM with this
        horribly code:

        $soap->proxy($url,  # this just needs the right hostname
            credentials => [ $host_port, '',
                             '\\' . $windows_username, $windows_password ],
            conn_cache => LWP::ConnCache->new,
        );

I again look forward to getting rid of this hack with the new release!

Andrew

Re: [Soaplite-devel] accessing WSDL file with NTLM authentication

[Byrne R. <by...@ma...>]

Thank you so much for pointing this out to the development team. I know 
it has been a while since you wrote this, but you and your input is not 
forgotten.

I have integrated this suggestion into the next release of SOAP::Lite - 
0.65 beta 2. It will hopefully be released at the end of this week.

Andrew Pimlott wrote:

>I am using SOAP::Lite to access a Windows 2003 server with NTLM
>authentication required.  I've looked at the hacks in the cookbook, but
>I don't think they will suffice, because I need to use NTLM not just for
>the SOAP calls, but for accessing the WSDL file.
>
>Generally, I would really like to be able to pass in my own
>LWP::UserAgent to use for all web requests.  This allows for both
>great flexibility and better use of resources.  Would it be hard to add
>this?  Can anyone suggest an approach?
>
>In this case, I think I can work-around the problem by downloading the
>WSDL file by hand, and giving it SOAP::Lite as a file: URL; then using
>the SOAP::Transport::HTTP::Client::get_basic_credentials (or another)
>trick for the SOAP requests.  But I hope I can come up with a better
>solution in the end.
>
>Andrew
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>Soaplite-devel mailing list
>Soa...@li...
>https://lists.sourceforge.net/lists/listinfo/soaplite-devel
>
>  
>

Re: [Soaplite-devel] UDDI v2/3 support (Re: [soaplite] SOAP::Lite 0.65 Development Update)

[Mark F. <mar...@ea...>]

----- Original Message ----- 
From: "Paul Kulchenko" <pau...@ya...>
>
>... It would be great if you could write a working
> example with a real v2 server.

Paul, I did write a working example which exercises *every* v2 inquiry
method. The problem is, there was no good way I could think of to do this on
any server (a real server) and know what the values are. It would have to
start at the top (find_business) and drill its way down. That may not be a
good example of each method since the example would be dependent upon the
content of a server. It could take a lot of processing to get to a specific
method a user wants to exercise.

I opted for the ability to invoke a single method (API) with hard-coded
values. Which means, the user would have to use a registry's UI to look up
some values and plug them into the script.

What I have would be easily modified into a "start from the top and drill
down" script. I'm just not sure I would want an example like that if I were
(as I am) the novice user. I'd rather the documentation say "go to a
registry, look up some values and plug them into the script for the method
you want to execute. At worst, its' just not going to find anything -- which
is a good starting point to delve into why it didn't.

I've attached the script and you're more than welcome to include it in the
examples. I started to do a "publishv2" script. But, that got to be too
tedious. I also felt it wouldn't be as useful since most people wouldn't
have publish authority to any server. I figured if they could master
inquiryv2, they could probably figure out how to inoke publishing calls.
Maybe just an example of one publish to illustrate how to do authentication?
I've got that.

Mark

Re: [Soaplite-devel] UDDI v2/3 support (Re: [soaplite] SOAP::Lite 0.65 Development Update)

[Mark F. <mar...@ea...>]

Byrne

I think the only interface change is using "uddiversion => 2" on the "use"
statement.

Example:

==============

my $uddi_server = 'http://uddi.microsoft.com/inquire';

use UDDI::Lite uddiversion => 2,      # UDDI v2
  +trace=>[qw(headers fault debug)],  # displays raw UDDI messages
(send/receive)
  +autodispatch => proxy => $uddi_server,
  import => 'UDDI::Data',
  import => ['UDDI::Lite' => ':find']   # import find method names
;

===============

There may have also been a change to the importable labels. They are delete,
auth, save, validate, find, get. Or, inquiry or publish (which import
respective subsets of the preceeding).

It should be noted that v3 support is incomplete. The problem with v3 is
that the schema uses more non-UDDI namespaces. Accessing attributes and
elements is not as automatic as v1 and v2.

This began to be a problem in v2 when the language attribute was xml:lang.
This wasn't too bad with just one attribute requiring special qualifiying on
two elements (name and description). But, v3 is taking this to new levels.
xml:lang occurs on more elements. And, other namespaces are being used (like
"dsig" on
the signiture *element*).

There are some other things which I'm not sure how UDDI::Lite should or
shouldn't try to handle. Like v3's new support for multi-queries into a
single complex query. I remember something else stood out to me but I can't
find it at the moment. (It was the XML feature which lets you specify the
rules at validation time. I thought one of the methods had this.)

Mark