Lightweight SOAP and REST webservice clients for Groovy with full control over requests.
Groovy-wslite is a lightweight library for Groovy that provides no-frills SOAP and REST webservice clients. It gives developers full control over request messages and buffers all data in memory, making it suitable for precise web service interactions without heavy abstractions. The library handles SSL, proxies, and various content types while maintaining a simple API.
Groovy developers who need to interact with SOAP or REST web services and want fine-grained control over request construction and response handling, particularly in Grails applications or Android projects.
Developers choose Groovy-wslite for its simplicity, direct control over web service messages, and seamless integration with Groovy's dynamic features. It avoids the complexity of larger frameworks while providing essential functionality like SSL customization and proxy support.
Lightweight SOAP and REST webservice clients for Groovy
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows precise construction of SOAP envelopes and REST requests using Groovy's MarkupBuilder, giving developers exact control over what is sent, as shown in the SOAP and REST examples.
Supports custom trust stores, trusting all certificates for development, and can be set per client or per request, detailed in the SSL sections for both SOAP and REST clients.
Leverages Groovy features like closures and builders for an intuitive API, making it natural for Groovy developers, as evidenced by the DSL-like syntax in examples.
Provides multiple levels of proxy configuration—request, client, or system properties—with clear precedence rules, explained in the proxy sections.
Buffers all request and response data in memory, which can lead to performance issues with large payloads, as stated in the library's philosophy.
Focuses only on SOAP and REST, lacking support for newer web service technologies like GraphQL or gRPC, which might limit modern use cases.
Version 2.0 is still in beta with plans for breaking changes, and the README warns to consult the Changelog, indicating potential instability for production use.