I have succesfully consumed an AXIS web service using .NET, please refer to this url for further detail: http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=178
However, I haven't been able to do the reverse process, i.e. to consume a .NET service using AXIS and I believe it's the way that the WSDL is generated by .NET, in which for most -if not all- data types are declared as complex types, which java2wsdl leaves unbound, or at least that's what I can tell from the autogenerated stub files. I recently received an email on how to instruct in C# code not to use complex types, but I haven't had a chance to try it. Jorge. -----Original Message----- From: Andrew Stopford [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 7:38 PM To: [EMAIL PROTECTED] Subject: consuming axis in .net Hi, Apologies if I cross any ground covered ground here but I was wondering if anyone has successfully consumed axis using .net beta 2 ? I have created a simple .jws file, this runs fine using axis. I have also created a simple .net web service and that works fine in .net so I know .net and axis are working ok. Using visual studio .net beta 2 I can add the .jws?wsdl file as a web referance and access its methods within the enviroment. If I however run the code a SoapException is returned (time out error) Any clues, is this approach best or is another approach better ? Anyone who does this before I would be thankful for a heads up. Thanks Andrew
