Cheers
Wojtek
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 27, 2007 1:43 PM
To: axis-user@ws.apache.org
Subject: Re: problem: AXIS client <=> .NET service (wrong content of the SOAP
messages)
You generated stubs using wsdl2
You generated stubs using wsdl2java, right? The tool will generate
code according to the binding specified in the WSDL, which is wrapped
doc/literal.
This method should work:
service.read(opt,items,bholder,rslt,err);
Anne
On 9/27/07, Wojciech Buczak <[EMAIL PROTECTED]> wrote:
>
>
>
>
> H
Hi,
I have a suspicion that my problem is based on the wsdl encoding:
document/literal or rpc.
Do you think it is possible somehow to ''force'' axis to use different
encoding while generating the java classes?
Cheers
Wojtek
From: Wojciech Buczak [
Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 26, 2007 11:51 PM
> To: axis-user@ws.apache.org
> Subject: Re: problem: AXIS client <=> .NET service (wrong content of the
> SOAP messages)
>
> Gmail cut off most of the WSDL. Could you send it as
Sure,
Please find the WSDL attached
Cheers
Wojtek
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 26, 2007 11:51 PM
To: axis-user@ws.apache.org
Subject: Re: problem: AXIS client <=> .NET service (wrong content of the
SOAP messages)
Gmail cut off most of the WSDL. Could you send it as an attachment please?
Thanks,
Anne
On 9/26/07, Wojciech Buczak <[EMAIL PROTECTED]> wrote:
>
>
> Sure!
>
> Thanks for your help!
>
> PS. This is a standard OPC-XML da WSDL, which specifies basic operations for
> accessing OPC servers from SOAP.
I'm not able to access the WSDL. Can you post it here for us?
Anne
On 9/26/07, Wojciech Buczak <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
>
>
> I've encountered a problem while using AXIS-generated java client that tries
> to call a .NET web service. Using AXIS 1.4 I've generated the client's st
