RE: Axis client to .NET server problems

2004-09-24 Thread Anne Thomas Manes
Title: RE: Axis client to .NET server problems I suggest that you run wsdl2java and use the generated stub rather than using the DII call interface.   The wrapped style (which automatically marshals your parameters) doesn’t work with the call interface. It works only when using the stub

RE: Axis client to .NET server problems

2004-09-24 Thread Anne Thomas Manes
Title: RE: Axis client to .NET server problems I suggest that you run wsdl2java and use the generated stub rather than using the DII call interface.   The wrapped style (which automatically marshals your parameters) doesn’t work with the call interface. It works only when using the stub

RE: Axis client to .NET server problems

2004-09-24 Thread Peter S. Ng
Title: RE: Axis client to .NET server problems Hi, I altered the operation style to "document" in the Call object, but when the request shows up as: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.

RE: Axis client to .NET server problems

2004-09-24 Thread Sunkara, Jayachandra S
Title: Axis client to .NET server problems Make sure you don’t have your client configured to send the soap message in the RPC/literal style. Follow DOCUMENT/literal style. That should work fine. That’s what I did, when I experienced similar problem interoping with a .NET server. .NET by

Axis client to .NET server problems

2004-09-24 Thread Peter S. Ng
Title: Axis client to .NET server problems Hi, I have created a client using AXIS to talk to a .NET service however, I always this error: - http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected