The application should be an example web application demonstrating how to synchronize "Outlook like" recurring calendar entries with events in [url removed, login to view] through their web services API. This application should also synchronize the recurring event from [url removed, login to view] to MS Exchange through the MAPI API. Since understanding the architecture is important for me, source comments are highly appreciated.
1. On a simple web page, create a recurring event to be stored in [url removed, login to view] and synchronized to Exchange including the ability to update, modify and delete the recurring event through the web page into both [url removed, login to view] and Exchange.
2. On a simple web page, a) selecting the recurring event from a list of currently stored recurring events in [url removed, login to view] for that user, b) then be able to read, update, delete the contents, date, time of the recurring event selected from the list.
3. When reading, updating, deleting the selected recurring event have the choice to either update all recurring events in the series or update just the next task in the series.
4. When the recurring event is updated, deleted in part 3 above, after updating the events in [url removed, login to view], synchronize these events from [url removed, login to view] to Exchange at the same time using MAPI.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
1. Needs to conform to a Model, View, Controller architecture. Needs to utilize the full MAPI API.
2. Would prefer J2EE - using JSP, servlets and EJBs deployable in a Tomcat / JBoss environment. However if MAPI will be difficult in this platform, then
3. DOTNet Website using ASP.Net, C+/C# wrapping MAPI is also fine.
4. For testing, I will provide either a full DotNet environment or Tomcat on JBoss J2EE application server, where the seller can deploy their application. However for development purposes, I would prefer the developer to have their own environment.
5. From a [url removed, login to view] perspective, please get yourself a free developer edition by going to [url removed, login to view] and sign up for a free developer edition in which to code against the webservices API. Documentation and help is available free also from [url removed, login to view]
6. Expect the latest version of Exchange and use MAPI to communicate.