Hi, what exactly do you need to do? When you encode the AXIS service with DOC / lireral then that creates a lof of problems on the AXIS side, sometimes AXIS creates DOC / encoded types which is not valid (in a DOC/literal context) and .NET does not handle them. When you encode the AXIS service with RPC / encoded then sending arrays of basic types (byte, int, string, ...) should work fine (it tested it with C#), yet sending HashMaps or the like does not work but there is a ciruumvention. Useful links are: http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/DotNetInterop http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/DotNetInteropMapInfo (this shows how to send a java.util.Map over the wire interoperably)
Okay, without detailed information I cannot answer further. Paul -----Original Message----- From: peter maas [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 8. September 2004 09:25 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Axis webservices and Visual Basic Hi all, we are experimenting with accessing our Axis based webservices with a Visual Basic client. Alltough we have manage to use the VB client on non-axis webservices it doesn't work with any of the axis webservices. We have tried a some of the different (rpc/document/wrapped)* *encoding styles, but this doesn't seem to change anything. anyone got any pointers to documentation related to what the cause of this problem might be? regards, Peter Maas Application Architect / Streaming Noterik Multimedia BV Prins Hendrikkade 120 1011 AM Amsterdam The Netherlands Tel: +31 (0)205929966 Fax: +31 (0)204688405 Gsm: +31 (0)624687952 Web: www.noterik.nl -------------------------------------- Take a look at our streaming solutions: http://www.streamedit.com/demo.html Recent project: http://www.managenergy.tv --------------------------------------- :wq!
