[hillman]

Weird.

I haven't played with using anything but the bundled version of Java with the sync4j server, but I'm running the admin console on a completely different box (a Win XP box), and it "just worked".

With the logging, I was able to get logging from all components of the server (the core engine and the zimbra module) by just setting the top-level logging level. The default is "INFO" which is fairly terse. Setting it to "ALL" gives you all the gory details suitable for debugging.

Re: problems with Blackberry client. I've done a bit more testing at our site with my colleague's device (a BlackBerry Curve - 8310). In short, none of the free clients work with the connector so far. The older sync4j clients are sending their data in what appears to be base64 encoding, which the sync4j server doesn't expect and can't deal with. The newer Funambol client uses SyncML version 1.2 which the Sync4j server doesn't support, so the server throws an exception.

We had some success with the Nexthause SyncML client, but it's a commercial client ($30). We bought it to test against Oracle's SyncML interface, so the testing with Zimbra is just a bonus. Using that client, we were able to sync contacts (to some extent), but not calendars. Testing is on-going. Unfortunately we can't really do any more testing with the free clients until the Zimbra connector is ported to Funambol v 3 & 6 (which add support for SyncML 1.2)

Update: The reason the Nexthause client couldn't sync the calendar is because the server isn't sending a version string with its VCALENDAR updates. Since there are now 2 versions of VCalendar, it makes the update ambiguous, so the client gives an error. This may not be fixable from the Zimbra module, which means it'll remain broken until it gets ported to Funambol v3/6 also