Download JAR files tagged by request with all dependencies

A servlet filter that logs requests to the log (slf4j) and writes them asynchronously to the DB. RequestLoggerFilter - logs request info to the DB RequestLoggerFilterPerfJdbc - subclass of RequestLoggerFilter that also logs time spent in JDBC using perf-jdbc RequestLoggerFilterPerfmon4J - subclass of RequestLoggerFilter that also logs time spent in JDBC using perfmon4j By default, uses the "java:/comp/env/jdbc/request-logger" data-source to log to. Can be overridden with the "com.alterion.requestlogger.jdbc.datasource-jndi" system-property. DB schemas for MS-SQL and PostgreSQL are in src/main/sql

This will eventually be a port of Google's libphonenumber to Scala. For now, because I need this functionality quick, it simply wraps libphonenumber. It is NOT complete by any means. I've only added the functionality that I needed. Currently you get a PhoneNumber case class that assumes the country is USA when you don't pass the country in. While you can pass the country in, the only country defined is USA. If you're interested in more from this library, report an issue or send me a pull request. I want to complete it and slowly remove the dependency on Google's libphonenumber

Programmatically generate, load, modify, and convert Excel .xlsx spreadsheets in your Java applications. Document Solutions for Excel (DsExcel, previously GcExcel) is a cross-platform high-speed, small-footprint spreadsheet API library that requires no dependencies on Excel. The powerful calculation engine supports 450+ Excel Functions and custom functions to perform complex calculations. DsExcel is 2x+ faster and uses less memory than Apache POI and allows you to save to XLSX, PDF, HTML, CSV, JSON and Images. Deploy your applications to the cloud, Windows, Mac, or Linux. If you'd like to remove the trial watermark and other trial limitations, please email [email protected] to request your 30-day evaluation key.

A set of reflection utilities and miscellaneous utilities related to working with classes and their fields with no dependencies which is compatible with java 1.5 and generics. The package was originally created by Aaron Zeckoski for the Sakai Project and Generic DAO project but was repackaged to make it distributable by request. It is used in the RSF framework (http://www2.caret.cam.ac.uk/rsfwiki/) and the EntityBroker among other things. Note about the BeanUtils provided dependency: BeanUtils is not required if you are not using it in your project. Note about the Hibernate provided dependency: Hibernate is not required if you are not using it in your project.

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

There are two ways to use OSGi in server-side[1]. In Carbon, what we have done is, embedding an OSGi framework inside a servlet container. So BridgeServlet delegates all the request from the servlet container to the HttpServiceServlet registered by the http.bridge bundle. This is required only when Carbon is running inside a webapp. There is a possibility to embed an HTTP server(ex. jetty) inside equinox and start a server with all our carbon bundles. This is same as running carbon inside spring DM server. For this scenario, we do not need org.wso2.carbon.http.bridge bundles and the org.wso2.carbon.bridge extension bundle. 1. http://eclipse.org/equinox/server/http_quickstart.php

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)