Prev: making executables from expect scripts
Next: canvas $pathname -wrap 1
From: Gerald W. Lester on 14 Jul 2010 23:40
Georgios Petasis wrote:
> στις 6/7/2010 22:56, O/H Donal K. Fellows έγραψε:
>> I'm working with an existing (and rather rococo) web service that has a
>> very particular model of how it publishes its WSDL. In particular, it
>> publishes its service address in one WSDL, its service definition in
>> another WSDL, and the types and elements used in a whole slew of XSDs.
>> It's frankly a mess, but I'm stuck with it (unless I can prove that it
>> is wrong, which I doubt).
>>
>> The problem? The WS::Client package (version 1.1.1, in the teapot)
>> chokes on this complexity when I use GetAndParseWsdl, only managing to
>> identify that there is a service on the port and not how to send it any
>> messages. If I try using ImportNamespace to add the extra definitions
>> in, then things also fall apart for the apparent lack of a
>> "targetNamespace" even though I can read that attribute on the top-level
>> element in the various documents when I download them manually.
>>
>> What, if anything, am I doing wrong? (If you want the URL of the parent
>> WSDL for testing, email me privately; I'd rather not expose the service
>> to arbitrary searching from the whole world as it's still experimental.)
>>
>> Donal.
>>
>
> Dear Donal,
>
> Have you resolved the issue?

I've not yet had a chance to do the required reworks.


--
+------------------------------------------------------------------------+
| Gerald W. Lester, President, KNG Consulting LLC |
| Email: Gerald.Lester(a)kng-consulting.net |
+------------------------------------------------------------------------+
First  |  Prev  | 
Pages: 1 2
Prev: making executables from expect scripts
Next: canvas $pathname -wrap 1