3. Component Requirements, Constraints, and Acceptance Criteria
This component will implement all available API methods
This component will handle authentication.
This component will include a factory method.
This component will accept an array or Zend_Config object as construct parameter.
This component will use Zend_Soap_Client to wrap SOAP requests in WSDL mode.
4. Dependencies on Other Framework Components
Zend_Soap_Client
Zend_Loader
Zend_Config
Zend_Server
5. Theory of Operation
This component is used to call the Force.com web service. This will cover all API methods declared in the WSDL. This will work by instantiating a Zend_Service_Salesforce_Wsdl_SObject, assigning the parameters to that SObject, and passing that object as a parameter when creating the SOAP call.
<ac:macro ac:name="note"><ac:rich-text-body><p> The Community Review team recommends this proposal be accepted for inclusion in the Framework </p>
<p>We do provide a small item of feedback here based on the code which we can see so far.<br />
We would like to see the visibility of the methods and members of the classes reconsidered, as private is used widely, which would narrow the scope for extension. Also, we would like some of the method names to be reviewed, to be more consistent with the rest of the framework.</p></ac:rich-text-body></ac:macro>
1 Comment
comments.show.hideFeb 05, 2011
Ryan Mauger
<ac:macro ac:name="note"><ac:rich-text-body><p> The Community Review team recommends this proposal be accepted for inclusion in the Framework </p>
<p>We do provide a small item of feedback here based on the code which we can see so far.<br />
We would like to see the visibility of the methods and members of the classes reconsidered, as private is used widely, which would narrow the scope for extension. Also, we would like some of the method names to be reviewed, to be more consistent with the rest of the framework.</p></ac:rich-text-body></ac:macro>