Now that we have succeeded in creating, updating and deleting calendar items and mastered Exchange Impersonation, it’s time to turn our attention to having Exchange notify us about what it is doing. Part 4 of this series is going to provide a detailed code walk-through of some code that leverages the Subscription API.
The example includes two code examples – one for Java programmers and one for OpenEdge programmers. The OpenEdge version writes updates through the OpenClient via the OpenEdge AppServer to an OpenEdge database.
Exchange Web Services – Subscriptions and Notifications
Apr 26
Posted by Bruce Gruenbaum in Commentary, Exchange Web Services, Java, OpenClient, OpenEdge, OpenEdge AppServer, Web Development, n-tier Development | 10 Comments
It’s been a really busy week since I posted my first post on Exchange Web Services. I have learned a lot in that short period of time that I want to share with you. Whether you are an OpenEdge, Java or .NET developer, I think this post is going to have some information for all of you.
In my first post, I told you about the background story – I need to enable an OpenEdge CRM application to create, modify and delete calendar and task items in Microsoft Exchange. I also need Exchange to let me know any time a calendar or task item is changed so that I can update the OpenEdge database accordingly. Simple use cases.
When I left off last week, my next step was to get Exchange subscriptions working, and, boy, what a trip that has been.
Tags: .NET, C#, Dynamic OpenClient, EWS, Exchange EWS, Exchange Web Services, Java, Java 5, Java OpenClient, Microsoft Exchange 2007, OpenEdge, OpenEdge AppServer, OpenEdge OpenClient, Progress OpenClient