[Fusionforge-general] Fwd: SOAP Api documentation

Laurent HUET laurent.huet at gmail.com
Tue Mar 23 11:35:33 CET 2010


2010/3/22 Christian Bayle <christian.bayle at orange-ftgroup.com>

> It's a good stuff ... decomposing API by family because there is a lot of
>> operations (~60) in a single WSDL.
>> I suggested to have a WSDL by family. I can write a draft for these WSDL,
>> WS-I Basic Profile compliant, of course ;-)
>>
> I'm not at all SOAP specialist, this seems an interesting proposition, I'll
> discuss this with coclico partners.
> Do you have any suggestion / expertise about the choice of the SOAP API,
> what do you think about the zend one?


In my opinion, the WSDL (the interface contract) is the most important thing
in SOAP APIs.
I have written a WSDL for the Core operations (group.php and user.php in the
soap/common dir).
I will send it to the list when my tests will be finished.

The choice of the SOAP framework depends on the requirements.
I have found the following tools :
- PEAR:SOAP : seems to be design for PHP4 when PHP doesn't have a SOAP
support.
- NuSOAP : like PEAR:SOAP but seems to be more flexible than PEAR:SOAP.
- PHP SOAP Extension : since PHP 5, SOAP was supported natively (written in
C) and then is more performant than older tools like NuSOAP and PEAR:SOAP.
- Zend Framework : Like PHP SOAP Extension (based on SOAP Extension
probably) but offers tools to manipulate/generate the WSDL that are not
available with the PHP SOAP Extension.
- WSO2 Web Service Framework for PHP : Seems to support the most recent
standards, particularly the MTOM/XOP (binary attachments) that the other
frameworks does not support.  This framework support REST too. It seems to
be the most complete framework but a binary extension have to be installed
on the server (deb and rpm package are available on the WSO2 web site).

Currently, I'm testing the WSDL with the PHP SOAP extension. I'm a Java
developper and not a PHP developper ... so I'm not very performant for
writing PHP code. I will send you the testing code with the WSDL.

In a precedent mail, I told you that attachments implementation in the
current SOAP Api was not efficient.
Due to lack of time, I will not see this aspect for the moment.

Cheers,

Laurent


-- 
-----------------
Laurent HUET
e-mail : laurent.huet at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fusionforge.org/pipermail/fusionforge-general/attachments/20100323/8acb791f/attachment.htm>


More information about the Fusionforge-general mailing list