Accessing Java Web Service

[srpatna]

I am trying to access Web Service of a Vendor. Its built using Java on
Weblogic.
Connection is restricted to users with client certificate provided by them
and
NOT from any recognised authority.

The Web Service setup at the vendor does not allow us to browse the wsdl or
xsd. They have provided us the wsdl for to use.

My problem is I am unable to compile the wsdl using wsdl.exe because it gives
me an error message tht the xsd file is missing. Additionally I am unable to
connect to the web service via .NET get a connection timeout. I can use the
browser and see the connection in progress because it requests a client
certificate and connection is done.

Can anyone please help me clarify the following.
1. Does .NET have issues with client certificates issued by a CA not part of
the
trusted list.
2. How do we convert the wsdl to get the proxy file.

Vendor on their part say all users who have used java for implementation have
been using the service without any issue. Any changes at the vendor end is
not possible.

[Keenan Newton]

..Net uses the same mechanisms as Internet Explorer does for making HTTP
requests. With that the CA needs to be in the trusted list for the
user making the request. If you have multiple users accessing this web
service I suggest creating a service agent that will make the requests
for your users on their behalf. Think of a service agent as the same
thing as a data access component talking to a database but in this case
it will talk to a web service.

As for the Wsdl issues, man if i had a nickle for everytime I have seen
someoen have problems consuming a java web service in .Net, I would be
retired in the cayman islands right now. First, in my mind the easiest
way to get the wsdl into a proxy class, and to dump it on some local
site, and let Visual Studio do the work. I am assuming this is what
you are doing, but I could be wrong. Generally the xsd's are created
for typed datasets by the Visual Studio IDE, so I am not sure why it
says it is missing.

As for the vendor, if they could not support a .Net web service which
in reality should be only minor tweaks on there side. i would not do
business with them. Any one that says, well it works with Java, missed
the whole concept of a web service in the first place.

Anyways. the community here would need to see the wsdl to try to help
you find a resolution. So if you can please share it, so that we may
help.