Hello Jake, If the secondary calendar is owned by you, you should have write access to it. However, if it's owned by someone else, there's a possibility that you have only read access to the calendar. Either way, you can check this by logging into the calendar UI using the same account which you are using through the API and inserting an event.
Also, you can get more information about the ServiceException by using the getResponseBody public method. See the javadoc for more information: http://code.google.com/apis/gdata/javadoc/com/google/gdata/util/ServiceException.html Please let me know if one of these methods helps yield more information about the problem you are experiencing. Cheers, -Ryan On Jan 19, 7:07 am, "Jake" <[EMAIL PROTECTED]> wrote: > Is it possible that this non-default calendar is not authorised > correctly for writing? Might I need a session token or something? All > I'm doing currently is setting the credentials for the CalanderService. > Would this account for read-only-ness? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
