I refinanced my home loan at an incredible interest rate; this saved me 500.00
this month alone. All the information is right here. 
http://tpbaj.com/i/LzIvaW5kZXgvd2F6ZWUvZ2h0anRzYmJqcnNuZ2l3c2li take 30 seconds
and fill out this free form to save money

Hi,

I am getting this error now sure what is wrong.


perl stubmaker.pl http://localhost:7001/test4/test.jws?WSDL
Accessing...
SOAP::Schema->schema has been deprecated. Please use
SOAP::Schema->schema_url instead. at
/usr/local/share/perl/5.8.7/SOAP/Lite.pm line 2803.
Writing...
./test.pm exists, skipped...

Thanks
Arun

I had to spent many hours to find how to access document/literal
web services using SOAP:Lite. Cant believe SOAP::Lite folks didnt
have time to write a simpleexample. Too bad... anyway.. i kind a
figured it out and it is working well.


Before you start you would need the following perl modules

SOAP::Lite (SOAP-Lite-0.60)
XML::Parser(XML-Parser-2.34)

NOTE: Install the SOAP::Lite using CPAN will automaticall install
the XML::Parser. If it doesnt do that then install the XML::Parser
module.


SOAP call input (To the web service) from the perl client.
This is the output of the per client to the web services.
=========================================================
----- start----
<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:Body>

<lookupTicketRequest xmlns="urn:zzz:xml:ns:pmp-1.0">

<ticketNumber>1234</ticketNumber>

</lookupTicketRequest>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>
---- end----

Here the URL is "urn:zzz:xml:ns:pmp-1.0"

NOTE: MAKE SURE THE URN IS CORRECT BEFORE YOU CALL. IF THE URN IS
NOT CORRECT YOUR THE STRUCTURE OF THE SOAP DOCUMENT WILL BECOME
INCORRECT.




SOAP call output (From the web service)
This is the output of the web service after processing the request.
===================================================
----- start ----
<SOAP-ENV:Envelope
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:Body>

<ns:lookupTicketResponse xmlns:ns="urn:zzz:xml:ns:pmp-1.0">

<ns:result code="100">

<ns:message>Successfull</ns:message>

</ns:result>

</ns:lookupTicketResponse>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>
----- end ----


===========================================
PERL CODE THAT DOES THE TRICK
===========================================

This Perl code uses SOAP::Lite to access a document/literal web
service.
The web service is hosted in BEA.


---- program start ----------
use strict;
use SOAP::Lite;

# IMPORTANT
#
# uri  "urn:zzz:xml:ns:pmp-1.0" is the key to this document/litral
type. Make
# sure you have the correct uri.


my $soap = SOAP::Lite
     -> uri('urn:zzz:xml:ns:pmp-1.0')
     -> on_action( sub { return
'"http://localhost:7001/WebServices/pmp10.jws/lookupTicketRequest"' }
)
     -> proxy('http://localhost:7001/WebServices/pmp10.jws');

#Set the operation to call
my $method = SOAP::Data->name('lookupTicketRequest')
                ->attr({xmlns => 'urn:zzz:xml:ns:pmp-1.0'});

#Set data elements
my $query = SOAP::Data->name(ticketNumber => '123456');

my $result = SOAP::SOM->new;

#Call the service
$result = $soap->call($method => $query);

unless ($result->fault) {

  #Get 'result' element of element 'lookupTicketResponse'
  my $result1 = $result->valueof('//lookupTicketResponse/result');

  #Get the 'code' attribute of element 'result'
  print "Code =
".$result->dataof('//lookupTicketResponse/result')
->attr->{'code'}."\n";

  #Get the element 'message' of element 'result'
  print "Message =
".$result->valueof('//lookupTicketResponse/result/message');

  print "\n";

} else {
      print join ', ',
          $result->faultcode,
          $result->faultstring,
          $result->faultdetail;
}
---- end program ------------

========================
OUTPUT OF THIS PROGRAM
========================

Code =100
Message =Successfull

I had to spent many hours to find how to access document/literal
web services using SOAP:Lite. Cant believe SOAP::Lite folks didnt
have time to write a simple example. Too bad... anyway.. i kind a
figured it out and it is working well.


Before you start you would need the following perl modules

SOAP::Lite (SOAP-Lite-0.60)
XML::Parser(XML-Parser-2.34)

NOTE: Install the SOAP::Lite using CPAN will automaticall install
the XML::Parser. If it doesnt do that then install the XML::Parser
module.


SOAP call input (To the web service) from the perl client.
This is the output of the per client to the web services.
=========================================================
----- start----
<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:Body>

<lookupTicketRequest xmlns="urn:zzz:xml:ns:pmp-1.0">

<ticketNumber>1234</ticketNumber>

</lookupTicketRequest>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>
---- end----

Here the URL is "urn:zzz:xml:ns:pmp-1.0"

NOTE: MAKE SURE THE URN IS CORRECT BEFORE YOU CALL. IF THE URN IS
NOT CORRECT YOUR THE STRUCTURE OF THE SOAP DOCUMENT WILL BECOME
INCORRECT.




SOAP call output (From the web service)
This is the output of the web service after processing the request.
===================================================
----- start ----
<SOAP-ENV:Envelope
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:Body>

<ns:lookupTicketResponse xmlns:ns="urn:zzz:xml:ns:pmp-1.0">

<ns:result code="100">

<ns:message>Successfull</ns:message>

</ns:result>

</ns:lookupTicketResponse>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>
----- end ----


===========================================
PERL CODE THAT DOES THE TRICK
===========================================

This Perl code uses SOAP::Lite to access a document/literal web service.
The web service is hosted in BEA.


---- program start ----------
use strict;
use SOAP::Lite;

# IMPORTANT
#
# uri  "urn:zzz:xml:ns:pmp-1.0" is the key to this document/litral
type. Make
# sure you have the correct uri.


my $soap = SOAP::Lite
     -> uri('urn:zzz:xml:ns:pmp-1.0')
     -> on_action( sub { return
'"http://localhost:7001/WebServices/pmp10.jws/lookupTicketRequest"' } )
     -> proxy('http://localhost:7001/WebServices/pmp10.jws');

#Set the operation to call
my $method = SOAP::Data->name('lookupTicketRequest')
                ->attr({xmlns => 'urn:zzz:xml:ns:pmp-1.0'});

#Set data elements
my $query = SOAP::Data->name(ticketNumber => '123456');

my $result = SOAP::SOM->new;

#Call the service
$result = $soap->call($method => $query);

unless ($result->fault) {

  #Get 'result' element of element 'lookupTicketResponse'
  my $result1 = $result->valueof('//lookupTicketResponse/result');

  #Get the 'code' attribute of element 'result'
  print "Code =
".$result->dataof('//lookupTicketResponse/result')->attr->{'code'}."\n";

  #Get the element 'message' of element 'result'
  print "Message =
".$result->valueof('//lookupTicketResponse/result/message');

  print "\n";

} else {
      print join ', ',
          $result->faultcode,
          $result->faultstring,
          $result->faultdetail;
}
---- end program ------------

========================
OUTPUT OF THIS PROGRAM
========================

Code =100
Message =Successfull

I had to spent many hours to find how to access document/literal
web services using SOAP:Lite. Cant believe SOAP::Lite folks didnt
have time to write a simple example. Too bad... anyway.. i kind a
figured it out and it is working well.


Before you start you would need the following perl modules

SOAP::Lite (SOAP-Lite-0.60)
XML::Parser(XML-Parser-2.34)

NOTE: Install the SOAP::Lite using CPAN will automaticall install
the XML::Parser. If it doesnt do that then install the XML::Parser
module.


SOAP call input (To the web service) from the perl client.
This is the output of the per client to the web services.
=========================================================
----- start----
<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:Body>

<lookupTicketRequest xmlns="urn:zzz:xml:ns:pmp-1.0">

<ticketNumber>1234</ticketNumber>

</lookupTicketRequest>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>
---- end----

Here the URL is "urn:zzz:xml:ns:pmp-1.0"

NOTE: MAKE SURE THE URN IS CORRECT BEFORE YOU CALL. IF THE URN IS
NOT CORRECT YOUR THE STRUCTURE OF THE SOAP DOCUMENT WILL BECOME
INCORRECT.




SOAP call output (From the web service)
This is the output of the web service after processing the request.
===================================================
----- start ----
<SOAP-ENV:Envelope
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:Body>

<ns:lookupTicketResponse xmlns:ns="urn:zzz:xml:ns:pmp-1.0">

<ns:result code="100">

<ns:message>Successfull</ns:message>

</ns:result>

</ns:lookupTicketResponse>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>
----- end ----


===========================================
PERL CODE THAT DOES THE TRICK
===========================================

This Perl code uses SOAP::Lite to access a document/literal web service.
The web service is hosted in BEA.


---- program start ----------
use strict;
use SOAP::Lite;

# IMPORTANT
#
# uri  "urn:zzz:xml:ns:pmp-1.0" is the key to this document/litral
type. Make
# sure you have the correct uri.


my $soap = SOAP::Lite
     -> uri('urn:zzz:xml:ns:pmp-1.0')
     -> on_action( sub { return
'"http://localhost:7001/WebServices/pmp10.jws/lookupTicketRequest"' } )
     -> proxy('http://localhost:7001/WebServices/pmp10.jws');

#Set the operation to call
my $method = SOAP::Data->name('lookupTicketRequest')
                ->attr({xmlns => 'urn:zzz:xml:ns:pmp-1.0'});

#Set data elements
my $query = SOAP::Data->name(ticketNumber => '123456');

my $result = SOAP::SOM->new;

#Call the service
$result = $soap->call($method => $query);

unless ($result->fault) {

  #Get 'result' element of element 'lookupTicketResponse'
  my $result1 = $result->valueof('//lookupTicketResponse/result');

  #Get the 'code' attribute of element 'result'
  print "Code =
".$result->dataof('//lookupTicketResponse/result')->attr->{'code'}."\n";

  #Get the element 'message' of element 'result'
  print "Message =
".$result->valueof('//lookupTicketResponse/result/message');

  print "\n";

} else {
      print join ', ',
          $result->faultcode,
          $result->faultstring,
          $result->faultdetail;
}
---- end program ------------

========================
OUTPUT OF THIS PROGRAM
========================

Code =100
Message =Successfull

--- arun9a <arunr2002@...> wrote:

> I had to spent many hours to find how to access
> document/literal
> web services using SOAP:Lite. Cant believe
> SOAP::Lite folks didnt
> have time to write a simpleexample.

I have an example client and server I can email to
anyone who wants it. It has six examples from simple
to complex (including a client call using a WSDL).

I found SOAP::Lite *way* too complex due to its own
mixed bag of syntaxes. My examples aren't rocket
science. And they don't explain the 18 different ways
you can do something in SOAP::Lite (as if that's a
badge of honor?). It's just six examples to get a
person up and running without banging their head
against the wall.

Mark



____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com

Yes, that seems like a deserialization issue.  SOAP::Lite
expects:

   <list xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:any-type[4]">

instead of

   <list>

in order to create an array of elements.

You may want to check the list archive of the last couple of
weeks for related mails.

Cheers, Andre.


Quoting [Jens Puruckherr] (Jun 27 2005):
> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
> To: soaplite@yahoogroups.com
> From: "Jens Puruckherr" <jpuruckherr@...>
> Mailing-List: list soaplite@yahoogroups.com; contact
soaplite-owner@yahoogroups.com
> Date: Mon, 27 Jun 2005 10:45:23 +0200
> Subject: [soaplite] transport of ready xml
>
> Hi,
>
> i want to send a ready XML via SOAP to my server.
> (client, server and called class are only a minimlaistic testsystem,
> without any dataprozessing)
> I use:
>
> my $soapdata = SOAP::Data->type(xml=>$myxml);
>
> to pass it to the call.
>
> But on the server I didnt' get back the original values.
> My XML-source looks like:
>
> <liste>
> <test nr="1">
>         <item>xxx</item>
>         <wert>yyy</wert>
> </test>
> <test nr="2">
>         <item>aaa</item>
>         <wert>bbb</wert>
> </test>
> <test nr="3">
>         <item>ccc</item>
>         <wert>ddd</wert>
> </test>
> <test nr="4">
>         <item>eee</item>
>         <wert>fff</wert>
> </test>
> </liste>
>
> The called class at the server only dumps all parameters(@_).
> I get just:
>
> $VAR1 = [
>           'myClass',
>           {
>             'test' => {
>                       'wert' => 'fff',
>                       'item' => 'eee'
>                     }
>           }
>         ];
>
>
> So the first tree entries from the xml are lost.
> How can I get back all entires from my xml?
> Is it a problem of the serializer or the deserializer?
> How may I fix it, so that it's working  for different xmls?
>
>
>
>
> Mit freundlichen Grüßen
>
> Jens Puruckherr
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>



--
+-----------------------------------------------------------------+
| Andre Merzky                      | phon: +31 - 20 - 598 - 7759 |
| Vrije Universiteit Amsterdam (VU) | fax : +31 - 20 - 598 - 7653 |
| Dept. of Computer Science         | mail: merzky@...       |
| De Boelelaan 1083a                | www:  http://www.merzky.net |
| 1081 HV Amsterdam, Netherlands    |                             |
+-----------------------------------------------------------------+

Jens,
you need to navigate through the SOAP body, see the section
ACCESSING HEADERS AND ENVELOPE ON SERVER SIDE in the docs.
Something like this will get you going

sub hello {
     my $som = pop @_;

     my $liste = $som->match('//liste');

     for my $t ($som->valueof('test')) {
         print "$t->{wert} $t->{item}\n";
     }

}

Duncan


At 2005-07-04, 15:28:02 you wrote:

>Yes, that seems like a deserialization issue.  SOAP::Lite
>expects:
>
>  <list xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:any-type[4]">
>
>instead of
>
>  <list>
>
>in order to create an array of elements.
>
>You may want to check the list archive of the last couple of
>weeks for related mails.
>
>Cheers, Andre.

>
>Quoting [Jens Puruckherr] (Jun 27 2005):
>> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
>> To: soaplite@yahoogroups.com
>> From: "Jens Puruckherr" <jpuruckherr@...>
>> Mailing-List: list soaplite@yahoogroups.com; contact
soaplite-owner@yahoogroups.com
>> Date: Mon, 27 Jun 2005 10:45:23 +0200
>> Subject: [soaplite] transport of ready xml
>>
>> Hi,
>>
>> i want to send a ready XML via SOAP to my server.
>> (client, server and called class are only a minimlaistic testsystem,
>> without any dataprozessing)
>> I use:
>>
>> my $soapdata = SOAP::Data->type(xml=>$myxml);
>>
>> to pass it to the call.
>>
>> But on the server I didnt' get back the original values.
>> My XML-source looks like:
>>
>> <liste>
>> <test nr="1">
>>         <item>xxx</item>
>>         <wert>yyy</wert>
>> </test>
>> <test nr="2">
>>         <item>aaa</item>
>>         <wert>bbb</wert>
>> </test>
>> <test nr="3">
>>         <item>ccc</item>
>>         <wert>ddd</wert>
>> </test>
>> <test nr="4">
>>         <item>eee</item>
>>         <wert>fff</wert>
>> </test>
>> </liste>
>>
>> The called class at the server only dumps all parameters(@_).
>> I get just:
>>
>> $VAR1 = [
>>           'myClass',
>>           {
>>             'test' => {
>>                       'wert' => 'fff',
>>                       'item' => 'eee'
>>                     }
>>           }
>>         ];
>>
>>
>> So the first tree entries from the xml are lost.
>> How can I get back all entires from my xml?
>> Is it a problem of the serializer or the deserializer?
>> How may I fix it, so that it's working  for different xmls?
>>
>>
>>
>>
>> Mit freundlichen Grüßen
>>
>> Jens Puruckherr

Hi,

I've got a simple webservice that requires a SOAP request that looks
something like this:

---

SOAPAction: "http://scm/doWinBuild"

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
     <doWinBuild xmlns="http://scm">
       <projectName>string</projectName>
       <sourceURL>string</sourceURL>
       <buildTool>string</buildTool>
       <buildParams>string</buildParams>
     </doWinBuild>
   </soap:Body>
</soap:Envelope>

---

After much tweaking, I've finally got my SOAP::Lite client producing
similar XML:

---

<?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:doWinBuild xmlns:namesp1="http://scm">
       <projectName xsi:type="xsd:string">myproject</projectName>
       <sourceURL xsi:type="xsd:string">mysource</sourceURL>
       <buildTool xsi:type="xsd:string">mybuildtool</buildTool>
       <buildParams xsi:type="xsd:string">mybuildparams</buildParams>
     </namesp1:doWinBuild>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

---

I've also checked that the SOAPAction is correct. However, when this
hits the C# web service, it is not interpreted correctly: although
the correct method (doWinBuild) is called, all the parameter
variables (projectName, sourceURL etc.) are null.

This is clearly because of some fault in the request, but I don't see
anything obvious to explain it (of course, my XML is subpar, so...)

Does anyone have any suggestions? Thanks in advance.

Does SOAP::Lite support Complex WSDL's.

Eg: the request in wsdl is defined as:

  <s:complexType name="Request">
   <s:sequence>
   <s:element minOccurs="0" maxOccurs="1" name="Header"
type="tns:Header" />
   <s:element minOccurs="1" maxOccurs="1" name="Id" type="s:int" />
    </s:sequence>
  </s:complexType>

<s:complexType name="Header">
   <s:sequence>
   <s:element minOccurs="0" maxOccurs="1" name="password"
type="s:string" />
   <s:element minOccurs="0" maxOccurs="1" name="name" type="s:string" />
</s:sequence>

How would I use SOAP::Lite to pass these parameters. Any help would be
appreciated
Ganesh

That is not so much a WSDL as it is a schema. But that schema is easily
supported. Suppose that "Request" is the schema for a request message's
input. Let's say that request message is called "do_something." Then the
SOAP::Lite call look like this:

my $som = SOAP::Lite->service("URL to
WSDL")->do_something("<password>","<name>");

gkupps wrote:

> Does SOAP::Lite support Complex WSDL's.
>
> Eg: the request in wsdl is defined as:
>
> <s:complexType name="Request">
>   <s:sequence>
>   <s:element minOccurs="0" maxOccurs="1" name="Header"
> type="tns:Header" />
>   <s:element minOccurs="1" maxOccurs="1" name="Id" type="s:int" />
>    </s:sequence>
> </s:complexType>
>
> <s:complexType name="Header">
>   <s:sequence>
>   <s:element minOccurs="0" maxOccurs="1" name="password"
> type="s:string" />
>   <s:element minOccurs="0" maxOccurs="1" name="name" type="s:string" />
> </s:sequence>
>
> How would I use SOAP::Lite to pass these parameters. Any help would be
> appreciated
> Ganesh
>
>
>
>
> SPONSORED LINKS
> Communication and networking
>
<http://groups.yahoo.com/gads?t=ms&k=Communication+and+networking&w1=Communicati\
on+and+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protoco\
l&w5=Wireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=zrT70VhU2\
wpMoVKtjfbJBg>
>
<http://groups.yahoo.com/gads?t=ms&k=Communication+and+networking&w1=Communicati\
on+and+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protoco\
l&w5=Wireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=zrT70VhU2\
wpMoVKtjfbJBg>
>  Protocol
>
<http://groups.yahoo.com/gads?t=ms&k=Protocol&w1=Communication+and+networking&w2\
=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=Wireless+applic\
ation+protocol&w6=Protocol+analysis&c=6&s=162&.sig=9DpeRuEKwcfS-z8yair2iA>
>
<http://groups.yahoo.com/gads?t=ms&k=Protocol&w1=Communication+and+networking&w2\
=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=Wireless+applic\
ation+protocol&w6=Protocol+analysis&c=6&s=162&.sig=9DpeRuEKwcfS-z8yair2iA>
>  Communication protocol
>
<http://groups.yahoo.com/gads?t=ms&k=Communication+protocol&w1=Communication+and\
+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=W\
ireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=IxDbscIJuIzgwbH\
zrhlNBQ>
>
<http://groups.yahoo.com/gads?t=ms&k=Communication+protocol&w1=Communication+and\
+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=W\
ireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=IxDbscIJuIzgwbH\
zrhlNBQ>
>
> File transfer protocol
>
<http://groups.yahoo.com/gads?t=ms&k=File+transfer+protocol&w1=Communication+and\
+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=W\
ireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=JS4C6y0UwfO-UvB\
ekXd64A>
>
<http://groups.yahoo.com/gads?t=ms&k=File+transfer+protocol&w1=Communication+and\
+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=W\
ireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=JS4C6y0UwfO-UvB\
ekXd64A>
>  Wireless application protocol
>
<http://groups.yahoo.com/gads?t=ms&k=Wireless+application+protocol&w1=Communicat\
ion+and+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protoc\
ol&w5=Wireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=-S5mcKf2\
joo019aCXPzHDA>
>
<http://groups.yahoo.com/gads?t=ms&k=Wireless+application+protocol&w1=Communicat\
ion+and+networking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protoc\
ol&w5=Wireless+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=-S5mcKf2\
joo019aCXPzHDA>
>  Protocol analysis
>
<http://groups.yahoo.com/gads?t=ms&k=Protocol+analysis&w1=Communication+and+netw\
orking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=Wirele\
ss+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=FnT9ajWQieMRBr-xnL4Q\
Mw>
>
<http://groups.yahoo.com/gads?t=ms&k=Protocol+analysis&w1=Communication+and+netw\
orking&w2=Protocol&w3=Communication+protocol&w4=File+transfer+protocol&w5=Wirele\
ss+application+protocol&w6=Protocol+analysis&c=6&s=162&.sig=FnT9ajWQieMRBr-xnL4Q\
Mw>
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "soaplite
>       <http://groups.yahoo.com/group/soaplite>" on the web.
>
>     *  To unsubscribe from this group, send an email to:
>        soaplite-unsubscribe@yahoogroups.com
>       <mailto:soaplite-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>

Send instant messages to your online friends http://uk.messenger.yahoo.com

Hi SOAP::Lite members,

I have been using a soap lite based service for the last three
years at my company's website without any problems. Yesterday, when I
tried the service (after a few month's gap),  I observed the follwing:

Calls on remote objects using object names work correctly, but calls
made using object references have suddenly stopped working.

So, this works:

Class::method();

But this does not:

$cref = new Class(); # this line works
$cref->method(); # this line produces the following error:

# faultcode: SOAP-ENV:Client
# faultstring: Denied access to method (setValue) in class (TestSOAP)
#at /usr/lib/perl5/site_perl/5.6.1/SOAP/Lite.pm line 2267.

Here is the more relevent info about my setup:

Client: 'SOAP::Lite/Perl/0.51',
SOAPServer: 'SOAP::Lite/Perl/0.60'
SERVER_SOFTWARE : 'Apache/1.3.33 (Unix) mod_auth_passthrough/1.8
mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635
mod_ssl/2.8.22 OpenSSL/0.9.6b PHP-CGI/0.1b',

I have reduced the problem to a testcase and included the following
with my post:

1. test_server.pl
2. TestSOAP.pm
3. test_client.pl
4. Environment variables as seen by the server

Since my code (either on client or server) did not change, I suspect
that this is caused by some change in the environment at
my ISP's set up. Unfortunately, I can not access the httpd.conf file.
Any pointers about what I should be looking at or why this might be
happening would be very much appreciated. I searched through the
archives but could not find anything that helped.

Thanks,
Jiten

#==================== test_server.pl =========================
my $soap_path = "/home/MY_COMPANY/www/cgi-bin/service/lib";
require SOAP::Transport::HTTP;

SOAP::Transport::HTTP::CGI
     -> dispatch_to($soap_path)
     -> handle;

#===================== TestSOAP.pm ===========================
package TestSOAP;

sub new {
    bless {}, shift;
};

sub getValue
{
     my $self = shift;
     return $self->{Val};
}

sub setValue
{
     my $self = shift;
     return $self->{Val} = shift;
}

sub getEnv
{
     my $env = {};
     %$env = %ENV;
     return $env;
}

1;

#==================== test_client.pl =========================

use Data::Dumper;
use SOAP::Lite +trace => all;
use SOAP::Lite +autodispatch =>
    uri=>"TestSOAP",
     proxy=>"http://www.MY_COMPANY.com/cgi-
bin/service/bin/test_server.pl";
     on_fault=>\&handle_soap_fault;

# demonstrate that calls made without ref work correctly
# this block works and prints out server-side env
my $senv = TestSOAP::getEnv();
print Dumper $senv;

# the following block used to print out "Good"
# Now the first line works, the second line gives the following error
# faultcode: SOAP-ENV:Client
# faultstring: Denied access to method (setValue) in class (TestSOAP)
#at /usr/lib/perl5/site_perl/5.6.1/SOAP/Lite.pm line 2267.

my $ts = new TestSOAP();
$ts->setValue("Good");
print $ts->getValue(); print "\n";

# end of main

sub handle_soap_fault
{
     my($soap, $res) = @_;
     my $content = $soap->{'_call'}{'_content'};
     my $ehash = ${$content}[$#{$content}];
     my $fc = $ehash->{'Body'}->{'Fault'}->{'faultcode'};
     my $fs = $ehash->{'Body'}->{'Fault'}->{'faultstring'};
     print "faultcode: $fc\n";
     print "faultstring: $fs\n";
     die ref $res ? $res->faultdetail : $soap->transport->status, "\n";
}



================= environment variables on server ===================

$VAR1 = {
           'QUERY_STRING' => '',
           'SERVER_ADDR' => '66.78.26.16',
           'CONTENT_TYPE' => 'text/xml; charset=utf-8',
           'SERVER_PROTOCOL' => 'HTTP/1.0',
           'REMOTE_PORT' => '4332',
           'HTTP_ACCEPT' => 'text/xml, multipart/*',
           'HTTP_USER_AGENT' => 'SOAP::Lite/Perl/0.51',
           'HTTP_HOST' => 'www.MY_COMPANY.com',
           'GATEWAY_INTERFACE' => 'CGI/1.1',
           'SERVER_ADMIN' => 'webmaster@MY_COMPANY.com',
           'SERVER_SOFTWARE' => 'Apache/1.3.33 (Unix)
mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4
FrontPage/5.0.2.2635 mod_ssl/2.8.22 OpenSSL/0.9.6b PHP-CGI/0.1b',
           'REMOTE_ADDR' => '67.123.173.118',
           'SCRIPT_NAME' => '/cgi-bin/service/bin/test_server.pl',
           'SERVER_NAME' => 'www.MY_COMPANY.com',
           'DOCUMENT_ROOT' => '/home/MY_COMPANY/public_html',
           'REQUEST_URI' => '/cgi-bin/service/bin/test_server.pl',
           'HTTP_SOAPACTION' => '"/TestSOAP#getEnv"',
           'SCRIPT_FILENAME' => '/home/MY_COMPANY/public_html/cgi-
bin/service/bin/t
est_server.pl',
           'REQUEST_METHOD' => 'POST',
           'CONTENT_LENGTH' => '435',
           'PATH' => '/usr/local/bin:/usr/bin:/bin',
           'SERVER_PORT' => '80'
         };

Hi All

I am trying to invoke a method using SOAP Lite by providing the
service parameter as follows:

use SOAP::Lite +autodispatch =>
service => 'https://ccuapi.xyz.com';

I am getting a message which says :

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

Does anybody have an idea, what this means and what needs to be done
to get rid of this problem?

Appreciate the help provided.

Thanks
Rajit

The URL passed to $soap->service() MUST resolve to a WSDL file. If you
need to point SOAP::Lite at the serice's URL,then use the proxy() method.

Rajit wrote:

> Hi All
>
> I am trying to invoke a method using SOAP Lite by providing the
> service parameter as follows:
>
> use SOAP::Lite +autodispatch =>
> service => 'https://ccuapi.xyz.com'; <https://ccuapi.xyz.com%27;>
>
> I am getting a message which says :
>
> "A service address has not been specified either by using
> SOAP::Lite->proxy() or a service description)"
>
> Does anybody have an idea, what this means and what needs to be done
> to get rid of this problem?
>
> Appreciate the help provided.
>
> Thanks
> Rajit
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "soaplite
>       <http://groups.yahoo.com/group/soaplite>" on the web.
>
>     *  To unsubscribe from this group, send an email to:
>        soaplite-unsubscribe@yahoogroups.com
>       <mailto:soaplite-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>

Hi all,
I have implemented a webservice with Java Axis and would like to offer
my users a perl client, too. Some other people asked already questions
about serializing java objects etc. on this list but they didn't get
an answer.

I have just ONE specific question about creating/sending a SOAP/Java
Object back to the server. Hopefully THIS question will be answered.

I'm using SOAP::Lite version 0.65 Beta 6 and was quite impressed by
its functionality and its easy usage.

I tried two ways of creating out of the wsdl file (created by axis)
end ended up all the time with the same message:

1.) I used the stubmaker.pl and it created me a great class:
connecting to the service, calling methods with simple datatypes as
arguments and getting/accessing complex objects is working fine. But
as soon as I get an object from the server that must be send back to
the server the client is claming that

"JavaObjectName" can't be found in a schema class 'SOAP::Serializer'

The object schema in the wsdl-type-definition and contains just
simple datatypes like strings. Do I have to write a serializer for
every custom object or is there just an error in the wsdl file?

<wsdl:types>
<schema targetNamespace="urn:JTestVO"
xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://xml.apache.org/xml-soap"/>
    <import namespace="http://ejb.javax"/>
    <import namespace="http://exception.myservice.localhost"/>
    <import namespace="http://localhost:8080/axis/services/myservice"/>
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="JTestVO">
     <sequence>
      <element name="firstname" nillable="true" type="xsd:string"/>
      <element name="lastname" nillable="true" type="xsd:string"/>
     </sequence>
    </complexType>
   </schema>
</wsdl:types>

results in
"JTestVO" can't be found in a schema class 'SOAP::Serializer'

2.)  Method

use strict;
use SOAP::Lite;
use Data::Dumper;
use MIME::Entity;
print "Calling Soap Server:\n\n";
my $service=SOAP::Lite->service('file:./Test.xml.wsdl');
my $id_vo=$service->getData("123123");
print "\nTest: ".$id_vo->{"firstname"};
my $cap=$service->getCapabilities($id_vo);

as soon as the last method is called I get again:
"JTestVO" can't be found in a schema class 'SOAP::Serializer'

Please give me a hint where I can find further information or how i
can create a custom object, which will be accepted by the webservice.

Thanks Gernot

Hello, I am attempting to test my SOAP::Lite client in various error
conditions. One such condition is when the SOAP server cannot be
reached (i.e., a connection timeout occurs).

I have set a timeout for the object:
my $soap = SOAP::Lite->uri($uri)->proxy($proxy, timeout => 10);

As I understand it, this should make a timeout occur after 10 seconds.

Next is my method call:

$soap->runner($para);

Since the server is not running, this will cause a connection timeout.
After 3 minutes (not 10 seconds), I receive a message:

500 Connect failed: connect: Connection timed out; Connection timed out

Also, it is important to note that if the method call is NOT in an
eval {};, then I get an exception when the timeout occurs (something I
cannot find documented anywhere).

My question is, how do I get the connect attempt to stop if my
specified timeout has elapsed, and simply allow me to detect the error
condition and allow my program to continue on?

Thanks in advance,
Dominick Meglio

--- Dominick Meglio <dmeglio@...> wrote:

> My question is, how do I get the connect attempt to
> stop if my
> specified timeout has elapsed, and simply allow me
> to detect the error
> condition and allow my program to continue on?

I don't know what the correct answer is regarding
S::L's handling of client connection timeouts. But, as
a workaround, you should be able to set an alarm
within your eval and trap it. You need a signal
handler for the alarm. I had an example of doing this
with something else. I'd have to look for it. (It is a
little trickier than it sounds because there's a race
condition between the inner alarm and the outer eval.
Something like that.)

As far as eval'ing to trap fatal errors. I think
that's relatively common. I know I had to do it with
ssh::sftp. I didn't think it was too cumbersome. I had
to accomodate for what may be multiple errors within
an eval and that $@ will have the last error (which
may not be as informative as earlier errors). I
handled this with a signal handler to capture every
warning event. I added each warning message to an
array each time the signal handler was invoked. In the
end, I had an array of messages (if multiple errors
occured).

=====
my @warnings;

$SIG{"__WARN__"} = sub { $warnings[$#warnings + 1] =
$_[0]; };

eval {$my_result = $object->function(".");};

$SIG{"__WARN__"} = "DEFAULT";

if ($#warnings > -1 or (!defined($pwd) or $pwd eq "")
) {
   # treat it as an error, display each row of @array
}
======

Maybe that would be useful to you?

Mark




__________________________________
Yahoo! Mail for Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
http://mobile.yahoo.com/learn/mail

Don't miss out on the lowest interest rates ever. Lower your monthly payments.
Saving money is easy, refinance now.
http://tpbaj.com/i/LzQvaW5kZXgvd2F6ZWUvbDJwMmZt take 30 seconds and fill out
this free form to save money

I am having a problem getting attachments to work. I have gone through
all of the previous messages on this topic, however none of them
solved my problem.

I am using Apache2::SOAP for mod_perl2 support after the mod_perl2 API
changes.

I am using this code to create the soap request (slightly modified to
conceal paths):


CLIENT CODE:

     my $Ent = MIME::Entity->build(
         Type        => "image/jpeg",
         Encoding    => 'base64',
         Path        => "/path/to/tehimage.jpeg",
         Filename    => "tehimage.jpeg",
         Disposition => 'attachment'
         );

     my @Parts = ($Ent);

     $Response = SOAP::Lite
         ->readable(1)
         ->uri("urn:/OR/SOAP")
         ->parts(@Parts)
         ->proxy("https://myserver.com/soap")
         ->req(FileName=>'tehimage.jpeg');


httpd.conf:

     <Location /soap>
         SetHandler perl-script
         PerlResponseHandler Apache2::SOAP
         PerlSetVar dispatch_to "OR::SOAP"
     </Location>


THE SOAP REQUEST:

SOAP::Transport::HTTP::Client::send_receive: POST
https://myserver.com/soap HTTP/1.1
Accept: text/xml
Accept: multipart/*
Content-Length: 5293
Content-Type: Multipart/Related; type="text/xml";
start="<main_envelope>"; boundary="----------=_1121282892-23095-0";
charset=utf-8
SOAPAction: "urn:/OR/SOAP#req"

This is a multi-part message in MIME format...

------------=_1121282892-23095-0
Content-Type: text/xml
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Location: /main_envelope
Content-ID: <main_envelope>

<?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
   >
     <namesp6:req xmlns:namesp6="urn:/OR/SOAP"
     >
       <c-gensym28
       >
         <FileName xsi:type="xsd:string"
>tehimage.jpeg</FileName></c-gensym28></namesp6:re
q></SOAP-ENV:Body></SOAP-ENV:Envelope>
------------=_1121282892-23095-0
Content-Type: image/jpeg; name="tehimage.jpeg"
Content-Disposition: attachment; filename="tehimage.jpeg"
Content-Transfer-Encoding: base64
Content-Description: This is a SOAP request with an image as a MIME
  attachment.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.417 (Entity 5.417)

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAHgAA/+4ADkFk
b2JlAGTAAAAAAf/bAIQAEAsLCwwLEAwMEBcPDQ8XGxQQEBQbHxcXFxcXHx4X
GhoaGhceHiMlJyUjHi8vMzMvL0BAQEBAQEBAQEBAQEBAQAERDw8RExEVEhIV
FBEUERQaFBYWFBomGhocGhomMCMeHh4eIzArLicnJy4rNTUwMDU1QEA/QEBA
QEBAQEBAQEBA/8AAEQgAlgCWAwEiAAIRAQMRAf/EAI0AAQACAwEBAAAAAAAA
--snip--


THE RESPONSE:

SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 200 OK
Connection: close
Date: Wed, 13 Jul 2005 19:29:19 GMT
Server: Apache
Content-Length: 787
Content-Type: text/xml; charset=utf-8
Client-Date: Wed, 13 Jul 2005 19:29:19 GMT
Client-Peer: [some ip]
Client-Response-Num: 1
SOAPServer: SOAP::Lite/Perl/0.60

<?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><SOAP-ENV:Fault><f
aultcode>SOAP-ENV:Client</faultcode><faultstring>Application
failed during request deserialization [Lite.pm]: junk 'This is a
multi-part message in MIME format...

------------=_1121282959-23095-1
Content-Type: text/xml
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Location: /main_envelope
Content-ID: ' before XML element
</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>



The above fault is happening before it ever gets to my service module.
It seems to be dying in SOAP::Lite.pm inside of the decode sub on the
line: my $parsed = $self->parser->parse($_[0]);

Any ideas?

Hi all,

The envelope I am receiving is something like:

  <soapenv:Body>
   <soapenv:Fault>
    <faultcode xmlns:ns1="kassandra">ns1:REQ002</faultcode>
    <faultstring>Malformed Request</faultstring>
    <detail>
    ...

I get "ns1:REQ002" as the fault code. How do I resolve "ns1" to the
correct namespace URI?

I would need to get the code as "kassandra:REQ002" for the correct
processing of the fault, as the server returns some error codes that
can only be distinguished by their namespaces, but I do not find any
way to translate the prefix in the faultcode value to the URI.

Thanks in advance,
Rodrigo Ruiz

Hi,
is the answer to my questions to simple or is there no
answer? It IS REALLY important for my project to solve
this serializer problem as soon as possible. I tried to
find a solution in the recommended book "Programming Web Services with
Perl" which seems to be not up-to-date enough.

Please give me a hint at least in a driection,
Gernot

Could you repost the question please?

A.


Quoting [gernot_stocker] (Jul 20 2005):
>
> Hi,
> is the answer to my questions to simple or is there no
> answer? It IS REALLY important for my project to solve
> this serializer problem as soon as possible. I tried to
> find a solution in the recommended book "Programming Web Services with
> Perl" which seems to be not up-to-date enough.
>
> Please give me a hint at least in a driection,
> Gernot


--
+-----------------------------------------------------------------+
| Andre Merzky                      | phon: +31 - 20 - 598 - 7759 |
| Vrije Universiteit Amsterdam (VU) | fax : +31 - 20 - 598 - 7653 |
| Dept. of Computer Science         | mail: merzky@...       |
| De Boelelaan 1083a                | www:  http://www.merzky.net |
| 1081 HV Amsterdam, Netherlands    |                             |
+-----------------------------------------------------------------+

Shure... I just copied the text from my former post:
Thanks for your interest
Gernot

Old message:

Hi all,
I have implemented a webservice with Java Axis and would like to offer
my users a perl client, too. Some other people asked already questions
about serializing java objects etc. on this list but they didn't get
an answer.

I have just ONE specific question about creating/sending a SOAP/Java
Object back to the server. Hopefully THIS question will be answered.

I'm using SOAP::Lite version 0.65 Beta 6 and was quite impressed by
its functionality and its easy usage.

I tried two ways of creating out of the wsdl file (created by axis)
end ended up all the time with the same message:

1.) I used the stubmaker.pl and it created me a great class:
connecting to the service, calling methods with simple datatypes as
arguments and getting/accessing complex objects is working fine. But
as soon as I get an object from the server that must be send back to
the server the client is claming that

"JavaObjectName" can't be found in a schema class 'SOAP::Serializer'

The object schema in the wsdl-type-definition and contains just
simple datatypes like strings. Do I have to write a serializer for
every custom object or is there just an error in the wsdl file?

<wsdl:types>
<schema targetNamespace="urn:JTestVO"
xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xml.apache.org/xml-soap"/>
<import namespace="http://ejb.javax"/>
<import namespace="http://exception.myservice.localhost"/>
<import namespace="http://localhost:8080/axis/services/myservice"/>
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="JTestVO">
<sequence>
<element name="firstname" nillable="true" type="xsd:string"/>
<element name="lastname" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</schema>
</wsdl:types>

results in
"JTestVO" can't be found in a schema class 'SOAP::Serializer'

2.) Method

use strict;
use SOAP::Lite;
use Data::Dumper;
use MIME::Entity;
print "Calling Soap Server:\n\n";
my $service=SOAP::Lite->service('file:./Test.xml.wsdl');
my $id_vo=$service->getData("123123");
print "\nTest: ".$id_vo->{"firstname"};
my $cap=$service->getCapabilities($id_vo);

as soon as the last method is called I get again:
"JTestVO" can't be found in a schema class 'SOAP::Serializer'

Please give me a hint where I can find further information or how i
can create a custom object, which will be accepted by the webservice.

Thanks Gernot

I am not good at WSDL files, but it seems to me it is
missing a port type and operation.  So, it does not specify
what methods can be called.  Wouldn't that be crucial?

e.g. 'getCapabilities' does not appear in your wsdl.

But then, as said, I could be completely of target...

Andre.


Quoting [gernot_stocker] (Jul 20 2005):
> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
> To: soaplite@yahoogroups.com
> From: "gernot_stocker" <gernot.stocker@...>
> Mailing-List: list soaplite@yahoogroups.com; contact
soaplite-owner@yahoogroups.com
> Date: Wed, 20 Jul 2005 08:58:45 -0000
> Subject: [soaplite] Re: SOAP::Lite client for Axis WebService and complex
objects
>
> Shure... I just copied the text from my former post:
> Thanks for your interest
> Gernot
>
> Old message:
>
> Hi all,
> I have implemented a webservice with Java Axis and would like to offer
> my users a perl client, too. Some other people asked already questions
> about serializing java objects etc. on this list but they didn't get
> an answer.
>
> I have just ONE specific question about creating/sending a SOAP/Java
> Object back to the server. Hopefully THIS question will be answered.
>
> I'm using SOAP::Lite version 0.65 Beta 6 and was quite impressed by
> its functionality and its easy usage.
>
> I tried two ways of creating out of the wsdl file (created by axis)
> end ended up all the time with the same message:
>
> 1.) I used the stubmaker.pl and it created me a great class:
> connecting to the service, calling methods with simple datatypes as
> arguments and getting/accessing complex objects is working fine. But
> as soon as I get an object from the server that must be send back to
> the server the client is claming that
>
> "JavaObjectName" can't be found in a schema class 'SOAP::Serializer'
>
> The object schema in the wsdl-type-definition and contains just
> simple datatypes like strings. Do I have to write a serializer for
> every custom object or is there just an error in the wsdl file?
>
> <wsdl:types>
> <schema targetNamespace="urn:JTestVO"
> xmlns="http://www.w3.org/2001/XMLSchema">
> <import namespace="http://xml.apache.org/xml-soap"/>
> <import namespace="http://ejb.javax"/>
> <import namespace="http://exception.myservice.localhost"/>
> <import namespace="http://localhost:8080/axis/services/myservice"/>
> <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
> <complexType name="JTestVO">
> <sequence>
> <element name="firstname" nillable="true" type="xsd:string"/>
> <element name="lastname" nillable="true" type="xsd:string"/>
> </sequence>
> </complexType>
> </schema>
> </wsdl:types>
>
> results in
> "JTestVO" can't be found in a schema class 'SOAP::Serializer'
>
> 2.) Method
>
> use strict;
> use SOAP::Lite;
> use Data::Dumper;
> use MIME::Entity;
> print "Calling Soap Server:\n\n";
> my $service=SOAP::Lite->service('file:./Test.xml.wsdl');
> my $id_vo=$service->getData("123123");
> print "\nTest: ".$id_vo->{"firstname"};
> my $cap=$service->getCapabilities($id_vo);
>
> as soon as the last method is called I get again:
> "JTestVO" can't be found in a schema class 'SOAP::Serializer'
>
> Please give me a hint where I can find further information or how i
> can create a custom object, which will be accepted by the webservice.
>
> Thanks Gernot
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>



--
+-----------------------------------------------------------------+
| Andre Merzky                      | phon: +31 - 20 - 598 - 7759 |
| Vrije Universiteit Amsterdam (VU) | fax : +31 - 20 - 598 - 7653 |
| Dept. of Computer Science         | mail: merzky@...       |
| De Boelelaan 1083a                | www:  http://www.merzky.net |
| 1081 HV Amsterdam, Netherlands    |                             |
+-----------------------------------------------------------------+

On Wednesday 20 July 2005 11:11, Andre Merzky wrote:
> I am not good at WSDL files, but it seems to me it is
> missing a port type and operation.  So, it does not specify
> what methods can be called.  Wouldn't that be crucial?
>
> e.g. 'getCapabilities' does not appear in your wsdl.

I included in the problem description just the relevant type part of
the wsdl, not the complete wsdl where also the getCapabilities()
method is defined. This method was just an example which gets
such a JTestVO as a parameter.

Should I send a complete WSDL file of the test service?

Thanks Gernot
--
Gernot Stocker,
Institute for Genomics and Bioinformatics(IGB)
Petersgasse 14, 8010 Graz, Austria
Tel.: ++43 316 873 5345
http://genome.tugraz.at

Could you please?  As said, I am not fit in WSDL, but I
could throw a second pairs of eyes on it ;-)

A.


Quoting [Gernot Stocker] (Jul 20 2005):
> From: Gernot Stocker <gernot.stocker@...>
> To: Andre Merzky <andre@...>
> Subject: Re: SOAP::Lite client for Axis WebService and complex objects
> Date: Wed, 20 Jul 2005 11:25:59 +0200
> Cc: soaplite@yahoogroups.com
>
> On Wednesday 20 July 2005 11:11, Andre Merzky wrote:
> > I am not good at WSDL files, but it seems to me it is
> > missing a port type and operation.  So, it does not specify
> > what methods can be called.  Wouldn't that be crucial?
> >
> > e.g. 'getCapabilities' does not appear in your wsdl.
>
> I included in the problem description just the relevant type part of
> the wsdl, not the complete wsdl where also the getCapabilities()
> method is defined. This method was just an example which gets
> such a JTestVO as a parameter.
>
> Should I send a complete WSDL file of the test service?
>
> Thanks Gernot
--
+-----------------------------------------------------------------+
| Andre Merzky                      | phon: +31 - 20 - 598 - 7759 |
| Vrije Universiteit Amsterdam (VU) | fax : +31 - 20 - 598 - 7653 |
| Dept. of Computer Science         | mail: merzky@...       |
| De Boelelaan 1083a                | www:  http://www.merzky.net |
| 1081 HV Amsterdam, Netherlands    |                             |
+-----------------------------------------------------------------+

Hello,

I'm hoping someone can help. I have a SOAP server that's been running
happily on 0.55 and which we're now looking at upgrading so that it
can support soap 1.2.

I've tried running the same code with a SOAP message that worked fine
on the old version and have hit a problem with arrays and multirefs.

Essentially, the XML describes an array of a complex type; the complex
type contains arrays of complex types. The XML sample I am using was
generated by a .Net client ( I think ) so uses multirefs to handle the
complex types and the arrays.

Here is an extract from the XML:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="urn:VendaProducts"
xmlns:types="urn:VendaProducts/encodedTypes"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
     <tns:CreateProduct>
       <skuElements href="#id1"/>
     </tns:CreateProduct>
     <soapenc:Array id="id1" soapenc:arrayType="tns:skuElement[1]">
       <Item href="#id2"/>
     </soapenc:Array>
     <tns:skuElement id="id2" xsi:type="tns:skuElement">
       <sku xsi:type="xsd:string">test1</sku>
       <priceElements href="#id3"/>
       <mediaElements href="#id5"/>
     </tns:skuElement>
     <soapenc:Array id="id3" soapenc:arrayType="tns:priceElement[1]">
       <Item href="#id4"/>
     </soapenc:Array>
     <soapenc:Array id="id5" soapenc:arrayType="tns:mediaElement[1]">
       <Item href="#id6"/>
     </soapenc:Array>
     <tns:priceElement id="id4" xsi:type="tns:priceElement">
       <sell xsi:type="xsd:double">0004999</sell>
       <cost xsi:type="xsd:double">000133080</cost>
     </tns:priceElement>
     <tns:mediaElement id="id6" xsi:type="tns:mediaElement">
       <name xsi:type="xsd:string">picture.jpg</name>
       <key xsi:type="xsd:string">thumb</key>
     </tns:mediaElement>
   </soap:Body>
</soap:Envelope>

This should deserialize to an array with a single skuElement. This
skuElement should contain an array with a single priceElement and an
array with a single mediaElement.

What I actually see on the server side (using Data::Dumper) is:

$VAR1 = [
           bless( {
                    'sku' => 'test1',
                    'priceElements' => [
                                       bless( {
                                                'cost' => '000133080',
                                                'sell' => '0004999'
                                              }, 'priceElement' )
                                     ],
                    'mediaElements' => [
                                       bless( {
                                                'name' => 'picture.jpg',
                                                'key' => 'thumb'
                                              }, 'mediaElement' )
                                     ],
                  }, 'skuElement' ),
           $VAR1->[0]{'priceElements'},
           $VAR1->[0]{'mediaElements'}
         ];


The code getting this is:

sub CreateProduct
{
	 my $self = shift;
	 my $envelope = pop(@_);

	 my $root = $envelope->dataof("/Envelope/Body/CreateProduct/skuElements");
	 my $products = $root->value;
	 print Dumper($products);
}

As I say, this worked fine using version 0.55 of SOAP::Lite and gave
the data structure as expected.

I also tried hand-editing the XML so that the priceElements and
mediaElements arrays (and their elements) are embedded directly in the
skuElement object. This worked fine and gave a data-structure as expected.

Any ideas?

Andy

On Wednesday 20 July 2005 11:38, Andre Merzky wrote:
> Could you please?  As said, I am not fit in WSDL, but I
> could throw a second pairs of eyes on it ;-)

Hi,
I have attached the WSDL generated by axis after deploying it with the following
axis deployment descriptor:

<deployment
	 xmlns="http://xml.apache.org/axis/wsdd/"
	 xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
  <service name="TestService" provider="java:EJB">
       <parameter name="beanJndiName" value="AxisServiceBean" />
       <parameter name="homeInterfaceName"
value="at.tugraz.genome.testservice.AxisServiceBeanHome" />
       <parameter name="remoteInterfaceName"
value="at.tugraz.genome.testservice.AxisService" />
       <parameter name="allowedMethods" value="*"/>
       <parameter name="jndiURL" value="jnp://localhost:1099"/>
       <parameter name="jndiContextClass"
value="org.jnp.interfaces.NamingContextFactory"/>
       <beanMapping qname="myNS:JTestVO" xmlns:myNS="urn:JTestVO"
languageSpecificType="java:at.tugraz.genome.testservice.JTestVO" />
   </service>
</deployment>

If this problem can/will be solved I would provide the complete code of the
axis/java/perl
TestService-project and a short howto. Then other people don't have to struggle
like me.

Thanks Gernot
--
Gernot Stocker,
Institute for Genomics and Bioinformatics(IGB)
Petersgasse 14, 8010 Graz, Austria
Tel.: ++43 316 873 5345
http://genome.tugraz.at

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
targetNamespace="http://localhost:8080/csaxis/services/TestService"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://localhost:8080/csaxis/services/TestService"
xmlns:intf="http://localhost:8080/csaxis/services/TestService"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns1="urn:JTestVO" xmlns:tns2="http://ejb.javax"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<!--WSDL created by Apache Axis version: 1.2
Built on May 03, 2005 (02:20:24 EDT)-->
  <wsdl:types>
   <schema targetNamespace="urn:JTestVO"
xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://xml.apache.org/xml-soap"/>
    <import namespace="http://ejb.javax"/>
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="JTestVO">
     <sequence>
      <element name="firstname" nillable="true" type="soapenc:string"/>
      <element name="lastname" nillable="true" type="soapenc:string"/>
     </sequence>
    </complexType>
   </schema>
   <schema targetNamespace="http://xml.apache.org/xml-soap"
xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://ejb.javax"/>
    <import namespace="urn:JTestVO"/>
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="Vector">
     <sequence>
      <element maxOccurs="unbounded" minOccurs="0" name="item"
type="xsd:anyType"/>
     </sequence>
    </complexType>
   </schema>
  </wsdl:types>

    <wsdl:message name="getEJBHomeResponse">

       <wsdl:part name="getEJBHomeReturn" type="xsd:anyType"/>

    </wsdl:message>

    <wsdl:message name="getPrimaryKeyRequest">

    </wsdl:message>

    <wsdl:message name="testAvailabilityRequest">

    </wsdl:message>

    <wsdl:message name="authenticateServiceRequest">

       <wsdl:part name="in0" type="soapenc:string"/>

       <wsdl:part name="in1" type="soapenc:string"/>

    </wsdl:message>

    <wsdl:message name="isIdenticalResponse">

       <wsdl:part name="isIdenticalReturn" type="xsd:boolean"/>

    </wsdl:message>

    <wsdl:message name="removeResponse">

    </wsdl:message>

    <wsdl:message name="getHandleRequest">

    </wsdl:message>

    <wsdl:message name="getPrimaryKeyResponse">

       <wsdl:part name="getPrimaryKeyReturn" type="xsd:anyType"/>

    </wsdl:message>

    <wsdl:message name="getCapabilitiesResponse">

       <wsdl:part name="getCapabilitiesReturn" type="apachesoap:Vector"/>

    </wsdl:message>

    <wsdl:message name="testAvailabilityResponse">

       <wsdl:part name="testAvailabilityReturn" type="soapenc:string"/>

    </wsdl:message>

    <wsdl:message name="getHandleResponse">

       <wsdl:part name="getHandleReturn" type="xsd:anyType"/>

    </wsdl:message>

    <wsdl:message name="removeRequest">

    </wsdl:message>

    <wsdl:message name="isIdenticalRequest">

       <wsdl:part name="in0" type="xsd:anyType"/>

    </wsdl:message>

    <wsdl:message name="getEJBHomeRequest">

    </wsdl:message>

    <wsdl:message name="getCapabilitiesRequest">

       <wsdl:part name="in0" type="tns1:JTestVO"/>

    </wsdl:message>

    <wsdl:message name="authenticateServiceResponse">

       <wsdl:part name="authenticateServiceReturn" type="tns1:JTestVO"/>

    </wsdl:message>

    <wsdl:portType name="AxisService">

       <wsdl:operation name="testAvailability">

          <wsdl:input message="impl:testAvailabilityRequest"
name="testAvailabilityRequest"/>

          <wsdl:output message="impl:testAvailabilityResponse"
name="testAvailabilityResponse"/>

       </wsdl:operation>

       <wsdl:operation name="getCapabilities" parameterOrder="in0">

          <wsdl:input message="impl:getCapabilitiesRequest"
name="getCapabilitiesRequest"/>

          <wsdl:output message="impl:getCapabilitiesResponse"
name="getCapabilitiesResponse"/>

       </wsdl:operation>

       <wsdl:operation name="authenticateService" parameterOrder="in0 in1">

          <wsdl:input message="impl:authenticateServiceRequest"
name="authenticateServiceRequest"/>

          <wsdl:output message="impl:authenticateServiceResponse"
name="authenticateServiceResponse"/>

       </wsdl:operation>

       <wsdl:operation name="remove">

          <wsdl:input message="impl:removeRequest" name="removeRequest"/>

          <wsdl:output message="impl:removeResponse" name="removeResponse"/>

       </wsdl:operation>

       <wsdl:operation name="getHandle">

          <wsdl:input message="impl:getHandleRequest" name="getHandleRequest"/>

          <wsdl:output message="impl:getHandleResponse"
name="getHandleResponse"/>

       </wsdl:operation>

       <wsdl:operation name="getEJBHome">

          <wsdl:input message="impl:getEJBHomeRequest" name="getEJBHomeRequest"/>

          <wsdl:output message="impl:getEJBHomeResponse"
name="getEJBHomeResponse"/>

       </wsdl:operation>

       <wsdl:operation name="getPrimaryKey">

          <wsdl:input message="impl:getPrimaryKeyRequest"
name="getPrimaryKeyRequest"/>

          <wsdl:output message="impl:getPrimaryKeyResponse"
name="getPrimaryKeyResponse"/>

       </wsdl:operation>

       <wsdl:operation name="isIdentical" parameterOrder="in0">

          <wsdl:input message="impl:isIdenticalRequest"
name="isIdenticalRequest"/>

          <wsdl:output message="impl:isIdenticalResponse"
name="isIdenticalResponse"/>

       </wsdl:operation>

    </wsdl:portType>

    <wsdl:binding name="TestServiceSoapBinding" type="impl:AxisService">

       <wsdlsoap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>

       <wsdl:operation name="testAvailability">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="testAvailabilityRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://testservice.genome.tugraz.at" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="testAvailabilityResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="getCapabilities">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="getCapabilitiesRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://testservice.genome.tugraz.at" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="getCapabilitiesResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="authenticateService">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="authenticateServiceRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://testservice.genome.tugraz.at" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="authenticateServiceResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="remove">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="removeRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://ejb.javax" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="removeResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="getHandle">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="getHandleRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://ejb.javax" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="getHandleResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="getEJBHome">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="getEJBHomeRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://ejb.javax" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="getEJBHomeResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="getPrimaryKey">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="getPrimaryKeyRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://ejb.javax" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="getPrimaryKeyResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

       <wsdl:operation name="isIdentical">

          <wsdlsoap:operation soapAction=""/>

          <wsdl:input name="isIdenticalRequest">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://ejb.javax" use="encoded"/>

          </wsdl:input>

          <wsdl:output name="isIdenticalResponse">

             <wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8080/csaxis/services/TestService" use="encoded"/>

          </wsdl:output>

       </wsdl:operation>

    </wsdl:binding>

    <wsdl:service name="AxisServiceService">

       <wsdl:port binding="impl:TestServiceSoapBinding" name="TestService">

          <wsdlsoap:address
location="http://localhost:8080/csaxis/services/TestService"/>

       </wsdl:port>

    </wsdl:service>

</wsdl:definitions>