View source for Calendar:WCAP Provider

[[Calendar:Feature_Implementations| <<Back to Features]]

==Using==



===Subscribing To Your Calendar===
The Sunbird/Lightning ''Create New Calendar'' wizard comes up with a third Format type for remote calendars (''Sun Java System Calendar Server (WCAP)'').  As location, provide a <code>HTTP</code> or preferrably <code>HTTPS</code> URL to a [http://www.sun.com/software/products/calendar_srvr/index.xml Sun Java System Calendar server].
<pre>
http://sd-calendar.staroffice.de/
</pre>
You can encode your common user-id into the url which will be used for the login prompt, e.g.
<pre>
http://jdoe@sd-calendar.staroffice.de/
</pre>
After creation, you need to switch the view on for this calendar in the ''Calendars'' list.

===Login===
For login, you will be asked for a pair of ''UserName/Password''.
If you don't pass login, you will be asked again.
If the calendar server does not support <code>HTTPS</code>, you will be asked whether to continue the login.

===UI===
If you create items, keep care to have the correct calendar selected and checked in the ''Calendars'' list, because this will be the one for insertion.  It
can be confusing if the selected calendar is not shown (unchecked), i.e.
you won't see your newly created event.  IMO we have to improve this.

==Logging==
===Log Level===
The provider can log for diagnose purposes.
Logs go to the <code>js</code> console, eventually to <code>stdout</code> (if <code>user_pref("browser.dom.window.dump.enabled", true);</code>) or
[[#Log_File|log file]].

Four log levels are defined:
*0 &rarr; no logging (release, default)
*1 &rarr; some logging, connection etc., but no calendar data
*2 &rarr; verbose log
*3 &rarr; very verbose log

You can set the log level your <code>user.js</code> in your profile:
 user_pref("calendar.wcap.log_level", ''n'');
or via ''Tools&rarr;Options&rarr;Advanced&rarr;General&rarr;Config Editor...'' (Thunderbird 2, Unix) and even change it without restarting Thunderbird.

===Log File===
You can specify a log file. Logs are always appended to the specified file.
 user_pref("calendar.wcap.log_file", "''/system/path/to/log/file''"); // *nix
 user_pref("calendar.wcap.log_file", "''c:\\system\\path\\to\\log\\file''"); // Windows
 user_pref("calendar.wcap.log_file_append", true); // whether log should be appended, default is false (truncate)

==Trouble Shooting==
*Some Calendar server versions cause trouble using the <code>get_calprops.wcap</code> command. If you encounter trouble with your version, the WCAP provider has a workaround using the <code>search_calprops.wcap</code> command. You can switch the usage setting pref
 calendar.wcap.no_get_calprops &rarr; true


[[category:calendar|WCAP Provider]]