https://bugs.meego.com/show_bug.cgi?id=22164
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2011-08-01 11:18:12 UTC ---
Fixed:
commit 44629fdd59f287252c4b4bcb09f660bbaff7aaf2
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Mon Aug 1 13:05:04 2011 +0200
WebDAV: fixed item operations without configuration (BMC #22164)
Item operations like --print-items failed if the configuration didn't
exist:
[ERROR] : virtual read-only configuration node, cannot write property
webDAVCredentialsOkay = 1
This was caused by trying to write the webDAVCredentialsOkay property
into a temporary, read-only configuration. The fix is to check for
read-only configs before attempting to use the property.
Alternatively it would have been possible to catch exceptions, but it
is not obvious which errors can be ignored.
commit 648307a7156e1ed7ddb317d42dc877c14ba6b947
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Mon Aug 1 12:55:47 2011 +0200
ConfigNode: added isReadOnly() (needed for BMC #22164)
Some users of ConfigNode (like the WebDAV backend) need to know
whether setting a optional property will succeed before attempting
it. When they know that it fails because the node is read-only, they
can skip setting it.
The alternative would be to throw a well-defined exception and catch
it, but that is not in line with the SyncEvolution design. Exceptions
should be for real, unexpected errors.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Medium
Keywords:
Status: RESOLVED
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: 1.2
Flags:
Changed: Status Resolution
--------
https://bugs.meego.com/show_bug.cgi?id=22164
--
Configure bugmail:
https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.