Sorry I used rpc/encoded that gave problems on both toolkits. .Net would not import it and AXIS RC1 created bad stub code.
James suggested to use the Xerces XML parser in stead. Further I don't have a clue :-( Sjaak > -----Original Message----- > From: Daniel Hägg [mailto:[EMAIL PROTECTED]] > Sent: 02 October, 2002 12:48 > To: [EMAIL PROTECTED] > Subject: Re: SAXException Bad types > > > > Schie, Sjaak van wrote: > > >You are revering to element name in the part like: > > <message name="InAllConfigurations"> > > <part name="parameters" element="s0:RequestAllConfigurations" /> > > </message> > > <message name="OutAllConfigurations"> > > <part name="parameters" element="s0:AllConfigurationsResponse" /> > > </message> > > > >This is all correct WSDL, but I have bad experience with > this (both .Net & > >.AXIS). > > > Really? But I have copied this from how .NET generates WSDL. > > >When I changed element=xxx to type=xxx, it all works (both toolkits). > > > Can you please show me what your type definition looks like. > It cannot be the same as when element=xxx is used. > > / > / Daniel > > -- The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
