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
From: Wojciech Buczak [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 27, 2007 11:03 AM
To: axis-user@ws.apache.org
Subject: RE: problem: AXIS client = .NET service (wrong content of the SOAP
messages)
Hi,
I have a suspicion that my problem is based on the wsdl encoding
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:
Hi,
I have a suspicion that my problem is based on the wsdl encoding:
document
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 stub from WSDL of the OPC DA XML web service and tried to call
some of it's interfaces. While some of them work fine, calling some
others end
