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
lapuccaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ste5anSenior DeveloperCommented:
Sure? Post the class view..
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lapuccaAuthor Commented:
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
0
mccarlIT Business Systems Analyst / Software DeveloperCommented:
Can you post the WSDL that the service publishes?
0
lapuccaAuthor Commented:
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
WCF

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.