Sunday, March 28, 2010

Consuming Exchange Web Service from Java – Proxy Generation

Download the WSDL and supporting files from your exchange server. Replace with your exchange server details.

Add service definition to Services.wsdl file

<wsdl:service name="ExchangeServices">
    <wsdl:port name="ExchangeServicePort" binding="tns:ExchangeServiceBinding">
      <soap:address location=""/>

Modify the import statement in types.xsd file as follows.

<xs:import namespace="" schemaLocation="" />

Now we are good to build the proxy files. Issue the following command to generate the ANT build file and java source files. Once you make further changes to the schema files and do not want to overwrite the build.xml file, you can use ‘--noBuildXML’ option for wsdl2java.

wsdl2java -u -uri Services.wsdl

When you build the files using, ANT, it gives compilation errors. I am not sure, why Axis fail to generate the files correctly. What I have done is to define the member variable for ‘localPathTracker’ in each of those files.

Consuming Exchange Web Service from Java – Setup Environment

  • Install following
    • JDK (1.5 or above)
    • Apache Axis2 (I used Axis 1.4.1)
    • Apache Ant
  • Configure following environment variables
    • AXIS2_HOME
    • ANT_HOME
  • Append following to PATH
    • %JAVA_HOME%\bin;%AXIS2_HOME%\bin;%ANT_HOME%\bin
  • Ensure that you can run the following commands from command line
    • java
    • wsdl2java
    • ant

Thursday, March 25, 2010

Consuming Exchange Web Service from Java

I had to get the Exchange Web Service (Exchange Version: 2010) APIs consumed from a Java program. Here is a set of preconditions, that I had, to start working on this.

  • Need to use Apache Axis2 web service stack, version 1.4
  • Consume mail and calendar APIs from Java

I did some research on any existing work for the same. I couldn’t find anything specific for Axis2. However, I found this great wiki page from imap2exchange project, which explains how to do it from Metro. In this blog series, I am trying to put together the sequence of actions I had to do to get the proxy code working from Axis2.

To get the email from user’s inbox, I had to do the following sequence.

  1. Setup your development environment
  2. Customize the WSDL & Schema to get Axis2 generate the proxy
  3. Fix compilation issues of Axis2 generated proxy
  4. Remove some namespace attaching in the request to avoid EWS complaining about the request format
  5. Edit the schema to resolve bugs in Axis2, regenerate proxy code and fix compilation issues

Back to blogging

Title could be little confusing. When I say back to blogging, I wasn’t blogging so frequently earlier. So that is probably a partially correct sentence. What I want to say is, I am starting to blog again now. :)