{"id":66581,"date":"2014-08-28T09:00:54","date_gmt":"2014-08-28T16:00:54","guid":{"rendered":"http:\/\/www.microsoft.com\/?p=66581"},"modified":"2024-08-13T12:27:13","modified_gmt":"2024-08-13T19:27:13","slug":"open-sourcing-exchange-web-services-ews-java-api","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/2014\/08\/28\/open-sourcing-exchange-web-services-ews-java-api\/","title":{"rendered":"Open sourcing Exchange Web Services (EWS) Java API"},"content":{"rendered":"\n
Victor Boctor is a principal architect on the Exchange team<\/em>.<\/p>\n\n\n\n Our last release of Exchange Web Services Java API was in January 2013 (see blog post<\/a>). Since then, we\u2019ve received feedback about several issues with our model for supporting the Java client APIs. These issues include:<\/p>\n\n\n\n Based on this feedback, we decided to do the work to make EWS Java API a true open source project. To accomplish that, we made the following changes for this release (1.3):<\/p>\n\n\n\n These improvements enable the Exchange community of Java developers to contribute and help drive the project. You will also be able to leverage the latest dev or stable releases as you need them to enable your scenarios.<\/p>\n\n\n\n Some of the other modifications for the 1.3 release\u2014so far\u2014include:<\/p>\n\n\n\n These improvements should enable you to effectively collaborate on the project. So go ahead and submit your private fixes as GitHub pull requests to make your contributions to the 1.3 release and beyond!<\/p>\n\n\n\n We\u2019ve also made available an Office 365 REST API<\/a> with OAuth 2.0 support<\/a> and an Android SDK<\/a> that uses these REST APIs. This new API is recommended for developers who are targeting Office 365 customers, and you can continue to use the EWS Java API if your customers have on-premises Exchange, or the functionality you need isn\u2019t yet offered as part of the REST API.<\/p>\n\n\n\n Thank you for your interest in Exchange. We welcome any feedback you have on our APIs and look forward to your using and improving them.<\/p>\n\n\n\n \u2014Victor Boctor, Twitter: @vboctor<\/p>\n","protected":false},"excerpt":{"rendered":" Our last release of Exchange Web Services Java API was in January 2013. Since then, we\u2019ve received feedback about several issues with our model for supporting the Java client APIs. Based on this feedback, we decided to do the work to make EWS Java API a true open source project. These improvements enable the Exchange community of Java developers to contribute and help drive the project. <\/p>\n","protected":false},"author":3368823,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ms_queue_id":[],"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","footnotes":""},"categories":[],"tags":[],"audience":[4081,4102],"content-type":[4034],"product":[4048,4036],"coauthors":[4437],"class_list":["post-66581","post","type-post","status-publish","format-standard","hentry","audience-enterprise","audience-small-and-medium-business","content-type-news","product-exchange","product-microsoft-365","review-flag-1-1680288349-853","review-flag-2-1680288349-543","review-flag-3-1680288349-124","review-flag-lever-1680288347-881","review-flag-new-1680288347-871"],"yoast_head":"\n\n
<\/figure>\n\n\n\n
\n
\n