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 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]> wrote: > > I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL > > from one of my CXF services. > > > > The results are not wonderful. I get warnings like the following. > > Based on my reading of the WSDL, the Microsoft tool is just > > confused, but I wonder if anyone else has been here? > > > > Schema validation warning: Schema item 'complexType' named > > 'NameIndexQuery' from namespace 'http://index.rnm.basistech.com' is > > invalid. Namespace 'http://rnm.basistech.com' is not available to be > > referenced in this schema. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
