web services

I am attempting to use Adobe LiveCycle Designer to communicate with my Drupal install. However, after I select the data connection type WSDL and paste in the url of the WSDL, I get a message on any service I select that says "Cannot choose this operation: - Soap Binding must be Document/Literal." In the module, it appears that the type is hard-coded to "rpc". I am stuck and not sure what to do. I am new to the group and the module, so please bear with my stupidity on this. Thanks for any thoughts.

Para aqueles que tem mais sorte que eu e possuem um IPhone e um Mac, mas, assim como eu, adoram Drupal ( :D ), segue um tutorial passo a passo de como criar um aplicativo para o IPhone, baseado em Drupal.

How to integrate a iPhone application with Drupal - http://goodold.se/blog/tech/integrate-iphone-app-drupal

Muito bom!!

Hello All,

I had been working for couple of days on a module that would allow me to transfer nodes from a Drupal Website to another drupal site (for now).

which includes a full node save along with terms,files and CCK extra fields.

its really been a headache since i started patching the method "taxonomy_node_save" in "taxonomy services";
i have done the step of save a node (piece of cake) but now into the terms problem hence the NID of the new transferred node needs to be send to the remote server.

ill keep you updated guys on it and might release a contribution soon.

Over the last year, some Drupal users have expressed interest in integrating Drupal with iMIS, a membership and financial management system used by non-profits, membership organizations, and educational institutions. We have successfully implemented a custom solution for an ongoing project that links Drupal to iMIS. The solution includes a custom module for integrating Drupal & iMIS. We plan to release this module to the Drupal community once we have completed testing, made the module more suitable for general use, and prepared detailed documentation. Since the module is not likely to be ready until Spring 2009, we felt that the Drupal and iMIS communities might benefit from a summary of our approach and progress to date.

Guys,

Scott Nelson (snelson) included me as one of the maintainers last friday and im glad to announce a new version of Services module for D6 (in fact, i released 2 versions today). The 6.x 0.11 contains several bugs fixed, a new security fix and some nice and long waited features:
* user.get service
* user.save service
* user.delete service
* file.get service
* file.getNodeFiles service
* menu.get service
* Several services were renamed for consistency, including node.load service to node.get
* node and user services now have a very granular permissions

Just thought I'd let everyone know I've started the Python Services API project, which provides a set of classes and and tests that Python developers can use as a basis for integration with the Services module. It's fairly bare-bones at the moment, and I'm by no means and expert Python developer, so feedback and contributions are more than welcome.

Just a quick note that nedjo posted a note about Services module going into core. This would allow use of XML-RPC, JSON, RSS, REST, SOAP and more to be loaded through a common Services API.

A Code Sprint will take place in Boston this coming Friday that will focus on the inclusion of this new Services API.

In Drupal 5: My C# application can access my drupal service al. la. Rob's great video. I turn on the session ids for the service, and call the system.connect service to get a sessionID, which I then pass around as the extra parameter in each of my service calls. I authenticate my user, but cannot persist the session state...

There's growing interest in the Drupal community in the prospect of renewing our core data handling APIs. Doing so will increase consistency and efficiency and ease barriers. It will also be a key step in enabling transactional web services.

In Drupal 6 we took some impressive first steps. What should we tackle for Drupal 7?

The attached paper, written by Nedjo Rogers and Henrique Recidive and sponsored by CivicSpace, aims to carry this discussion forward and map out both some conceptual space and concrete development tasks.