id and comp

[phingers]

I'm trying to update a calendar id, or cancel it, I see the ID portion of it, and that is the ID from my create, but what is the comp="" value?

I'm having trouble following that portion. Any pointers? I've read all the soap.txt files, and am still stumped.

Thanks.

[jholder]

Hi Phingers-
I just had a look at the soap.txt file in the SVN. The SVN is out of date.

Here are the latest SOAP docs. Also, we have a 4.5.8 source tar with the latest SOAP docs.

Here they are:
http://files.zimbra.com/blog/soap-tmp/soap.txt
http://files.zimbra.com/blog/soap-tmp/soap-calendar.txt
http://files.zimbra.com/blog/soap-tmp/soap-admin.txt
http://files.zimbra.com/blog/soap-tmp/soap-wiki.txt
http://files.zimbra.com/blog/soap-tm...-extension.txt
http://files.zimbra.com/blog/soap-tmp/soap-waitset.txt

I noticed in the soap.txt there was more about the comp tag & exceptions:

// CREATING EXCEPTIONS
// --------------------
//
// Just like CreateAppointment, except that instead of specifying a target FOLDER, you
// specify an existing PID and component-number
//
// *** If id= and comp= are set, then you are creating an EXCEPTION:
//
//   The default invite for the appointment MUST have a recurrence rule....
//      otherwise you should just be using ModifyAppointment!
//
//   EXCEPTION_ID is start-time for the particular instance you are overriding
//     EXCEPTION_ID MUST be some instance that matches the default-invite for
//     the appointment...that is, it MUST NOT BE the start time of the exception!
//
//   **The above is important**   So let me explain:
//
//   Given an appointment, happens every Wednesday @ 9am, with an exception that moves
//      it to 10am on 6/22
//
//   So our instances for June, 2005  are:
//       6/1 9am
//       6/8 9am
//       6/15 9am
//       6/22 10am (an existing EXCEPTION)
//       6/29 9am
//
//  So, if a user clicks on the 6/22 10am appointment and wants to modify it, you MUST NOT
//  try to use <CreateAppointmentExceptionRequest> to modify it!
//  You MUST use ModifyAppointmentRequest instead!!!
//
//  On the other hand, if a user clicks on the 6/15 9am appointment and wants to modify it,
//  then this is the right API to use.
//

let me know if this doesn't help.

john

[phingers]

John - appreciate the info, I will try to remember to come in and update these posts. Basically from my review and a few emails with support.

COMP is not used currently, its basically stubbed out to be used in the future.

My new issue, is documented, here: http://www.zimbra.com/forums/develop...html#post62343

I have no idea as to why this is occurring?

Thanks.