This is the long overdue 1.0 release of Web Service Client. It comes with two important changes:
- A new wsclient_tester submodule has been created to help with testing and debugging web service calls. Thanks dman!
- A lot of old cruft has been removed that was originally planned as subscription/notification system with remote entities. It caused some side effects when rebuilding entity information and it never took off as useful feature. I decided to remove it to make the module a lot shorter and less complex.
Full Changelog since 7.x-1.0-beta2:Read more
Maintenance release. Although wsclient works pretty solid there are some minor stable release blockers that need some love before a 1.0 release.
Changes since 7.x-1.0-beta1:
- #1302740 by nquocbao, klausi: Added support for global parameters for all operations of a service.
- fixed wrong comment
- removed deprecated hook_default_wsclient_alter() implementation as exportables are now always loaded from the db
- Improved wsclient UI to implement menu item customizations in the UI controller.
- allow endpoint types to alter the UI and used it to expose the REST operation URL setting.
Maintenance release without major changes. Entering beta phase now, but there are still some open issues (the UI is still lacking support for important settings that only can be used in code right now).
Changes since 7.x-1.0-alpha4:
Changes since 7.x-1.0-alpha3:
- #1027908 Entity API change: Fixed calls to entity_load_multiple_by_name() and changed the entity controller class to EntityAPIControllerExportable.
- Added the UI configuration path to the info file
- #1122812: Removed function call from hook_schema()
- #1102336: Improved README with installtion instructions, usage with Rules and usage for developers
- #1020428 by klausi: Fixed a notice in the remote event support
Second alpha release of Web service client, as ALPHA-1 is broken. This module provides the following features:
* Web service operations can be invoked as Rules actions
* Web service descriptions are entities that can be managed from code and from an administrative user interface
* REST and SOAP service types are supported
* Complex web service data types can be specified
* Developers can leverage an easy to use API for invoking web services
* Web service descriptions can be exported/imported to and from other Drupal sites
* Web service descriptions can be exported with Features (including dependency resolution for shared data types between services)
* Metadata for SOAP services (operations, data types) is extracted from WSDL files automatically
* Multiple web service calls can be combined in a Rules workflow
Development snapshot of most recent work.