Announcement

Collapse
No announcement yet.

webdav update still broken for kde4.4 kontact client

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • webdav update still broken for kde4.4 kontact client

    I just wondered if sync works for the kontact from the latest kde4.4 and 4.5 releases. Earlier, there was a bug with missing "last_modified" field, which prevented event updates work. Ok, I tried it with newer 4.4 & 4.5 versions, the "last_modified" field is really included within update request now but updates stil do not work. I can read all events and add new events but still cannot edit/modify existing ones. Huh ?

    Looking more into detail, there seems to be some problem with the folder_id field.
    One can see following in the log:

    Code:
    SEVERE: WEBDAV-0001 Category=8 Message=Invalid value in element "folder_id": . exceptionID=-606037176-16051
    WEBDAV-0001 Category=8 Message=Invalid value in element "folder_id": . exceptionID=-606037176-16051
            at com.openexchange.webdav.xml.XmlServlet.doPropFind(XmlServlet.java:282)
            at com.openexchange.tools.webdav.WebDavServlet.service(WebDavServlet.java:159)
            at com.openexchange.tools.webdav.OXServlet.service(OXServlet.java:125)
            at com.openexchange.webdav.PermissionServlet.service(PermissionServlet.java:104)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
            at com.openexchange.ajp13.najp.AJPv13RequestHandlerImpl.doServletService(AJPv13RequestHandlerImpl.java:504)
            at com.openexchange.ajp13.AJPv13Request.response(AJPv13Request.java:129)
            at com.openexchange.ajp13.najp.AJPv13RequestHandlerImpl.createResponse(AJPv13RequestHandlerImpl.java:316)
            at com.openexchange.ajp13.najp.AJPv13ConnectionImpl.createResponse(AJPv13ConnectionImpl.java:207)
            at com.openexchange.ajp13.najp.AJPv13Task.call(AJPv13Task.java:346)
            at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
            at java.util.concurrent.FutureTask.run(FutureTask.java:138)
            at com.openexchange.threadpool.internal.CustomThreadPoolExecutor$Worker.runTask(CustomThreadPoolExecutor.java:738)
            at com.openexchange.threadpool.internal.CustomThreadPoolExecutor$Worker.run(CustomThreadPoolExecutor.java:764)
            at java.lang.Thread.run(Thread.java:619)
    Caused by: WEBDAV-0001 Category=8 Message=Invalid value in element "folder_id": . exceptionID=-606037176-16050
            ... 15 more
    Caused by: java.lang.NumberFormatException: For input string: ""
            at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
            at java.lang.Integer.parseInt(Integer.java:470)
            at java.lang.Integer.parseInt(Integer.java:499)
            at com.openexchange.webdav.xml.XmlServlet.doPropFind(XmlServlet.java:280)
            ... 14 more
    So lets look at wireshark data:

    If we read the event by Kontact we get following from the ox-server:

    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <D:multistatus xmlns:D="DAV:" version="6.18.0-Rev7" buildname="Open-Xchange"><D:response xmlns:D="DAV:" 
    xmlns:ox="http://www.open-xchange.org">
    <D:href>400</D:href>
    <D:propstat><D:prop>
    <ox:object_status>CREATE</ox:object_status>
    <ox:start_date>1291461300000</ox:start_date>
    <ox:end_date>1291468500000</ox:end_date>
    <ox:location>here</ox:location>
    <ox:full_time>false</ox:full_time>
    <ox:shown_as>1</ox:shown_as>
    <ox:alarm_flag>false</ox:alarm_flag>
    <ox:uid>20ce8d61-6cf2-4cb3-a486-972aa46111e7</ox:uid>
    <ox:color_label>0</ox:color_label>
    <ox:title>test</ox:title>
    <ox:participants><ox:user ox:confirm="accept" ox:external="false">62</ox:user></ox:participants>
    <ox:created_by>62</ox:created_by>
    <ox:creation_time>1290952521000</ox:creation_time>
    <ox:modified_by>62</ox:modified_by>
    <ox:last_modified>1290953916455</ox:last_modified>
    <ox:object_id>400</ox:object_id>
    <ox:folder_id>225</ox:folder_id>
    <ox:private_flag>false</ox:private_flag>
    </D:prop><D:status>200</D:status>
    <D:responsedescription>OK</D:responsedescription>
    </D:propstat></D:response>
    </D:multistatus>

    Ok, so we got the folder_id = 225.

    An now the update request from Kontact:

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <D:multistatus xmlns:D="DAV:">
     <D:propertyupdate xmlns:D="DAV:">
      <D:set>
       <D:prop>
        <ox:object_id xmlns:ox="http://www.open-xchange.org">400</ox:object_id>
        <ox:client_id xmlns:ox="http://www.open-xchange.org">KResources_SLOX_Event_400</ox:client_id>
        <ox:last_modified xmlns:ox="http://www.open-xchange.org">1290952521420</ox:last_modified>
        <ox:title xmlns:ox="http://www.open-xchange.org">test1111</ox:title>
        <ox:note xmlns:ox="http://www.open-xchange.org"/>
        <ox:alarm xmlns:ox="http://www.open-xchange.org">0</ox:alarm>
        <ox:categories xmlns:ox="http://www.open-xchange.org"/>
        <ox:folder_id xmlns:ox="http://www.open-xchange.org">225</ox:folder_id>
        <ox:start_date xmlns:ox="http://www.open-xchange.org">1291461300000</ox:start_date>
        <ox:end_date xmlns:ox="http://www.open-xchange.org">1291468500000</ox:end_date>
        <ox:location xmlns:ox="http://www.open-xchange.org">here</ox:location>
        <ox:full_time xmlns:ox="http://www.open-xchange.org">false</ox:full_time>
        <ox:recurrence_type xmlns:ox="http://www.open-xchange.org">none</ox:recurrence_type>
       </D:prop>
      </D:set>
     </D:propertyupdate>
    </D:multistatus>
    ...written the same folder_id=225 back we got before and it is invalid ?

    Huh ??? Whats wrong here ? An OX server bug ?

  • #2
    Originally posted by sam View Post
    I just wondered if sync works for the kontact from the latest kde4.4 and 4.5 releases.

    [...]

    Huh ??? Whats wrong here ? An OX server bug ?
    When in doubt, please open a bug at bugs.open-xchange.com and don't
    forget to provide important details like which version of open-xchange
    you're using.

    Comment


    • #3
      Created bug report:

      Comment

      Working...
      X