Results 1 to 3 of 3

Thread: SOAP: how to demand <change>?

  1. #1
    ljm
    ljm is offline Project Contributor
    Join Date
    May 2006
    Posts
    81
    Rep Power
    9

    Default SOAP: how to demand <change>?

    I'm wondering what to do to guarantee a <change token="xxx"> in the <context> element of a SOAP response? I particularly want the change id/token in relation to a <ModifyBlahResponse>

    Currently, my SOAP client is issuing requests using:
    <context> <nonotify/><noqualify/></context>
    which seems to mostly work fine. Except for one server recently encountered where the (successful) server response contained a completely empty <context> element. I don't have access to the particular server so it's bit tricky to experiment with.

    So: what's the right/best way to issue a request that will guarantee a <change token='xxx'> in the response?
    Zindus - contact sync for Thunderbird and Zimbra

  2. #2
    ljm
    ljm is offline Project Contributor
    Join Date
    May 2006
    Posts
    81
    Rep Power
    9

    Default

    As far as I can tell from reading soap.txt, the server should provide a <change> element in it's response. Otherwise it's a server bug.

    This issue is proving to be an ongoing source of bugs for zindus users. So if my understanding about this is wrong, it would be great is someone could clarify.

    ie. if <change> is optional in the server response and there's something a client can/should do to force it, it would be great to know that.
    Zindus - contact sync for Thunderbird and Zimbra

  3. #3
    luh3417 is offline New Member
    Join Date
    Aug 2008
    Posts
    3
    Rep Power
    7

    Default

    Quote Originally Posted by ljm View Post
    As far as I can tell from reading soap.txt, the server should provide a <change> element in it's response. Otherwise it's a server bug.

    This issue is proving to be an ongoing source of bugs for zindus users. So if my understanding about this is wrong, it would be great is someone could clarify.

    ie. if <change> is optional in the server response and there's something a client can/should do to force it, it would be great to know that.
    I am here because I got this error out notice. I have reset and I still get it. This bug seems very old. Is there a fix?
    Thanks

    You have encountered a known Zimbra bug: SOAP: how to demand <change>?

    Suggest 'Reset' followed by 'Sync Now'.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. XSD/WSDL Files for the SOAP Server?
    By photoadrian in forum Developers
    Replies: 5
    Last Post: 12-23-2012, 02:32 AM
  2. Delete a calendar appointment via SOAP
    By kkuilla in forum Developers
    Replies: 5
    Last Post: 04-28-2010, 03:07 AM
  3. Soap Errors for multiple users
    By rexmora in forum Zimbra Connector for Outlook
    Replies: 9
    Last Post: 09-03-2009, 02:24 PM
  4. Jar For Soap Client
    By wcameron in forum Developers
    Replies: 19
    Last Post: 06-03-2009, 02:04 PM
  5. zmzimletctl deploy zimbra_posixaccount.zip - ERROR -
    By todd_dsm in forum Administrators
    Replies: 0
    Last Post: 04-02-2009, 01:41 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •