Search Results for "soap 1.2"

PHP implementation of SOAP 1.1 and 1.2 client specifications. Pure PHP, no dependencies on ext-soap. Extensible (JMS event listeners support). PSR-7 HTTP messaging. PSR-17 HTTP messaging factories. PSR-18 HTTP Client. No WSDL/XSD parsing on production. IDE type hinting support. Only document/literal style is supported and the webservice should follow the WS-I guidelines. There are no plans to support the deprecated rpc and encoded styles. Webservices not following the WS-I specifications might...

A fast and modern Python SOAP client. Compatible with Python 3.7, 3.8, 3.9, 3.10, 3.11, and PyPy. Build on top of lxml and requests. Support for Soap 1.1, Soap 1.2 and HTTP bindings. Support for WS-Addressing headers. Support for WSSE (UserNameToken / x.509 signing) Support for asyncio via httpx. Experimental support for XOP messages. Zeep inspects the WSDL document and generates the corresponding code to use the services and types in the document. This provides an easy-to-use programmatic...

..., SOAP and REST Web API development, WS-* protocols (WS-Security, WS-Policy, WS-ReliableMessaging, etc), XML-RPC and JSON. Licensed under GPLv2. Visit the developer center with guides, tutorials, and examples at www.genivia.com/dev.html The documentation of the toolkit, libraries, plugins and more is available at www.genivia.com/docs.html Commercial-use licenses and expert technical support services are available at competitive pricing levels, please visit www.genivia.com/products.html

DotNetOpenServer SDK is an open source lightweight fully extendable TCP socket client/server application framework enabling developers to create highly efficient, fast, secure and robust cloud based smart mobile device and desktop applications. Why? Unlike most application server frameworks, which are implemented over slow inefficient stateless protocols such as HTTP, REST and SOAP that use bulky ASCII data formats such as JSON and XML, DotNetOpenServer has been built from the ground up...

MicroWSS is a lightweight web services server/toolkit written in Java. Its purpose it to allow for simple development and deployment of services that use SOAP 1.2 and WSDL. It handles everything relating to XML, so that you only need to deal with Java.

Its a soap 1.2 client for all kinds of web services calls. Usually Webservices need to be called remotely but it cannot be called unless http call access is given to the service. Thus browser call is impossible for it to get tested.

Simple SOAP connector for Erlang/OTP. Compatible with SOAP 1.1 and 1.2. Currently supports XSD schema for service definition but no WSDL.

A messaging framework that uses web services to enable interoperability between client and server applications. The data exchanging relies on SOAP 1.2 Message Transmission Optimized Mechanism (MTOM) protocol and occurs as file streaming over the web.

SOAP-Server framework for Java Micro Edition (JME). Use this framework to run simple web services on mobile devices, e.g. PDAs. Supports SOAP 1.2 (without attachments). Runs on MIDP2.0/CLDC1.1 or CDC compatible VMs with sufficient memory.

AlchemySOAP is a C++ SOAP 1.1/1.2 protocol stack, licensed under the LGPL. It is fast, standards compliant, includes many automated unit/interop tests and other notable features (optional SSL and DOM support, etc.). AlchemySOAP is a fork of the EasySoap+

SOAP 1.2 Implementation Written in Java. The difference between SOAPAnywhere (SAW) and Implementations such as Apache SOAP and Axis is that SAW can not only be run through a WebAPP container but can also run in both a standlone mode and as an integrated

phpXMLP aims to be a XML Protocol implementation for PHP. It should provide support for SOAP 1.2 and WSDL 1.0. It follows very closely the design proposed by the XML Protocol Abstract Model Working Draft published on the 9th of July, 2001 by the W3C.