SOAP API based on Symfony2 or how to do it right?

Question

symfony

Actually there is a slight disagreement with colleagues regarding the process of writing a SOAP web service. We use Symfony2 as a framework. The problem is in the organization of those processes. Alas, I have not written services in PHP SOAP before, because it was not necessary. But the approach in .NET has always pleased me. Actually, before, we sat down with people who needed an apishka and thought what I should give and how. After that, I implemented the API in the form of some class with the WebService attribute and methods with the WebMethod attribute.
Since annotations are very common in Symfony2, I thought that the process would be no different here. But, alas, there are big problems with the resulting WSDL. They are very solvable, but a rather strange approach, in my opinion, has already been developed.
iPhone developers give us the WSDL, and already PHP developers simply implement the service based on this WSDL. On the other hand, to implement automatic generation and simplify the process of implementing services is a matter of several hours. Is this correct at all?

Answer 1

This is just the moment where you need to pick up a hammer instead of a microscope and painlessly hammer a nail. Get Zend_Soap_Server and forget about wdsl and such.
ps googled examples dev.umpirsky.com/soap-server-and-test-client-with-zend_soap-symfony2-doctrine2-and-postgresql/

Answer 2

Our project uses BeSimple for SOAP. Works to communicate with the iPad and everything seems to be fine so far.
But I won’t tell you about the implementation features, the moped code is not mine.