A bigger issue would be all the nillable elements that are types that aren't nillable in .NET, if a message contains a xsi:nil='true' for an xsd:int, xsd:dateTime (and other value types in .NET) .NET will fail to de-seialize the message. IMO This is by far a bigger issue than the rpc/encoded fud.
Cheers Simon > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 04, 2005 7:46 AM > To: [EMAIL PROTECTED] > Subject: Re: WSDL critique? > > Well... > > You're using RPC/encoded, and you're using SOAP encoding > arrays. And although these aren't Java-specific, they will > cause interop problems with .NET. If you want to ensure > interoperability with .NET, you should stick with WS-I > compliance and use the "wrapped" style. > > Anne > > > On Sun, 02 Jan 2005 21:22:21 -0700, Larry Meadors > <[EMAIL PROTECTED]> wrote: > > Duh. Here is the WSDL. > > > > >>> Larry Meadors 01/02/05 9:18 PM >>> > > OK, I am new at this, but want to create a web service that > is easy to > > use from both .net and java clients. > > > > I took a look at the WSDL, and do not see anything that looks java > > specific, but am afraid that it would need to bite me on the nose > > before I would. :-) > > > > Anyone willing to take a look and make some suggestions? > > > > Larry > > > > > > > >