[#6939] Funambol Blackberry SyncML plugin 6.6 GA fails to connect
Summary Funambol Blackberry SyncML plugin 6.6 GA fails to connect
Queue SyncML
Type Bug
State Resolved
Priority 1. Low
Owners Jan Schneider <jan (at) horde (dot) org>
Requester tmalone (at) lancer-ins (dot) com
Created 06/16/2008 (159 days ago)
Due
Updated 07/13/2008 (132 days ago)
Assigned 07/07/2008 (138 days ago)
Resolved 07/13/2008 (132 days ago)
Attachments sync-bb.tar.gz Download
respuri.diff Download
syncml.log.tar.gz Download
Milestone 3.2.2
Patch No

History
07/13/2008 Jan Schneider State ⇒ Resolved
 
07/10/2008 Jan Schneider Comment #10
Taken from Karsten Fourmont
Taken from Horde DevelopersHorde Developers
Reply to this comment
My fault, I forgot to commit the code the actually creates the RespURI url.
07/10/2008 CVS Commit Comment #9 Reply to this comment
07/07/2008 tmalone (at) lancer-ins (dot) com Comment #8
New Attachment: syncml.log.tar.gz Download
Reply to this comment
I applied your patches and was not able to make a successful sync.  It 
still appears that the respURI is no included in the Sync Header.

I have attached a tar file of the sync logs for the failed session.
07/07/2008 Jan Schneider Comment #7
State ⇒ Feedback
Reply to this comment
Can you try if what I committed works for you? My SyncML client is 
broken at the moment.
07/07/2008 CVS Commit Comment #6 Reply to this comment
07/06/2008 Jan Schneider Milestone ⇒ 3.2.2
 
06/17/2008 Jan Schneider Assigned to Jan Schneider
 
06/17/2008 Chuck Hagenbuch State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
Assigned to Karsten Fourmont
 
06/17/2008 tmalone (at) lancer-ins (dot) com Comment #5
New Attachment: respuri.diff Download
Reply to this comment

Please provide the sync log files.
The sync log files are attached.

However, as I indicated below the fix was just a matter of
uncommenting the RespURI section that was commented out in
lib/SyncML/XMLOutput.php.
Here is a patch that adds the RespURI back to XMLOutput.php.
06/17/2008 tmalone (at) lancer-ins (dot) com Comment #4
New Attachment: sync-bb.tar.gz Download
Reply to this comment
Please provide the sync log files.
The sync log files are attached.

However, as I indicated below the fix was just a matter of 
uncommenting the RespURI section that was commented out in 
lib/SyncML/XMLOutput.php.


06/16/2008 Jan Schneider Comment #3
State ⇒ Feedback
Reply to this comment
Please provide the sync log files.
06/16/2008 tmalone (at) lancer-ins (dot) com Comment #2 Reply to this comment
OK my initial investigation was a little off base.  It seems that the 
funambol client is looking for the RespURI in the SyncHdr section from 
the server.

In the SyncML/XMLOutput.php the RespURI is specifically commented out and
prevented from being sent.

Re-adding the RespURI fixes the funambol client problem.

When trying to use the latest version of the Funambol Blackberry
SyncML plugin (version 6.6 GA) the client fails to sync.  The error
message returned from the client is "Cannot find the Response URI in
server response."

The error seems to come out of the funambol source code file:
/funambol/client-api/j2me/syncml/src/com/funambol/syncml/spds

The comment right before the error message is "// Get the server URL
with the session ID".  It would seem that the funambol client is
expecting some sort of session ID to be embedded in the server URL
returned by horde.
06/16/2008 tmalone (at) lancer-ins (dot) com Comment #1
Patch ⇒
Milestone ⇒
Queue ⇒ SyncML
Summary ⇒ Funambol Blackberry SyncML plugin 6.6 GA fails to connect
Type ⇒ Bug
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Reply to this comment
When trying to use the latest version of the Funambol Blackberry 
SyncML plugin (version 6.6 GA) the client fails to sync.  The error 
message returned from the client is "Cannot find the Response URI in 
server response."

The error seems to come out of the funambol source code file: 
/funambol/client-api/j2me/syncml/src/com/funambol/syncml/spds

The comment right before the error message is "// Get the server URL 
with the session ID".  It would seem that the funambol client is 
expecting some sort of session ID to be embedded in the server URL 
returned by horde.