Download JAR files tagged by resources with all dependencies

This module provides versioning support for all modifications of the data contained in the LMF System (triples, resources, namespaces). Versions are accessible according to the Memento protocol using a special webservice. Versioning is triggered when a transaction finishes successfully and will store additional versioning information in the database. Note that this implies a certain performance overhead.

JXTA technology is a set of open protocols that allow any connected device on the network ranging from cell phones and wireless PDAs to PCs and servers to communicate and collaborate in a P2P manner. JXTA peers create a virtual network where any peer can interact with other peers and resources directly even when some of the peers and resources are behind firewalls and NATs or are on different network transports. JXSE is the Java implementation of the JXTA protocols.

OpenCms-Module 'org.opencms.workplace.tools.content'. <p>This module contains the OpenCms administration tools for managing the content of resources.</p> <p>Install this module if you want to modify file properties or content elements.</p> <p><i>(c) 2013 by Alkacon Software GmbH (http://www.alkacon.com).</i></p> OpenCms is a Content Management System that is based on Open Source Software. Complex Intranet and Internet websites can be quickly and cost-effectively created, maintained and managed.

GRAM simplifies the use of remote systems by providing a single standard interface for requesting and using remote system resources for the execution of "jobs". The most common use (and the best supported use) of GRAM is remote job submission and control. This is typically used to support distributed computing applications. This library has the API's to create a GRAM client.

This generates a schema artifact which contains all of the schemas from xmpp.org's subversion repository. Generating this artifact enables a schema to be referenced by jaxb using the ClassPathCatalogResolver and a catalog file. To refresh the content of this artifact, either remove the src/main/resources directory manually or run a clean build from hudson. This is because maven-scm-plugin is set to checkout only if that directory does not exist so that the remote subversion repository is not hit every time a build is performed.

JXTA technology is a set of open protocols that allow any connected device on the network ranging from cell phones and wireless PDAs to PCs and servers to communicate and collaborate in a P2P manner. JXTA peers create a virtual network where any peer can interact with other peers and resources directly even when some of the peers and resources are behind firewalls and NATs or are on different network transports.

JXTA technology is a set of open protocols that allow any connected device on the network ranging from cell phones and wireless PDAs to PCs and servers to communicate and collaborate in a P2P manner. JXTA peers create a virtual network where any peer can interact with other peers and resources directly even when some of the peers and resources are behind firewalls and NATs or are on different network transports.

The Shell Card Management API is REST-based and employs OAUTH 2.0,Basic and ApiKey authentication. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources. The internal workings of the platform are not important when interacting with the API. However, it is worth noting that the platform uses a microservice architecture to communicate with various backend systems and some API calls are processed asynchronously. All endpoints use the POST verb for retrieving, updating, creating and deleting resources in the Shell Card Platform. The endpoints that retrieve resources from the Shell Card Platform allow flexible search parameters in the API request body.

Data And Reporting product consists of API's which provides details of transaction and invoice informations about shell cards. The Shell Card Transaction and Invoice API is REST-based and employs Basic authentication in Version 1 and Oauth authentication in Version 2 end points. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources.