Thanks for the reply. What version Axis are your working with? I understand doc literal is the way to go but I was also under the impression that some people had this working with soap rpc encoding.
My goal is to get this working with as little effort as possible. That's why I started with soap rpc encoding. --- James Richardson <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > Sent: 06 January 2005 23:35 > > To: [EMAIL PROTECTED] > > Subject: Axis - .Net Interop Problems > > > > Problem: > > ======== > > The .Net 1.1 wsdl tool does not like the wsdl > > generated by Axis 1.1. The datatype 'Array' is > > missing. > > > > > > Environment: > > ============ > > Jboss 3.2.3/Axis 1.1 - .NET 1.1 > > > > Hosting services via Axis SOAP RPC Encoding which > > include complex types and arrays of other complex > > types. > > > > > > I too am wrestling with the same issue. I've found > more success with > "wrapped", "literal" services. This seems to get > around the array issue. > > However, axis seems to still generate broken wsdl, > as in .net you will > need to go around replacing "Unqualified" encoding > references to > "Qualified" in the .net generated code. > > You will also need to set up a BeanMapping element > for each of your > complex types in Axis. > > At least, that's where I'm heading right now. I > don't really know what I'm > doing here, just blindly stumbling around trying to > find something that > works. > > I'd post my config, but I can't get access to it > right now (its at home). > > This is with Whidbey .net wsdl. > > Does that help any? > > James > > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
