Hi! I want to create java client for web-services provided by Exchange server 2007. When I tryed generate client stub from WSDL, following error appeared "failed to parse WSDL". I'm using JDK6 and JAX-WS for it. Where could be the source of an error? By the way if you have any recommendation or advices about using exchange web-services with java, I'll be happy. Thanks!
Which wsdl are you using?
http://Server/ews/services.wsdlhttp://Server/EWS/exchange.asmx?wsdl
- Joel
http://Server/ews/services.wsdl By the way. I've searched source of services.wsdl and there is no <wsdl:service> element at all! Why?!
Hi,
Did you manage to go farther in your research about creating a client for Exchange 2K7 using JAVA ?
I can give you a feed back about it, even if I did not succeed yet to use the interface provided in the wsdl file. I generated the java package using axis, and it worked fine, even if I had to correct a number of constructor in classes in order to propagate the correct inheritance. It seems that axis2 report a problem when generating the package, because the service tag is missing. Any way, using axis, you can get a package that works. The problem is that the generated interface does not really correspond to the one generated on .Net. It seems that every request required the following objects: ExchangeImpersonationTYpe & SerialiezdSecurityContextType. These are properties of the class ExchangeServiceBinding, but I don't know yet how to initialize them correctly.
Hope this information may help you. And If you have any feed back about what you tried...
This might help (regarding the Axis proxy generation)
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2199009&SiteID=17
And this regarding the wsdl:service element:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1998826&SiteID=17
Regarding the ExchangeImpersonationType and SerializedSecurityContextType (and MailboxCulture for that matter), they are all optional SOAP headers defined in the WSDL file. ExchangeImpersonation is only required when you wish to make an Exchange Impersonation call using a service account that has the rights to perform work on behalf of another account. The SerializedSecurityContext represents "Token Serialization" which allows Exchange Servers to talk to each other. It is not intended for 3rd party consumption (it does pretty much the same thing as Exchange Impersonation anyways).
If you can't pass in NULL for these in the constructor of your proxy class, you might want to remove the args from your autogenerated proxy classes and see if that works.
Hope this helps
David | Microsoft Exchange Web Services
P.S: Shameless plug :)
http://www.amazon.com/gp/product/0735623929/ref=s9_asin_title_1/105-0106176-5300466?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=center-1&pf_rd_r=12SCAG3EC9BDECEKATW8&pf_rd_t=101&pf_rd_p=278240701&pf_rd_i=507846