Axis 1.2.1 <-> .NET 1.1 interoperability issue && various other problems

["Uss, Jonathan" <Jo...@ngc.com>]

Hello,

I'm creating a web service in Java using Axis 1.2.1, and our partner
company is using .NET to communicate with the web service.  I'm using
soap attachments to send and receive binary data along with a
complexType data structure.

There are several issues with it, and I'm hoping that the wonderful
people on this list will be able to help me solve them :-)

First, when I use WSDL2Java, the generated deploy.wsdd file contains '>'
characters in front of the types, which causes axis makeTypeElement()
faults when trying to view the wsdl dynamically.  I can remove those and
that part works, but I was wondering if that has any consequences
attached to it.

Next, the generated deploy.wsdd needs to be modified and the '<service
name=... style="document"...' needs to be corrected to
'style="wrapped"', otherwise I get errors when trying to invoke my web
service.  Again, the necessity of this fix makes me feel uneasy that my
wsdl is somehow broken.

Finally, once everything is said and done the above web service works
for Axis generated Java clients.  However, when our partner company
tries to consume the wsdl (with .NET) they're getting the following
errors:
// CODEGEN: The operation binding 'addMyData' from namespace
'com.example.MyDataService' was ignored.  Missing soap:body input
binding.
// CODEGEN: The operation binding 'getMyData' from namespace
'com.example.MyDataService' was ignored.  Missing soap:body output
binding.

I've heard mixed information that DIME is required for .Net soap
attachments but also that MIME also works.  I have no experience with
soap attachments and .NET and have no way to test it out myself and was
wondering if anyone can give me a straight answer of what I need to do
to get this all to work.

Note: I've also tried to get the interop working asking our partner
company to use the axis generated http://url:8080/service?WSDL style
link, and they get the following errors:

Schema validation warning: The 'base' attribute is either invalid or
missing.

Warning: Schema could not be validated. Class generation may fail or may
produce incorrect results.

Error: Unable to import binding 'DataServiceSoapBinding' from namespace
'(namespace)'.
  - Unable to import operation 'addMyData'.
  - Schema with targetNamespace='com.example.MyDataService/types' has
invalid syntax.
  - The 'base' attribute is either invalid or missing.

However, I have a feeling that the error and this approach is not the
right way to go, because the generated wsdl file is missing the
<mime:multipartRelated> tags and my SwA setup, so the .NET client
wouldn't even know about the soap attachments?

Any help with anything mentioned would be greatly appreciated.  Thanks!

I've attached my wsdl file.

--
Jonathan R. Uss
E-2C Software Engineer
Northrop Grumman Integrated Systems
925 South Oyster Bay Road
Bethpage, NY  11714-3582
M/S: G01-014
Phone: (516) 704-3922