Download JAR files tagged by native with all dependencies

JNAerator (pronounce "generator") simply parses C and Objective-C headers and generates the corresponding JNA and Rococoa Java interfaces (it also has a very limited support for C++). This lets Java programmers access native libraries transparently, with full IDE support and little to no hand-tweaking. Users who are looking for ready-to-use libraries should check the NativeLibs4Java project instead.

The Proton system tests execute against either the Java or the C implementations, based on the chosen profile. To execute, run either "mvn test -P proton-j" or "mvn test -P proton-jni". To reduce the set of Python tests run, set system property proton.pythontest.pattern, for example: mvn test -Dproton.pythontest.pattern='proton_tests.transport.TransportTest.*' The proton-jni profile looks for the JNI jar and native libraries under directory <basedir>/build/proton-c. To override this, run Maven like so: "mvn test -P proton-jni -Dproton-c-build-dir=/path/to/build/dir".

NekoPull is an XML document parsing API that extends the Xerces Native Interface (XNI) to provide pull parsing functionality. The pull parsing paradigm is different from tree-based APIs like the Document Object Model (DOM) and event stream APIs like the Simple API for XML (SAX) in that the application controls the parsing of documents. NekoPull is similar to lex in that the application requests, or pulls, the document information one piece at a time instead of having document information pushed to the application.

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.

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (eg. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (eg. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

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 project provides Result-type similar to Result-type in Rust that allows to return either successfull result or otherwise some kind of error. In Java native way of reporting errors are exceptions, either checked or unchecked, but Result-type provides a way to pass error enformation as a first-class value through the code written in functional style. Routines are provided for interoperability of normal code that uses exception and functional code that uses Result-type, so that exceptions can be catched and propagated as errors in Result-type and then rethrown again later in the control-flow.

CITA-Cloud is an open-source blockchain development framework. It is released under the Apache 2.0 license and provides an architecture and development tools for customization. Its aim is to overcome the scalability and programmability challenges of blockchain technology at the underlying level. Leveraging cloud-native capabilities, it allows flexible replacement of blockchain components. Research institutions can easily integrate and transform their research results. Ultimately, the goal is to achieve flexibility, openness, and interoperability at the underlying level of blockchain for different scenarios.

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