On 2005-03-06 at 00:11:13 and11_bf wrote:
>--- In email@example.com, jmzorko@m... wrote:
>> > use SOAP::Lite;
>> > print SOAP::Lite
>> > ->
>> > service('http://www.xmethods.net/sd/StockQuoteService.wsdl')
>> > -> getQuote('MSFT');
>> Is this better?
>> my $success = eval
>> my $service = SOAP::Lite->service( "uri://to.WSDL.file"
>> $service->someMethod( $someParam, @someArrayOParams );
>> Falling You - exploring the beauty of voice and sound
>> New album, "Touch", available now
>Sorry, I've sent prev. message to the wrong address.
>Thanks fore reply. Anyway, this is not what I'm looking for.
>$service->someMethod( $someParam, @someArrayOParams );
>Code above calls someMethod as a class method rather than object's
>I.e. I'd like to have object initialized (I also waht to be able to
>pass some args. into class' constructor), something like this:
>$obj = $service->SOAP::new('args');
>I know it is possible without using WSDL thi way:
>$service = SOAP::Lite->proxy(..)->uri(..);
>$obj = $service->call(new => 'args')->result;
I don't think this will do what you are claiming. $obj will just be a
variable in your client, it will not have any reference to a remote
object. You still need to do
to pass the object back to the remote system.
>But I didn't see any directions on using such things with WSDL. All I
>saw is just a phrases about that in this case $service is not a
>SOAP::SOM. So, does it mean that I can't get object reference while
Using WSDL you can get the SOAP::SOM object from the most recent call
my $result = $service->someMethod();
my $som = $service->call;
The 'O' in SOAP stopped meaning 'Object' a long time ago. It is
probably best to treat SOAP as a mechanism for RPC and for
transferring XML documents. It is not a way of handling remote
S::L does provide some support for that though using 'autodispatch',
but that will only be of use when both client and server are written