Someone e-mailed me off-line and pointed out that I post UML diagrams on my blog fairly regularly. He wanted to know what tool I use for this. In the process, his e-mail reminded me that I had written a post back in March of 2009, where I said that an upcoming post would talk about this. Promises, promises!
Actually, now is a really good time to have this conversation because with the work I am doing on the Exchange Web Service code, I have just finished revamping my internal infrastructure to support the equipment and software I need to do the job. So this is going to be a two-part article. In this part, I’ll tell you about the software development components that I use. In the next part, I’ll tell you about the infrastructure components. The problem is that you need to understand some of the details of why, so I’m going to start with a little background.
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.
A couple of months back, a gentleman who has now become a friend and business partner, came to me and asked me if there was any way to get at all the calendar items in his sales organization’s calendars with the intention of integrating it with his Progress OpenEdge CRM system. Jim is using Exchange 2007 for his e-mail and calendaring solutions.
I was aware that Microsoft had released a new API for Exchange in Exchange 2007 called Exchange Web Services (EWS), and so I said that I needed to do a little research on the API, but I was pretty sure that it was possible. Sure enough, MSDN has some documentation of the API and Microsoft is touting it as the replacement for all APIs that communicate with Exchange. Web Services – how hard can it be?
As I alluded to in my post yesterday, I have done a lot of work around Content Management Systems over the last few weeks. The research that I did was actually not supposed to happen right now, but necessity is the mother of invention and sometimes providence has its hand in what we do. Back [...]
A little while ago I wrote an article on my blog about Joomla. I have had a few off-line comments about the article and as they were not written here I have decided to treat them as private responses and not publish the author’s names and their comments. But there were some very valid suggestions made [...]