Indeed, this plugin seems to be perfect. I've also tried it before posting this message but encoutered some problems (maybe sovable ?).
I explain : As you can see in the documentation page of the plugin ( http://www.symfony-project.org/plugins/ckWebServicePlugin), the example shows how to make a class with SOAP (simplified) functions. By simplified, I mean that you decide which functions you will make accessible via SOAP once your application is finished. In my example, we can imagine that my SOAP handler will have the following methods pattern to deal with my contacts, countries and langs : * Country[] getListCountries() * Lang[] getListLangs() * Contact[] getListContacts() * Contact getContactById( integer $id ) * Lang getLangByCodeIso( string $code_iso ) As you can see, all these functions can be considered as an abstraction layer which will call the application's model. If my application's model growth up, I will need to add methods to this class. If my model change, I will need to change method's implementation. What I really want to do is to find a way to avoid maintaining both a web browsing interface and a SOAP API which share the same model. Does anyone have an idea on how to do that kind of stuff ? Maybe a sunshine here : http://www.symfony-project.org/cookbook/1_1/en/iphone ? Every comment is welcome. Seb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
