Group items tagged

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.

"The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock this data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. Project Info odata4j is a new open-source toolkit for building first-class OData producers and first-class OData consumers in Java. "

"Apache Tuscany simplifies the task of developing SOA solutions by providing a comprehensive infrastructure for SOA development and management that is based on Service Component Architecture (SCA) standard. With SCA as it's foundation, Tuscany offers solution developers the following advantages: Provides a model for creating composite applications by defining the services in the fabric and their relationships with one another. The services can be implemented in any technology. Enables service developers to create reusable services that only contain business logic. Protocols are pushed out of business logic and are handled through pluggable bindings. This lowers development cost. Applications can easily adapt to infrastructure changes without recoding since protocols are handled via pluggable bindings and quality of services (transaction, security) are handled declaratively. Existing applications can work with new SCA compositions. This allows for incremental growth towards a more flexible architecture, outsourcing or providing services to others. In addition, Tuscany is integrated with various technologies and offers: a wide range of bindings (pluggable protocols) various component types including and not limited to Java, C++, BPEL, Spring and scripting an end to end service and data solution which includes support for Jaxb and SDO a lightweight runtime that works standalone or with other application servers a modular architecture that makes it easy to integrate with different technologies and to extend Integration with web20 technologies Apache Tuscany SCA is implemented in Java and C++ (referred to as Native)"

"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."

This blog host some of the good article on Java, FIX Protocol and Tibco Rendezvous messaging. I have shared Interview questions, daily tips, commands and approach on how to increase productivity and work effectively with these technology.

"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."

The CDO (Connected Data Objects) Model Repository is a distributed shared model framework for EMF models and meta models. CDO is also a model runtime environment with a focus on orthogonal aspects like model scalability, transactionality, persistence, distribution, queries and more. CDO has a 3-tier architecture supporting EMF-based client applications, featuring a central model repository server and leveraging different types of pluggable data storage back-ends like relational databases, object databases and file systems. The default client/server communication protocol is implemented with the Net4j Signalling Platform.

Apache XML-RPC is a Java implementation of XML-RPC, a popular protocol that uses XML over HTTP to implement remote procedure calls. Version 3 of Apache XML-RPC is still compliant to the XML-RPC specification. However, the user may enable several vendor extensions are available, that greatly extend the power of XML-RPC: All primitive Java types are supported, including long, byte, short, and double. Calendar objects are supported. In particular, timezone settings, and milliseconds may be sent. DOM nodes, or JAXB objects, can be transmitted. So are objects implementing the java.io.Serializable interface. Both server and client can operate in a streaming mode, which preserves resources much better than the default mode, which is based on large internal byte arrays.

"A hub for integrating your enterprise with the rich information available on the Web, the WSO2 Mashup Server leverages popular Web 2.0 formats and protocols into your service platform. Combining simple yet rich mashups with reusability, security, reliability, and governance, the WSO2 Mashup Server includes features for connecting Web Services to humans through Web pages, gadgets, feeds, instant messages, email and more. The WSO2 Mashup Server offers: Go Cloud-Native WSO2 Mashups as a Service gives you instant self-service provisioning, multi-tenancy and has built-in monitoring and metering capabilities. Increase productivity Reduce cost Gain more control Avoid vendor lock-in The ideal platform for defining composite services for user interfaces and mobile applications. A simple way to deploy services developed in JavaScript. Access to REST and WS-* web services, feeds, and scraped web pages with data scripted together quickly using common Web developer skills, the result being a new service, or a web page, gadget, email or instant message. The ability to secure hosted Mashups. Support for both recurring and longer-running tasks and service lifecycles. Monitoring, configuration of security and quality of service settings such as throttling. With no up-front license agreements or subscription fees, getting started with the WSO2 Mashup Server requires less developer effort, ensuring faster ROI."

"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 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. "