Hi, Mark! ... I think it s too long ;) ... hm, I wouldn t say that. It s little bit more complicated. $soap = SOAP::Lite- proxy(...)- uri();Message 1 of 3 , Oct 31, 2001View SourceHi, Mark!
--- Mark Wilkinson <mwilkinson@...> wrote:
> I have lurked long enough :-)I think it's too long ;)
> has bugged me for the past few weeks. The SoapLite documentation
> implies that these two statements are identical:hm, I wouldn't say that. It's little bit more complicated.
> $service->call("Method" => @args)->result;
$soap = SOAP::Lite->proxy(...)->uri();
$soap->call(Method => @args);
*almost* identical (->call gives some advantages) as well as
$soap->call(Method => @args)->result;
where both return *real* values (whereas code above returns SOM).
now, this code works differently:
$service = SOAP::Lite->service('http://....wsdl');
$service->Method(@args); # returns *real* result
$service->call(Method => @args); # isn't available in this case
> *need* the latter to work because I need to get my hands on the SOMYou can still access SOM object using
> comes back from the method call, and the first statement does not
> return a SOM.
which returns SOM object that's the result of the last call.
> The error I get is always the same: Can't call send_recieve on anbtw, v0.52 producec different (better?) error in this case:
> undefined value.
"Transport is not specified (using proxy() method or service
Hope it helps.
Best wishes, Paul.
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
... thank you for your welcome, and for your rapid reply! ... aha! So my last couple of weeks have been wasted trying to make something work that *can t* workMessage 2 of 3 , Oct 31, 2001View Source--- In soaplite@y..., Paul Kulchenko <paulclinger@y...> wrote:
> I think it's too long ;)thank you for your welcome, and for your rapid reply!
> $service = SOAP::Lite->service('http://....wsdl');aha! So my last couple of weeks have been wasted trying to make
> $service->Method(@args); # returns *real* result
> $service->call(Method => @args); # isn't available in this case
something work that *can't* work :-) Okay, next time I'll spend less
time lurking and more time questioning!!
> $service->callyeah, that's what I am doing... I just thought it was a bit "messy" to
do it that way, and was wondering why I wasn't able to do it the other
> "Transport is not specified (using proxy() method or serviceI had a feeling that this was a part of the problem. I had noticed
that, although WSDL has a "slot" for transport in the soap:binding, it
doesn't seem to make much difference what uri I put in there... so I
assumed that it was ignored.
Well, I'm relieved to have that all sorted out! I have one more
problem, but I want to work on it myself for a while before I ask the
group, otherwise I will never learn this stuff deeply...