You are correct that I do not control the .NET service, although the folks who do say they'll make a patch for Java. Not sure how they'll manage that though.
Thanks for the insight. That saves me a lot of head scratching. 8- ) -----Original Message----- From: Cun Yong Tan [mailto:[EMAIL PROTECTED]] Sent: Friday, April 26, 2002 6:09 AM To: [EMAIL PROTECTED] Subject: RE: WSDL2java error with .NET WSDL I think the problem is because Axis only handles a subset of the XML Schema data types. The JAX-RPC spec specifies the XML Schema data types that a JAX-RPC implementation are required to support. (See "Appendix: XML Schema Support" of the JAX-RPC draft spec for details.) "time" is not one of them but "dateTime" is. If you change the "time" to "dateTime", it should work - assuming that you don't run into other data types (e.g. unsignedInt) that Axis don't support either. Of course, this also assumes that you control the .NET service also which doesn't sound like it in your case. >From: "Mount, Dave" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: RE: WSDL2java error with .NET WSDL >Date: Thu, 25 Apr 2002 16:59:05 -0700 > >I am having similar trouble with a .NET WSDL file for a different set of >web >services. > >java.io.IOException: Type http://www.w3.org/2001/XMLSchema:time is >referenced but not defined. > at >org.apache.axis.wsdl.toJava.SymbolTable.checkForUndefined(Unknown >Source) > at org.apache.axis.wsdl.toJava.SymbolTable.add(Unknown Source) > at org.apache.axis.wsdl.toJava.Emitter.emit(Unknown Source) > at org.apache.axis.wsdl.toJava.Emitter.emit(Unknown Source) > at org.apache.axis.wsdl.WSDL2Java$WSDLRunnable.run(Unknown Source) > at java.lang.Thread.run(Thread.java:484) > > >When I look at the XMLSchema, I see that 'time' is part of a secondary >schema that is included in the first. Since this comes from w3.org, I >assume that the schemas are correct. Perhaps WSDL2Java isn't looking at >the >include file, although it recognizes all of the references before this >(string, date, etc.) > >The suspicious area might be namespace references to Microsoft schemas for >the .NET toolkit. The company that generated the WSDL says it works on >.NET >(with C# and all of that nonsense 8- ). > >Any thoughts? Has anyone tried WSDL2Java on anything more complex than the >samples? >------------------------------------- >Dave Mount >Application Architect >BenefitPoint, Inc. >[EMAIL PROTECTED] _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
