Download JAR files tagged by used 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.

Evita is a specialized database with easy-to-use API for e-commerce systems. Purpose of this research is creating fast and scalable engine that handles all complex tasks that e-commerce systems has to deal with on daily basis. Evita should operate as a fast secondary lookup / search index used by application frontends. We aim for order of magnitude better latency (10x faster or better) for common e-commerce tasks than other solutions based on SQL or NoSQL databases on the same hardware specification. Evita should not be used for storing and handling primary data, and we don't aim for ACID properties nor data corruption guarantees. Evita "index" must be treated as something that could be dropped any time and built up from scratch easily again.

Provides all necessary resources for a Java project to enforce the coding style that I am using in my lectures about software development at Munich University of Applied Sciences and in all of my open source projects. It configures several static analysis tools for Maven and IntelliJ. Moreover, it provides some sample classes that already use this style guide. This classes can be used as such but are not required in this project. These classes also use some additional libraries that are included using the Maven dependency mechanism. If the sample classes are deleted then the dependencies can be safely deleted, too.

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.

ADIF Processor visualizes contacts in your input file on Google Earth. It generates a Google Earth Project file, also known as a KML file, with a visualization of each contact in the ADIF/SOTA CSV input file where station locations can be determined. It parses structured tags in comments to enrich the correct ADIF output file. QRZ.com is used to determine station locations and provide additional information in the ADIF output file. The markdown/text file output contains a listing of contacts. The processor contains activity databases for the main outdoor activities such as SOTA, POTA, GMA, HEMA etc.