asked on

I added a JAVA SOAP web service(MTOM) to my project using add web services but all methods are exposed as classes only

Hi I'm using VS2013, asp.net and C#,
The vendor finally fixed something in their wsdl and now I can fincally add it using just the Add Service Reference. However, the problem is now all the methods are exposed as classes. I can't even use them to execute now. is there something on my end that I need to do?
Attached is the binding section, generated automatically by VS.

Thank you.
binding.txt

ASKER CERTIFIED SOLUTION

ste5an

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

lapucca

ASKER

Attached is the screen shot of when I add Service Reference of this Java service and the screen shot of Object browser of the service added. When adding the service, in the screen shot you see that it only exposes the classes when they should be methods. In the object browser it shows them all as classes as well. I do not know what that PotType is but it's directly under the service when I add it and from it under are all the classes but no method. For example, getProtocol is supposed to be a method but it's a class here.
Thank you.
OBJECT-BROWSER.png
SERVICE-REFERENCE.png

SOLUTION

mccarl

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

lapucca

ASKER

Okay, I figure out a way to invoke these classes are static classes. It's just odd that VS exposes them as classes and not methods. I also had to create a proxy class to use this static classes. Is this normal to have them as static classes?

Also, I had to add this to my web.config, "<transport clientCredentialType="Basic" />". Should this be generated along with other part of all the information under the <system.serviceModel> based on the wsdl?

I think this is a poorly formed wsdl that we got. I mean, we had to modify the endpoint myself, it has 2 binding name (that can't be normal) and it's also missing the clientCredentialType (shouldn't this be auto-generated based on WDSL?

Appreciate some confirmation on my above suspicion if this is a ill-formed wsdl.

Thank you.
wsdl.xml