Re: Microsoft interoperability

2007-10-09 Thread Dave Kallstrom
I've seen that warning from .NET's wsdl tool a number of times. It has never caused any problems though. It sill seems to generate both Vb and C# code that works just fine. Also we have two clients up and running on .NET and all are running fine. On 10/9/07, Benson Margulies [EMAIL PROTECTED]

Re: Microsoft interoperability

2007-10-09 Thread Daniel Kulp
One more thing... Can you run our own wsdlvalidator (in the bin directory) against the wsdl just to double check that the wsdl looks OK from it's standpoint? Dan On Tuesday 09 October 2007, Dave Kallstrom wrote: I've seen that warning from .NET's wsdl tool a number of times. It has never

RE: Microsoft interoperability

2007-10-09 Thread Benson Margulies
So far, not too good. 'Unable to generate a temporary class (result = 1). Error CS0030: Cannot convert type BasisTechnology.rnm.ws.Name[] to BasisTechnology.rnm.ws.Name' This is thrown on construction of the proxy class generated by their wsdl tool. I'm also getting all the parameters wrapped

RE: Microsoft interoperability

2007-10-09 Thread Benson Margulies
Subject: RE: Microsoft interoperability So far, not too good. 'Unable to generate a temporary class (result = 1). Error CS0030: Cannot convert type BasisTechnology.rnm.ws.Name[] to BasisTechnology.rnm.ws.Name' This is thrown on construction of the proxy class generated by their wsdl tool

RE: Microsoft interoperability

2007-10-09 Thread Benson Margulies
The cs0030 is this charming bug of Microsoft's: http://support.microsoft.com/kb/891386 -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 9:57 AM To: cxf-user@incubator.apache.org Subject: RE: Microsoft interoperability Also