-------------- Original message from "Oeschey, Lars (I/ET-83, extern)" <extern.lars.oeschey@...>: --------------

> You will find that the "500 Internal Server Error" is returned for
> many cases where there is a problem on the server side like missing
> parameters or restrictive file permissions. The 500 error is what I
> would expect for the situation you describe.
> It would be nice to get something more descriptive from SOAP.
> However, the error condition you describe is not a problem with SOAP
> (transport), but a problem with the service/subroutine itself. If
> you have access to the parameter list on the server side before it's
> (automatically?) parsed, you should be able to check that list and
> return your own SOAP error code and string if parameters are missing
> or invalid.

hm, I asked the company that is responsible for the server side of the
SOAP I use. They told me they send a faultcode etc., it looks like this:

HTTP/1.1 500 Internal Server Error
Connection: close
Content-Type: text/xml; charset=utf-8
Content-Length: 561
Server: Indy/9.0.18
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<soap:Fault>
<soap:faultcode>soap:Server</soap:faultcode>
<soap:faultstring>
IdSoapRpcXml.TIdSoapReaderXML.GetParameter: Parameter
&#34;in2&#34; not found in list &#34;&#34;
</soap:faultstring>
<detail xsi:type="EIdSoapRequirementFail"></detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>

However with your example code

use SOAP::Lite;
$soap= SOAP::Lite
->uri('http://soap.data.inform.com')
->proxy('http://soapserver.tld:3003/soap/');

eval {$soapReply = $soap->teInput("lala,lulu");};
if ($@) {
chomp ($@);
print "Server Error ->" . $@ . "<-...skipping";
}
elsif ($soapReply->fault) {
print "Fault code from function ->" .
$soapReply->faultcode . "<-";
print "Fault string from function ->" .
$soapReply->faultstring . "<-...skipping";
}
else {
print $soapReply;
}

I get nothing more than the 500 Server error. I think I should also get
the soap->faultcode etc., something must be still wrong on my side
then...

> I'm not a great perl person, but doesn't using eval put the fault
string
> out of scope for the block in which you are attempting to print?

I also practically never used eval, so I don't know ;)

> I've always been able to get the error message back - and I
> never use eval
> (i understand that it is handy for trapping errors and not
> crashing the script)

The eval was a workaround, since without using it, I wouldn't get
*anything* back in case of error, the http 500 error wouldn't even come
back to me, and I had no idea if the call was successful.

> also, why are you testing the error path through your code, or do
> you really want to send a single param in your call ?
> (as opposed to teInput("lala", "lulu");)

hm, what do you mean?

Lars

I got a bit further on this, though not very successful. Using the
->trace method of SOAP::Lite, I could see what I'm sending and
receiving:

sent:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.
org/soap/encoding/"
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:teInput xmlns:namesp1="http://soap.data.inform.com">
<c-gensym3 xsi:type="xsd:string">MAN9999999/1</c-gensym3>
<c-gensym5 xsi:type="xsd:string">LAD1020</c-gensym5>
<c-gensym7 xsi:type="xsd:int">1</c-gensym7>
</namesp1:teInput>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

received:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xs="http://www.
w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<soap:Fault>
<soap:faultcode>soap:Server</soap:faultcode>
<soap:faultstring>IdSoapRpcXml.TIdSoapReaderXML.GetParameter: Parameter
"in2" not found in list
"c-gensym3,c-gensym5,c-gensym7"</soap:faultstring>
<detail xsi:type="EIdSoapRequirementFail"></detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>

looking at the wsdl file, I see that the third parameter should be
string, while I send int (though I didn't do anything, somewhere it gets
autotyped):

<message name="teInput">
<part name="in0" type="xs:string"/>
<part name="in1" type="xs:string"/>
<part name="in2" type="xs:string"/>
</message>

So this is the reason, why it's denied. But: Why don't I get the fault
parameters? With this:

use SOAP::Lite;# +trace => [qw(all)];
my $soap= SOAP::Lite
	 ->uri('http://soap.data.inform.com')
	 ->proxy('http://audiinsa00220.in.audi.vwg:3003/soap/');

my $som=$soap->teInput("MAN9999999/1", "LAD1020", "1");

if ($som->fault) {
	 print $som->faultdetail;
	 print $som->faultcode;
	 print $som->faultstring;
	 print $som->faultactor;
}

I only get:
500 Internal Server Error at soaptest.pl line 6

and: How can I force the parameter to be a string?

Lars

----- Original Message -----

From: Oeschey, Lars (I/ET-83, extern)

To: soaplite@yahoogroups.com

Sent: Wednesday, October 01, 2008 3:28 AM

Subject: RE: [soaplite] Re: How to get errors

> I'm not a great perl person, but doesn't using eval put the fault
string
> out of scope for the block in which you are attempting to print?

I also practically never used eval, so I don't know ;)

> I've always been able to get the error message back - and I
> never use eval
> (i understand that it is handy for trapping errors and not
> crashing the script)

The eval was a workaround, since without using it, I wouldn't get
*anything* back in case of error, the http 500 error wouldn't even come
back to me, and I had no idea if the call was successful.

> also, why are you testing the error path through your code, or do
> you really want to send a single param in your call ?
> (as opposed to teInput("lala", "lulu");)

hm, what do you mean?

Lars

Hi,

I am using SOAP-Lite v 0.710.08.  I am trying to get the result data
from the xml response, but I keep getting error 'Can't call
method "dataof" without a package or object reference at ...'.

Here is the response I am getting back from the webservice request:

<ServiceResponse>
	 <RequestType>CheckListenerStatus</RequestType>
	 <SuccessInd>Y</SuccessInd>
	 <Response>The Listener service is currently running.</Response>
	 <RequestDateTime>10/02/2008 13:12:01</RequestDateTime>
</ServiceResponse>

I then get the error when I make the following call:

my $successInd = $som->dataof('//ServiceResponse/SuccessInd');

How can I fix this?

> the parameter missing error you are receiving is because it
> expects two (3)
> args, and you were only sending one - now, you do need to get your
> error detection working - and i haven't had any problem printing
> the faultcode and strings -
> i recommend you read the wsdl with soap lite that will get
> the type correct.
> in your second response

as you can see from the post after that one (btw, this is the slowest
list I know, not from participants but post speed, i.e. yahoo ;)), I've
been able to trace sent and received stuff. I also managed meanwhile, to
force the third parameter into "string" type, which can be seen with the
trace. I still get the same error from the other side, which I blame on
the server side now, but I still don't get the faultcode/string, and it
definitely is sent (which is also seen in the trace mentioned in the
previous mail)

> faultstring may only contain
> "500 Internal Server Error at soaptest.pl line 6"
> perhaps your server side code is bad?

maybe server-side code is bad... but the 500 Message comes not from
*within* SOAP but is just the transport error (same as with a web
server). I do see the SOAP fault in the trace, and it looks like it
should be captured by SOAP::Lite, but it isn't...

regards, Lars

> I keep getting error 'Can't call
> method "dataof" without a package or object reference at ...'.


> my $successInd = $som->dataof('//ServiceResponse/SuccessInd');

Appears your $som object is an empty string.

--
Radek

> <message name="teInput">
> <part name="in0" type="xs:string"/>
> <part name="in1" type="xs:string"/>
> <part name="in2" type="xs:string"/>
> </message>

First don't input raw values to teInput function. Follow your service
description.
Something like this:

my $som=$soap->teInput(
                                       SOAP::Data->name(in0 => 'MAN9999999/1'),
                                       SOAP::Data->name(in1 => 'LAD1020'),
                                       SOAP::Data->name(in2 =>
1)->type('string'),
                                       );


--
Radek

> > <message name="teInput">
> > <part name="in0" type="xs:string"/>
> > <part name="in1" type="xs:string"/>
> > <part name="in2" type="xs:string"/>
> > </message>
>
> First don't input raw values to teInput function. Follow your service
> description.
> Something like this:
>
> my $som=$soap->teInput(
>                                       SOAP::Data->name(in0 =>
> 'MAN9999999/1'),
>                                       SOAP::Data->name(in1 =>
> 'LAD1020'),
>                                       SOAP::Data->name(in2 =>
> 1)->type('string'),

great, this works! Thanks a lot! Would you mind explaining what the
difference is now? Can I maybe read up somewhere about generic Soap
handling? It seems my fault was just not following "best practice", so
I'd like to know what "best practice" would be ;)

Lars

> First don't input raw values to teInput function. Follow your service
> description.
> Something like this:
>
> my $som=$soap->teInput(
>                                       SOAP::Data->name(in0 =>
> 'MAN9999999/1'),
>                                       SOAP::Data->name(in1 =>
> 'LAD1020'),
>                                       SOAP::Data->name(in2 =>
> 1)->type('string'),

This works good for the positive case (i.e. all values are good). If I
want to get an error, by sending the last value as string, I should get
an error from $som->fault however. I only get a http 500 error. The
trace contains the fault though:

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/s
oap/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><teInput
xmlns="http://soap.data.inform.com"><in0
xsi:type="xsd:string">MAN9999999/1</in0><in1 xsi:type="xsd:st
ring">LAD22010</in1><in2
xsi:type="xsd:int">1</in2></teInput></soap:Body></soap:Envelope>
SOAP::Transport::HTTP::Client::send_receive:
HTTP::Response=HASH(0x1e38270)
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 500 Internal
Server Error
Cache-Control: proxy-revalidate
Connection: close
Date: Mon, 06 Oct 2008 13:44:41 GMT
Server: Indy/9.0.18
Content-Length: 689
Content-Type: text/xml; charset=utf-8
Client-Date: Mon, 06 Oct 2008 13:44:40 GMT
Client-Peer: 10.250.52.241:8080
Client-Response-Num: 1

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xs="http://www.
w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Body><soap:F
ault><soap:faultcode>soap:Server</soap:faultcode><soap:
faultstring>Type Mismatch. For the parameter in2, the type found was
"int" in the namespace
"http://www.w3.org/2001/XMLSchema", which
doesn't match any of the expected values:
{http://www.w3.org/2001/XMLSchema}string</soap:faultstring><detail
xsi:type="EIdSoapRequirementFail"></d
etail></soap:Fault></soap:Body></soap:Envelope>

I'm trying to get the fault like this:

if ($som->fault) {
	 print $som->faultdetail; # returns value of 'detail' element as
                             	 # string or object
	 print $som->faultcode;   #
	 print $som->faultstring; # also available
	 print $som->faultactor;  #
}
else {print "result:$som\n";}

> I'm trying to get the fault like this:
>
> if ($som->fault) {
> print $som->faultdetail; # returns value of 'detail' element as
> # string or object
> print $som->faultcode; #
> print $som->faultstring; # also available
> print $som->faultactor; #
> }
> else {print "result:$som\n";}

You should get the fault this way. You may changed the $som object
before calling a fault method.


--
Radek

> great, this works! Thanks a lot! Would you mind explaining what the
> difference is now? Can I maybe read up somewhere about generic Soap
> handling? It seems my fault was just not following "best practice", so
> I'd like to know what "best practice" would be ;)

A request expects a soap structure which is done by SOAP::Data class.
Check the SOAP::Lite docs.

--
Radek

We have Perl v5.8.0 client code that has always targeted SOAP 1.2
with SOAP::Lite 0.55.  It runs against a remote server with the same
releases.  We recently moved all of the client code to a new Linux
system with Perl 5.8.5 and SOAP::Lite 0.710.08. Now, when
communicating with the remote server we get error: Content-Type must
be 'text/xml' instead of 'application/soap'

I understand SOAP 1.2 uses this new content type over the old v1.1
text/xml, but again, this code has been working for years. The remote
server has not changed! We still have the old client system up and
can do side by side testing.

I tried changing the SOAP version to 1.1 just to send the content-
type that it's expecting, but then other issues come up, like a
hardcoded prefix SOAP-ENC:Array needs to be soapenc:Array.

Can I force the content-type of a v1.2 transaction to text/xml?
What else can be done to remedy this situation?  The people who own
the remote server will certainly not upgrade because of this.

Thanks!

> I tried changing the SOAP version to 1.1 just to send the content-
> type that it's expecting, but then other issues come up, like a
> hardcoded prefix SOAP-ENC:Array needs to be soapenc:Array.
>
> Can I force the content-type of a v1.2 transaction to text/xml?
> What else can be done to remedy this situation? The people who own
> the remote server will certainly not upgrade because of this.

You can change the content-type with

$soap->transport->http_request->header('Content-type' => 'text/xml');

--
Radek

I wrote:
> > I tried changing the SOAP version to 1.1 just to send the content-
> > type that it's expecting, but then other issues come up, like a
> > hardcoded prefix SOAP-ENC:Array needs to be soapenc:Array.
> >
> > Can I force the content-type of a v1.2 transaction to text/xml?
> > What else can be done to remedy this situation? The people who own
> > the remote server will certainly not upgrade because of this.

Radek responded
> You can change the content-type with
>
> $soap->transport->http_request->header('Content-type' => 'text/xml');

Thank you for the suggestion. This does change the header but the
server is now complaining that the client is using the wrong SOAP
version. There is a major difference between the headers sent before
and after the upgrade.

Before upgrade:

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

After upgrade:

<soap:Envelope
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:soapenc="http://www.w3.org/2003/05/soap-encoding"
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding"
   xmlns:soap="http://www.w3.org/2003/05/soap-envelope">

It looks like the server isn't prepared for the v2003 schemas that come
with SOAP::Lite v0.710 compared to v0.55 - and we cannot change the
server. As mentioned in my original post, SOAP-ENC:Array is hardcoded
into the transaction code and doesn't agree with the newer schema
anyway.

My current recommendation to the client is to downgrade SOAP::Lite and
that probably involves a downgrade of Perl as well, and that may affect
yet other dependencies. Better suggestions are welcome.

I'm hoping for a quick solution here, but my client is willing to pay
to get this resolved quickly if a solution needs to be more involved.
So far I have emailed Paul Kulchenko to request compensated services
but I have not received a response. I welcome emails from qualified
developers with references. You must have a complete understanding of
the situation (I believe my postings here have provided that) and a
ready proposal for a solution, we cannot fund research or education.

Thanks for your time.

Hi Tony,

the namespaces are defined in SOAP::Constants. Unfortunately they cannot
be overridden at run time, because perl's peep-hole optimizer inlines
constants.

However, the constants are not used directly by SOAP::Lite, but through
the following SOAP::Constants variables:

@SUPPORTED_ENCODING_STYLES
%XML_SCHEMAS
%XML_SCHEMA_OF
%SOAP_VERSIONS

To change all occurances, do the following:

BEGIN {
use SOAP::Lite

my $url_enc = "http://www.w3.org/2001/06/soap-encoding";
my $url_env = "http://www.w3.org/2001/06/soap-envelope";

push @SOAP::Constants::SUPPORTED_ENCODING_STYLES, $url_enc;

$SOAP::Constants::SOAP_VERSIONS{'1.2'}->{NS_ENC} = $url_enc;
$SOAP::Constants::SOAP_VERSIONS{'1.2'}->{NS_ENV} = $url_env;

$SOAP::Contants::XML_SCHEMAS{$url_enc} = 'SOAP::XMLSchemaSOAP1_2';
$SOAP::Contants::XML_SCHEMAS_OF{$url_enc} = 'XMLSchemaSOAP1_2';
}

This should change the (new) namespaces back to the old ones throughout
SOAP::Lite (untested...).

Note that SOAP::Constants variables are global - all your SOAP::Lite
instances in the current process will be affected (may be an issue under
mod_perl).

Martin


Am Samstag, den 18.10.2008, 22:57 +0000 schrieb Tony Gravagno:
> ...
> Thank you for the suggestion. This does change the header but the
> server is now complaining that the client is using the wrong SOAP
> version. There is a major difference between the headers sent before
> and after the upgrade.
>
> Before upgrade:
>
> <SOAP-ENV:Envelope
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENC="http://www.w3.org/2001/06/soap-encoding"
> xmlns:SOAP-ENV="http://www.w3.org/2001/06/soap-envelope"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> SOAP-ENV:encodingStyle="http://www.w3.org/2001/06/soap-encoding">
>
> After upgrade:
>
> <soap:Envelope
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:soapenc="http://www.w3.org/2003/05/soap-encoding"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding"
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
>
> It looks like the server isn't prepared for the v2003 schemas that
> come
> with SOAP::Lite v0.710 compared to v0.55 - and we cannot change the
> server. As mentioned in my original post, SOAP-ENC:Array is hardcoded
> into the transaction code and doesn't agree with the newer schema
> anyway.
>
> My current recommendation to the client is to downgrade SOAP::Lite
> and
> that probably involves a downgrade of Perl as well, and that may
> affect
> yet other dependencies. Better suggestions are welcome.
>
> I'm hoping for a quick solution here, but my client is willing to pay
> to get this resolved quickly if a solution needs to be more involved.
> So far I have emailed Paul Kulchenko to request compensated services
> but I have not received a response. I welcome emails from qualified
> developers with references. You must have a complete understanding of
> the situation (I believe my postings here have provided that) and a
> ready proposal for a solution, we cannot fund research or education.
>
> Thanks for your time.
>
>
>
>
>

I am trying to install SOAP-Lite 0.710.08 on Windows XP with Perl
v5.8.8 build 817 (Mar 20, 2006) and I am receiving the following error:

When running perl Makefile.PL:

Could not eval '
      package ExtUtils::MakeMake::_version;
      no strict;

      local $VERSION;
      $VERSION-undef; do {
           use version; $VERSION = qv('0.710.08');
      }; $VERSION
      ' in lib/SOAP/Lite.pm:  Can't locate version.pm in @INC (@INC
contains: D:/Perl/lib D:/Perl/site/lib .) at (eval 70) line 7, <FH>
line 22.
BEGIN failed--compilation aborted at (eval 70) line 7, <FH> line 22.
WARNING:  Setting VERSION via file 'lib/SOAP/Lite.pm' failed at
D:/Perl/lib/ExtUtils/MakeMaker.pm line 495

Note:  When I install it under Perl v5.8.8 build 824 (Sept 3, 2008),
it works successfully.  Unfortunately, the production servers are
still under Perl v5.8.8 build 817 so I cannot just switch to build 824.

Has anyone run into this problem?  If so, can it be resolved under
build 817?

Thanks

dear all,

i have 2 case that realy need your help. but if you only answer 1 of
those care really thanks fully to you.

First case:

i want to establish the connection with my customer using MM7 (
anybody know? ), the things that i know about MM& seven is Server
Client communication whit SOAP and HTTP as protocol.
since i new in Perl and SOAP, so i really need your help.

1. the customer send me SOAP XML whit attachment ( plain/text ) to me
    and this is the example of SOAP envelope :
=======================================================================
POST http://XXX.XXX.XXX.XXX:9999 HTTP/1.1
Host: XXX.XXX.XXX.XXX:9999
customer-id:ABC1234
x-fh-Connection-ID:3
Content-Type:multipart/related; boundary="fh-mms-multipart-boundary-0";
type="text/xml"; start="<cid-999999000000@5>"
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/soapenvelope.
xsd">
<soap-env:Header>
<TransactionID
soap-env:mustUnderstand="1"
xmlns="http://www.firsthop.com/specs/MM7-extended/MM7-extended-1-3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.firsthop.com/specs/MM7-extended/MM7-
extended-1-3/MM7-extended-1-3.xsd">
fh-transaction-id-12345678909
</TransactionID>
</soap-env:Header>
<soap-env:Body>
<DeliverReq
xmlns="http://www.firsthop.com/specs/MM7-extended/MM7-extended-1-3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.firsthop.com/specs/MM7-extended/MM7-
extended-1-3/MM7-extended-1-3.xsd">
<MM7Version>5.5.0-extended</MM7Version>
<LinkedID>routerSMSNode1@cs01nfhq:57999</LinkedID>
<Sender><Number>+6283809000XXX</Number></Sender>
<Recipients><To><ShortCode>9999</ShortCode></To></Recipients>
<TimeStamp>2007-12-26T03:15:46-00:00</TimeStamp>
<Content allowAdaptations="true" href="<00005DC71A4C0019@...>"
type="SMS"/>
</DeliverReq>
</soap-env:Body>
</soap-env:Envelope>
======================================================================

    and the attachment is "Hello World".
    how can i get the value of "customer-id" "TransactionID"
    "MM7Version" "LinkedID" "Number" "ShortCode" "TimeStamp"
    and the attachment "Hello World".

2. can you explain to me about [ allowAdaptations="true" ] and how to
    replay [ soap-env:mustUnderstand="1" ] ?

Second case

Please help me to create simple ( yes, just simple will help me a lot
)Server script and client script.

and this is the situation :
1. i need a sample script to deliver SOAP envelop with the attachment
    a text string like " Hello World ".
2. i need a sample script to print out the envelope and catch the
    value in the envelope ( header and body ) and in the attachment,
    and give the response back.

once again i really thanks fully to you if you can answer my problem.
right now i still learn the Perl and SOAP.

Thx

Regards

I've never done any SOAP or WSDL stuff before (although I am familiar
with various RPC standards).  I was reading through some of the
documentation for SOAP::Lite and I was wondering if someone can glance
at a WSDL url and determine if SOAP::Lite's schema functionality will
support it:

https://www.istreamdeposit.com/services/FileLoaderService0711?wsdl

From what I can tell of the service's documentation I'm going to need
to create container objects and the like.

I ran the stub generator and it didn't complain but honestly I'm just
now researching SOAP/WSDL so I'm not really even sure what I'm looking
at just yet :)

Any input on that url is much appreciated.

I exposed a method using WebServices in Java (with WSDL) and I don't
know how to call from SOAP:Lite. This method have only a parameter
with this object structure:

<xs:complexType name="note">
   <xs:sequence>
     <xs:element minOccurs="0" name="date" type="xs:dateTime"/>
     <xs:element minOccurs="0" name="text" type="xs:string"/>
     <xs:element minOccurs="0" name="user" type="xs:string"/>
   </xs:sequence>
</xs:complexType>

The XML generated by SOAP:Lite is always with this parameter empty:

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:tns="http://endpoint.ws.openkm.git.es/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><tns:complex><arg0
xsi:nil="true" xsi:type="tns:note" /><text
xsi:type="xsd:int">333</text><user
xsi:type="xsd:int">111</user></tns:complex></soap:Body></soap:Envelope>

Does anyone have any examples of how to call a web service in Perl
without using the SOAP:Lite package or any other third-party package?
I realize it may be more cumbersome, but due to restraints with our
current server environment, this is an avenue we need to explore.  Any
help would be greatly appreciated.

Thanks

For anyone watching this thread, the issue was resolved for the most
part with the code that Martin provided. Just add a semi-colon to the
end of the using statement.  :)  Martin, thank you very much!

We also asked Paul Kulchenko for for-fee consultation and appreciate
his assistance as well.

--- sandeep sahane wrote:
> As per my understanding of SOAP::Lite package, it is
> an wonderful package I have seen till the date. I went
> through the supports it provides and found that its
> the package that we are looking for our project.

I hope I don't offend anyone using SOAP::Lite but I'd to offer some
personal observations.

We were asked by a client over 5 years ago to provide a SOAP::Lite
client to correspond to a SOAP::Lite service to which they needed to
connect.  My first question was "why does it need to be SOAP::Lite" and
the answer was that the SOAP::Lite server required a SOAP::Lite
client.  This sort of defeats the whole purpose of web services
compared to proprietary protocols, but the client had a need so we
satisfied it.  Observation 1: Lack of compatibility is an issue that
should have affected the choice of this tool.

The version back then was 0.55.  We were recently asked to upgrade the
client server, and long story made short, getting the latest v0.71 to
work with the existing 0.55 client was beyond my skills. Advice
provided here and by Paul Kulchenko, author of SOAP::Lite led to a
solution.

Observation 2: In 5 years the software has moved from 0.55 to 0.71,
just 16 builds, not even a "release".
Observation 3: There has never been a v1.0 release.
Observation 4: To get an issue resolved I needed to commission the guy
who wrote the software, someone who is gainfully employed and doesn't
support this software for a living.
Observation 5: Perl seems to be a dead or dying language, surpassed by
PHP, Ruby, .NET, Java, and a resurgence in JavaScript.  I lost a bet
there because I thought the winner was going to be Perl, but the world
moves on, and most Open Source software you see today is C, Java, and
PHP - not Perl.

So given these observations, and people are quite welcome to disagree
with my conclusions, I personally believe SOAP::Lite is _not_ a
suitable tool for new development.

Please don't confuse that with "dislike".  The software works for the
most part, but if it doesn't, then you're in trouble.  As mentioned
above, I've had a number of exchanges with Paul and he is very
professional and was very gracious in offering his assistance.  I have
nothing but good things to say about him and the core of the software.

But as time moves on, some commercial and open source products die, and
it looks like this is one of them.  So it's time to move on beyond them.

What are alternatives?  .NET easily supports Web Services, client and
server, in many ways.  For PHP there is NuSOAP, though there are many
issues with that too.  I recommend looking at that (SourceForge) but as
with Perl and SOAP::Lite, be prepared to get into the NuSOAP code
yourself because it looks to me like that project isn't well maintained
and the author (or the one guy who supports it now) is getting burned
out.

If you're going to do web services, do not choose Open Source Software
purely because OSS is Free - as in "no cost".  Choose OSS because you
know that you can take responsibility for building on the source and
improving the code.  Do not choose OSS, especially an old package like
SOAP::Lite if you do not have skills with Perl or web services and you
know you're going to need to rely on other people for help.  That's
asking for trouble.

Some OSS tools are high quality and have large and lively developer
teams.  With those tools you have more freedom to take without giving,
but of course you should always give where possible anyway.  The "Free"
part of OSS is not "free beer" or "free lunch", it means you are free
to see the code and improve on it.  That will take lots of your time
with SOAP::Lite.  If you have time to learn, then yes, it is also no-
cost software.  If you do not, then like myself, you should be willing
to pay people to work on the code for you.  For this package, I was
lucky that there was anyone qualified to work on the software.

So, my recommendation is to find software that you can maintain
yourself, that has a large development team who can maintain it for
you, and be prepared to pay people for their services when you get
stuck - especially with this package.

I hope that helps.

Hi i am using wsdl the contains of it is
<complexType name="ArrayOfTarget">
         <complexContent>
         <restriction base="soapenc:Array">
                 <attribute ref="soapenc:arrayType"
wsdl:arrayType="impl:Target[]"/>
         </restriction>
         </complexContent>
  </complexType>

<complexType name="Target">
         <sequence>
                 <element name="nas-ip" nillable="true" type="xsd:string"/>
                 <element name="port" nillable="true" type="xsd:long"/>
                 <element name="secret" nillable="true" type="xsd:string"/>
         </sequence>
</complexType>

<complexType name="ArrayOfRadiusattributes">
         <complexContent>
         <restriction base="soapenc:Array">
                 <attribute ref="soapenc:arrayType"
wsdl:arrayType="impl:Radiusattributes[]"/>
         </restriction>
         </complexContent>
</complexType>

<complexType name="Radiusattributes">
         <sequence>
                 <element name="RadiusattributeName" nillable="true"
type="xsd:string"/>
                 <element name="RadiusattributeValue" nillable="true"
type="xsd:string"/>
                 <element name="RadiusattributeFormat" nillable="true"
type="xsd:long"/>
         </sequence>
</complexType>

<complexType name="ChangeProfile">
         <sequence>
                 <element name="TargetData" nillable="false"
type="impl:ArrayOfTarget"/>
                 <element name="RadiusattributesData" nillable="false"
type="impl:ArrayOfRadiusattributes"/>
                 <element name="Command" nillable="false"
type="xsd:string"/>
         </sequence>
</complexType>

<complexType name="ChangeProfileResponse">
         <sequence>
                 <element name="iResponseCode" nillable="false"
type="xsd:long"/>
         </sequence>
</complexType>
</schema>


My soap server is in c/c++,I want to send the vales of nsa-ip port to
server ,

Hello all,

I am writing web service. I want to use soap lite for the client side
and for the server I am using jax-ws. I want to handle errors using
exceptions. My server side WS throws javax.xml.ws.WebServiceException.
My problem is no matter what I do, I can't catch the exception and get
the exception string out.

My client code:
#!/usr/bin/perl -w
use strict;

use SOAP::Lite
         on_fault => sub { my($soap, $res) = @_;
       die ref $res ? $res->faultdetail : $soap->transport->status, "\n";
     };

my $res = SOAP::Lite
         ->service('http://localhost:8084/casi/CWS?wsdl');

my $var = SOAP::Data->type('string');
$var->name('p1');
$var->value('my p1');

eval {
         print "before call\n";
         my $result = $client->test1($var);
         print $result. '\n';;
};
if ($@) {
         print "$@\n";
}

Any ideas?