Hi, Please see my comments inline
Currently ADB binding doesn't supports complex type extensions. Thats absolutely brokes work for Salesforce Apex API 8.0 (partner.wsdl). And I really expect the fix of that.
AFAIK ADB does support complex type extensions ! It had problems with the simple type extensions (and we got a significant contribution from GSOC for that) and I'm guessing Amila is working on whatever is remaining.
Xbeans databinding support enterprise wsdl of Salesforce, but unfortunatelly it doesn't supports partner wsdl due to xmlbeans databinding doesn't supports xsd:any feature. Although xmlbeans 2.2.0 which is used by Axis2 1.1.1 supports xsd:any (see http://xmlbeans.apache.org/docs/2.0.0/guide/conHandlingAny.html). Is any workaround to make Salesforce Apex API 8.0 (partner wsdl) workable with Axis2.
I'm not getting you here. Once the XMLBeans classes are generated, they shouldn't be different from the classes generated by standalone XMLBeans compiler (scomp). You can use the generated XMLBeans classes as you would do with XMLBeans classes that are generated in any other way. If not there is a problem :)
Jibx databinding currently also doesn't support xsd:any. Is it feasible to use JAXB bindings for that? So as I can see Axis2 totally doesn't support Salesforce partner wsdl. Can you provide some approximately estimate when Axis2 will be feasible for Salesforce? P.S.: Expect you kind advise what databinding is the best for WS client/server? I saw very good performance for JAXB bindings (http://wso2.org/library/588). -- Thanks in advance, Yura.
-- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
