Download JAR files tagged by http with all dependencies

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

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.

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.

日志模块，集成log4j2, 提供工具类可静态打印日志, 业务可import通用日志配置(中间件配置和业务基础配置)开箱即用， 另外还提供http接口出入参打印和rpc提供者和消费者的出入参打印(有开关可以热启动和热关闭，同时可在线修改日志级别)， traceId在日志中进行输出以及普通文件日志之外的结构化日志( 供运维采集分析可视化)，提供全链路信息（包括tid）跨线程跨线程池的能力 Log module, integrates log4j2, provides tool classes that can print logs statically, business can import common log configurations (middleware configuration and business basic configuration) out of the box, and also provides http interface input and output parameter printing and rpc providers and consumers. Input and output parameter printing (there is a switch for hot start and hot shutdown, and the log level can be modified online), traceId is output in the log and structured logs other than ordinary file logs (for operation and maintenance collection and analysis visualization). The ability to provide full link information (including tid) across threads across thread pools.

Set of various Utils: stacktrace noise filter, String to/from unicode sequence converter, simple Http client JSON parser/serializer, Silent String parsing to Integer and other numeric types, Parsing String to time intervals with support for time unit suffixes, JSON parser that provides serialization/deserialization of classes to JSON, Version comparator and Version ranges operations, Self-throttling binary reader from Http request, File reader, A utility that automatically initiates a Factory with instances of all classes that implement user provided interface. An infrastructure for writing Scheduled Task classes where time interval for task execution is provided in humanly readable format (such as "9h" for 9 hours)

This artifact provides the implementation of the L* learning algorithm described in the paper "Learning Regular Sets from Queries and Counterexamples" (https://doi.org/10.1016/0890-5401(87)90052-6) by Dana Angluin including variations and optimizations thereof such as the versions based on "On the Learnability of Infinitary Regular Sets" (https://dx.doi.org/10.1006/inco.1995.1070) by Oded Maler and Amir Pnueli or "Inference of finite automata using homing sequences" (http://dx.doi.org/10.1006/inco.1993.1021) by Ronald L. Rivest and Robert E. Schapire.

This Lutra submodule provides a common framework that other submodules in Lutra use and extend. It includes an implementation of OTTR's data model with classes for templates, instances, types, etc.; a system for handling results and error messages; core interfaces and abstract classes for streamed pipelines for parsing and writing templates and instances; as well as implementation of the TemplateStore, a container for templates, with algorithms for checking correctness of templates and expanding and checking correctness of instances. Lutra is the reference implementation of the OTTR framework. For more information about OTTR, see http://ottr.xyz.

DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it helps developers to save time when designing simple/medium complexity reports generating the layout of the report elements automatically. It creates reports dynamically, defining at runtime the columns, column width (auto width), groups, variables, fonts, charts, crosstabs, sub reports (that can also be dynamic), page size and everything else that you can define at design time. DJ keeps full compatibility with Jasper Reports since it's a tool that helps create reports programmatically in a easy way (it only interferes with the creation of the report design doing the layout of the elements). You can use the classic .jrxml files as templates while the content and layout of the report elements are handled by the DJ API. http://dynamicjasper.com