Projects tagged ‘interoperable’

Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis SOAP stack to build on the lessons learnt from Apache Axis. Apache Axis2 not only supports SOAP 1.1 and SOAP 1.2 ... [More] , but it also has integrated support for the widely popular REST style of Web services. [Less]

Apache CXF simplifies the construction, integration, and flexible reuse of technical and business components using a standards-based, service-oriented architecture (SOA). CXF is a merger of two prior ... [More] OSS projects - Celtix ObjectWeb and XFire projects. CXF support JAX-WS, RESTful and POJO for the building Web Services. CXF support SOAP, JMS, CORBA and more. [Less]

PEtALS is the highly distributed Open Source ESB hosted by OW2. PEtALS delivers OW2 JavaTM Business Integration (JBI) platform. PEtALS provides lightweight and packaged integration solutions, based ... [More] on JSR-208 specifications, with a strong focus on distribution and clustering. PEtALS helps you to integrate your Enterprise Business Units in order to provide a value added global solution. By assembling all your enterprise elements, you can provide new applications by re-using some existing ones. Thus, all your applications expose their logic by exposing services. This concept is know as a Service Oriented Architecture (SOA). The project also provides a set of JBI components and a component development kit that will help users to develop their own components. [Less]

JORAM (Java Open Reliable Asynchronous Messaging) is an open source implementation of the JMS (Java Message Service) 1.1 API. It provides access to a really distributed MOM (Message Oriented ... [More] Middleware), built on top of the ScalAgent D.T. agents based platform and used within many critical operational applications. Stable versions of JORAM are JMS 1.1 certified. Moreover JORAM is used by JOnAS to undergo the J2EE 1.4 certification, and has passed all tests concerning JMS 1.1 certification in this J2EE TCK. JORAM is a mature project started in 1999, it is an open source software released under the LGPL license since May 2000. Professional Support is available from Scalagent D.T. [Less]

Project Tango develops and evolves the codebase for Web Services Interoperability Technologies (WSIT) that enable interoperability between the Java platform and Windows Communication Foundation (WCF) ... [More] (aka Indigo). Project Tango's WSIT tecnology is bundled inside GlassFish v2. It is also possible to download a more recent version of WSIT and install into GlassFish or Tomcat. Project Tango uses JAX-WS and JAXB as a foundation upon which to build plugins to provide web services features such as bootstrapping communication, optimizing communication, reliable messaging, atomic transactions, security and trust. [Less]

JBoss Web Services Framework

Create Web Services with PHP5 in minutes. InstantSVC (pronounced as Instant Services) provides a set of tools to ease your development. You just need to document your object oriented PHP code with ... [More] PHPDocumentor in order to generate Web Services from it - SOAP Services as well as RESTful Web Services. Features of InstantSVC include an Extended Reflection API with information about data types, Annotations for PHP, a WSDL generator conform to WS-I Basic Profile, a Document/literal adapter generator, a Handler chain mechanism for SOAP processing, Implementations of WS-Security and the Username Token Profile, a Server for RESTful Web Services and an Administration tool for convenient creation and management of SOAP and REST servers. [Less]

The policy project has two distinct goals: - In the short term, make JAX-WS WS-policy aware by moving out the generic policy code from project Tango. - In the long term, provide a common, abstract ... [More] policy API layer. The API design should be independent of any particular policy expression language. Instead it should be use case driven and ease-of-use oriented. The project is inspired by the effort and experience gained with WS-Policy and other policy languages for web services in project Tango. Unlike the WS-Policy implementation in project Tango, this project is meant to approach the policy domain in a much more general sense and to enable policy features in a wide spectrum of Java SE and Java EE applications. [Less]

Web Services Interoperability Profile Environment is a toolkit for managing and using "service profiles" needed for SOA realisation. Core is an inheritance resolver library, used by a document generator and conformance test suite generator.

Implements a simple asynchronous loader and module pattern based on dynamic script tags (or load function for command line Javascript). This intended to be loaded before Javascript libraries that use ... [More] the module pattern, allowing those libraries to interoperate. Latest version: 1.2 UsageIn you html file: // tell JSAL where to find modules that start mylib jsal.lib('mylib', '../mylib/src'); // load mylib and mylib.blah jsal.load(['mylib', 'mylib.blah'], function () { // ../mylib/src/mylib.js and ../mylib/src/mylib/blah.js are loaded here }); // don't assume they are loaded here - the loader is async In your module (JSAL module pattern): jsal.module({ name : 'mylib', // this must match the name used to load it depends : ['myotherlib'], // dependencies are automatically loaded onload : function () { // dependencies are available here } });APIFunction: jsal.libTell JSAL where to load modules within a particular namespace from. Arguments: namespacePrefix - (string/array of strings) prefix(es) of namespaces to load. urlPrefix - (string) prefix of the URL to load modules from. Function: jsal.loadLoad a module/modules and run a function when done. Arguments: module - (string/array of strings) module(s) to load. callback - (function, optional) callback to run when the module(/modules) is loaded. Function: jsal.moduleCreate a new module with the JSAL module pattern. Arguments: opts - (object) options object containing: name - (string, required) the module name (must correspond to the filename). depends - (array of strings, optional) the modules that this module depends on. onload - (function, required) called when the dependencies are loaded. This is where the module implementation is put. InstallationCopy the file jsal.comp.js to a convenient location (can be inlined if you want to avoid the HTTP request). Library authors are encouraged to distribute JSAL with their library. AuthorThomas Yandell LicenseThe MIT License Copyright (c) 2008 Thomas Yandell Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. [Less]