Coilcore, thanks for your comments. WSDL for our SOAP api would be nothing more than a schema since all the interactions and dependencies of the commands can't be expressed in WSDL. While I can understand how you feel WSDL is mandatory it doesn't seem to be holding back either our internal development or that of our partners/users/customers based on the integrations I've seen. That said if the community thinks this is important enough then they will create a WSDL for our SOAP. Just like the folks who thought we needed a JSON adaptor for Ruby on Rails. So if someone feels the need to do this we are always here to help and will take the contribution seriously. If it's useful enough may even include it in future Zimbra releases.
Did you look at the com.zimbra.cs.client.* pkgs? This is a basic Java client that we use internally in a QA and performance test framework. |