Group items tagged

"The Qt SOAP project provides basic web service support with version 1.1 of the SOAP protocol. The SOAP (Simple Object Access Protocol) component recognizes the XML standard for describing how to exchange messages. Its primary usage is to invoke web services and get responses from Qt-based applications. These classes make it easy to construct, send, receive and process SOAP messages on the client side."

Apache Axis is an implementation of the SOAP ("Simple Object Access Protocol") submission to W3C. From the draft W3C specification: SOAP is a lightweight protocol for exchanging structured information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. This project is a follow-on to the Apache SOAP project. Please see the Reference Library for a list of technical resources that should prove useful.

ECF is a framework for building distributed servers, applications, and tools. It provides a modular implementation of the OSGi 4.2 Remote Services standard, along with support for REST-based and SOAP-based remote services, and asynchronous messaging for remote services. See the ECF Wiki for examples, tutorials, other documentation, as well as plans and efforts currently underway for future releases.

"The PHP/Java Bridge is an implementation of a streaming, XML-based network protocol, which can be used to connect a native script engine, for example PHP, Scheme or Python, with a Java virtual machine. It is up to 50 times faster than local RPC via SOAP, requires less resources on the web-server side. It is faster and more reliable than direct communication via the Java Native Interface, and it requires no additional components to invoke Java procedures from PHP or PHP procedures from Java. "

"JAX-WS Reference Implementation Project. This project provides the core of Metro project, inside GlassFish community This project develops and evolves the code base for the reference implementation of the Java API for XML Web Services (JAX-WS) specification. The current code base supports JAX-WS 2.0 and JAXWS 2.1 but the project will track future versions of the JAX-WS specifications."

"XMPP Web Services for Java (xws4j) is an implementation of machine to machine communication over XMPP according to the XMPP Extension Protocol XEP-0244 - IO Data and others. Although the name "web services" implies network communication over HTTP all communication is carried out over XMPP. The communicated content is encoded in XML, according to customized definitions of input and output in XML Schemata. "

"The XMPP Standards Foundation is an independent, nonprofit standards development organization whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF's Extensible Messaging and Presence Protocol (XMPP). You can read more here."

"Qworum defines a new type of service that is used for modularizing web applications. Qworum services are interactive, just like conventional websites. In addition, Qworum services are callable, much like traditional RPC services. "

"SwitchYard is a lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications. Wait, what? You mean like an Enterprise Service Bus (ESB)? Yeah, kind of. At it's core, SwitchYard provides an embeddable services runtime with limited dependencies, allowing you to deploy and run services where you need them: inside unit tests, embedded in your own applications, as modules in an OSGi framework, or within an application server. Of course, there will be modular components on top of core to provide connectivity, transformation, routing and orchestration, and all the other features that are typically associated with an ESB. The main difference between SwitchYard and traditional ESB offerings is that we are trying to make the runtime a transparent detail in the service lifecycle. SwitchYard aims to keep you focused on your services by providing tooling to help define, test, and manage the important details of a service - it's contract, policies, configuration, composition, and management . After all, the least important detail of your service is where it runs."