The EWS Java API 1.2 is now available, with added support for functionality in Exchange Server 2010 SP2. It also includes an important update to the license terms that affects what you can do with the source code and the redistribution terms.

Feature-wise, we’ve implemented the following updates to the EWS Java API, which might be of interest to you:

  • The API now targets the Exchange 2010 SP2 version of the schema.
  • We've added synchronous request-response pattern implemented for handling communication with the service.
  • The FullContactData option of the ResolveNames operation now includes new directory properties.
  • Streaming notifications includes the following updates :
    • Subscription creation no longer causes a deadlock.
    • The StreamingSubscription object no longer causes a crash when the Microsoft.Exchange.Data.Storage.MailboxSession object is disposed.
  • Get password expiration date functionality has been implemented.
  • Logging capability for the HTTP headers is now included.
  • The HTTPHeader collection now correctly populates with the response HTTP headers.

For more information about what's new in the EWS Java API 1.2, see the release notes included in the download.

In some ways, the biggest change is that we have updated the license terms to give you a bit more freedom to customize the EWS Java API. The license updates enable you, the licensee, to do the following:

  1. Modify the source code to fix bugs and make improvements in your own private branch of the code.
  2. Redistribute in binary format only, as part of your application, the EWS Java API, with any changes that you have made to the original source code.
  3. Submit bug fixes or source code to Microsoft. We can incorporate the fixes into future API releases, at our discretion.

As always, be sure to review the authoritative license terms for details.

Hopefully, these more flexible terms will open more possibilities for you to incorporate Exchange integration into your products. This update has been a long time coming, so start up your IDE, rev up your (private) code repository, and take off using the latest EWS Java API!