Download JAR files tagged by standards with all dependencies

1) This module contains various Zookeeper recipe implementations. 2) The recipe directory name should specify the name of the recipe you are implementing - eg. zookeeper-recipes-lock. 3) It would be great if you can provide both the java and c recipes for the zookeeper recipes. C recipes go in to zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/c Java implementation goes into zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/java. 4) The recipes hold high standards like our zookeeper c/java libraries, so make sure that you include some unit testing with both the c and java recipe code. 5) Also, please name your c client public methods as zkr_recipe-name_methodname (eg. zkr_lock_lock in zookeeper-recipes-lock/src/c) 6) To run the c tests in all the recipes, - make sure the main zookeeper c libraries in zookeeper-client-c are compiled. Run autoreconf -if;./configure; make. The libraries will be installed in {top}/src/c/.libs. - run autoreconf if;./configure;make run-check in zookeeper-recipes/$recipename/src/c

This repository provides a native Android SDK, which enables to integrate your Mobile App with myPOS Card terminals, processed by its platform, to accept card payments (including but not limited to VISA, Mastercard, UnionPay International, JCB, Bancontact). myPOS SDK Android communicates transparently to the card terminal(s) via Bluetooth. To process checkout SDK provides management of the terminal to complete all the steps for transaction processing, return or refund, card storage for recurring transactions, and communicates to the application transaction status, card token, card masked PAN. No sensitive card data is ever passed through to or stored on the merchant's phone. All data is encrypted by the card terminal, which has been fully certified to the highest industry standards (PCI, EMV I & II, Visa, MasterCard & Amex).

The main module contains the GeoTools public interfaces that are used by other GeoTools modules (and GeoTools applications). Where possible we make use industry standard terms as provided by OGC and ISO standards. The formal GeoTools public api consists of gt-metadata, jts and the gt-main module. The main module contains the default implementations that are available provided to other GeoTools modules using our factory system. Factories are obtained from an appropriate FactoryFinder, giving applications a chance configure the factory used using the Factory Hints facilities. FilterFactory ff = CommonFactoryFinder.getFilterFactory(); Expression expr = ff.add( expression1, expression2 ); If you find yourself using implementation specific classes chances are you doing it wrong: Expression expr = new AddImpl( expression1, expressiom2 );

Adds deployment support for akka-http applications in kubernetes. The facilities are: 1) promotheus statistics export and collection for akka http routes. The library collects http result codes, timings, and requests in flight. It additionally optionally exposes some basic akka statistics. 2) Graceful shutdown, health and readiness functions. These routes are provided at a low level to they can be used by both the routing DSL and special case implementations. 3) Access log collection. These functions can be freely composed to (e.g.) exclude health check routes from statistics and access log, or include them, depending on the requirements and standards of the user

The biblio transformation engine is a java framework developed by the Hellenic National Documentation Centre (EKT, www.ekt.gr) and consists of programmatic APIs for filtering and modifying records that are retrieved from various types of data sources (eg. databases, files, legacy data sources) as well as for outputing them in appropriate standards formats (eg. database files, txt, xml, Excel). The framework includes independent abstract modules that are executed seperately, offering in many cases alternative choices to the user depending of the input data set, the transformation workflow that needs to be executed and the output format that needs to be generated.

The biblio transformation engine is a java framework developed by the Hellenic National Documentation Centre (EKT, www.ekt.gr) and consists of programmatic APIs for filtering and modifying records that are retrieved from various types of data sources (eg. databases, files, legacy data sources) as well as for outputing them in appropriate standards formats (eg. database files, txt, xml, Excel). The framework includes independent abstract modules that are executed seperately, offering in many cases alternative choices to the user depending of the input data set, the transformation workflow that needs to be executed and the output format that needs to be generated.

JDOM is a Java-oriented object model which models XML documents. It provides a Java-centric means of generating and manipulating XML documents. While JDOM interoperates well with existing standards such as the Simple API for XML (SAX) and the Document Object Model (DOM), it is not an abstraction layer or enhancement to those APIs. Rather, it seeks to provide a robust, light-weight means of reading and writing XML data without the complex and memory-consumptive options that current API offerings provide. built July 23 2009

Jetty is an open-source, standards-based, full-featured web server implemented entirely in Java. It is released under the Apache 2.0 licence and is therefore free for commercial use and distribution. First created in 1995, Jetty has benefitted from input from a vast user community and consistent and focused development by a stable core of lead developers. There are many more examples of Jetty in action on the Jetty Powered Page that has selections from among the tens of thousands of production Jetty instances. However, as Jetty aims to be as unobtrusive as possible, countless websites and products are based around Jetty, but Jetty is invisible!

JBoss Rules provides an open source and standards-based business rules engine that enables easy business policy access, change and management. JBoss Rules is a fast and highly efficient rules engine that makes it easy for a business analyst or auditor to view your business rules as encoded in your IT application infrastructure to verify that the encoded rules indeed implement the documented business policies. JBoss Rules also supports a variety of language and decision table inputs, making it easy to quickly modify your business policies to respond to opportunities and competitive threats.

JBoss Rules provides an open source and standards-based business rules engine that enables easy business policy access, change and management. JBoss Rules is a fast and highly efficient rules engine that makes it easy for a business analyst or auditor to view your business rules as encoded in your IT application infrastructure to verify that the encoded rules indeed implement the documented business policies. JBoss Rules also supports a variety of language and decision table inputs, making it easy to quickly modify your business policies to respond to opportunities and competitive threats.