Download JAR files tagged by rest with all dependencies

Interfaces to be implemented by Domains, Connectors and Events which handle intatiation of Services and Proxies, classes for registration of bundles and services, classes for localization, classes that save connector properties (Persistence) and finally classes that enable the web application to have access to OSGI bundles. This bundle contains only the model and interface descriptions of all those services. In theory someone can take only a minor number of openengsb bundles, the api and create the rest of the system on his own.

This is a simple Web Service Client library to call wide variety of web service behind HTTP. In theory it can support any interface or payload. On the request side, to convert java object to HTTP request components (URL, headers, body), templating is used which allows it to call XML, JSON, SOAP, REST or anyother custom interface. On the response side, it uses pluggable parser and a mapper to only extract the fields that are of interest for the client program. The parser currently supports JSON and XML and returns a collections tree.

This feature provides a gateway between mobile, cloud, and web clients and z/OS back-end systems such as CICS Transaction Server, IMS, and batch applications. It provides RESTful APIs and enables you to route HTTP requests to remote REST endpoints. It also accepts and returns JSON payloads and communicates with back-end systems by providing a data transformation service that converts JSON payloads to/from byte arrays consumable by z/OS native-language applications written in Cobol, PL/I, and C.

A secure, REST administrative connector that can be used locally or remotely using any Java developer kit. This connector enables remote access from a Java client or directly through an HTTPS call. The administrator and reader roles protect the connector. The connector requires TLS to keep the communication confidential. The HTTPS port used by the connector is defined through the default HTTP endpoint. This feature supersedes the restConnector-1.0 feature. It enables the REST handler configuration APIs. When this feature is combined with features supporting configuration validation, the corresponding REST handler validation APIs are enabled.

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.

The matching web service client library for the server in this example project to connect to the server. This library is ideally provided by the service provider of the server, so that users can go ahead and hack their userland code against this client library, without having to worry about the transport. Whether the client library uses REST or SOAP is up to the implementor, both are possible. A user of the client library usually does not care what technology is used underneath (as long as things are working correctly).

This module contains library classes for accessing the ThreadFix REST API. The ThreadFix IDE plugins use this library to retrieve application and vulnerability marker information, and in the ThreadFix scanner plugins to get endpoint information and upload scans to ThreadFix applications. The easiest way to start using the library is with the PluginClient or ThreadFixRestClient classes. Both have constructors that take a PropertiesManager instance, which holds the ThreadFix API key and url information. The default PropertiesManager implementation stores these properties in threadfix.properties, but the ThreadFix plugins extend the default PropertiesManager class to override this behavior for the target platform.

The Data Highway is a service that allows data to be easily landed and consumed via REST interfaces which accept and produce JSON messages. The data is first defined using a schema and a "road" is created which will accept data messages that conform to this schema. Producers of data sets thus only need to define the structure of their data and are then able to send their data to a REST endpoint and not be too concerned with what happens next. The Data Highway will ensure that this data is made available for downstream streaming consumption and also stored reliably in a "data lake" in the cloud for access by various end users.