Download JAR files tagged by side with all dependencies

This is client side library for forker, and the one you most likely want to use in your own applications. It provides the ProcessBuilder replacement, ForkerBuilder, as well the helpers in OSCommand. ForkerBuilder is capable of launching processes using non-blocking I/O or attached to a PTY. It has many additional features not available in the standard process builder including permission elevation, daemonize, processor affinity and more. Parts of the non-blocking API are based on NuProcess (https://github.com/brettwooldridge/NuProcess)

This library allows your Java program to interface very easily with the Python world. It uses the Pyro protocol to call methods on remote objects. (See https://pyro5.readthedocs.io/). Pyrolite only implements part of the client side Pyro library, hence its name 'lite'... So if you don't need Pyro's full feature set, Pyrolite may be a good choice to connect java or .NET and python. Version 5.0 changes: support Pyro5 wire protocol. Dropped support of Pyro4 (stick to version 4.xx for that).

This project contains a JNA (Java Native Access) implementation built on top of the native Hnswlib (Hierarchical Navigable Small World Graph) which offers a fast approximate nearest neighbor search. It includes some modifications and simplifications in order to provide Hnswlib features with native like performance to applications written in Java. Differently from the original Python implementation, the multi-thread support is not included in the bindings itself but it can be easily implemented on the Java side.

Jadex XML is an XML data binding framework for Java and also for other representations. The main idea of Jadex XML is that neither the XML-Schema on the one side nor the Java classes on the other side should define other binding. Instead, a separate mapping between both is used as a mediation. This allows designing the XML representation independent of the Java side but still being able to connect both as desired. This idea was first put forward by the JiBX data binding framework. Jadex XML pushes it further by combining it with the configuration by exception principle. The framework can detect obvious correspondences between both sides automatically and only needs configuration information when translations are necessary. The configuration information is currently specified directly in form of Java configuration classes.

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.

This library provides the necessary implementations to screen the following patterns: Bullish Belt Hold Bearish Belt Hold Hammer Hanging Man Southern Doji Northern Doji Gapping Up Doji Gapping Down Doji Takuri Line One Candle Shooting Star Bullish Strong Line Bearish Strong Line Bullish Harami Bearish Harami Bullish Engulfing Bearish Engulfing Bullish Kicking Bearish Kicking Matching Low Matching High Bullish Harami Cross Bearish Harami Cross Bullish Doji Star Bearish Doji Star Dark Cloud Cover Piercing Line Descending Hawk Homing Pigeon Bullish Abandoned Baby Bearish Abandoned Baby Three Inside Up Three Inside Down Three Outside Up Three Outside Down Three White Soldiers Three Black Crows Morning Doji Star Evening Doji Star Morning Star Evening Star Upside Tasuki Gap Downside Tasuki Gap Bullish Side by Side White Lines Bearish Side by Side White Lines Rising Three Method

The Virtuoso server module (ks-server-virtuoso) provides an implementation of the Triple Store server-side component (API in ks-triplestore) on top of the OpenLink Virtuoso triple store, a scalable native code triple store that is accessed as an external service. The Virtuoso Sesame driver, which builds on the Virtuoso JDBC driver, is used to remotely access the Virtuoso server for writing data and performing SPARQL queries. For performance reasons, data modification is performed in a non-transactional way, with the module managing possible failures in a way that trigger the external repopulation of the Virtuoso triple store starting from the master copy of data stored in the Data Store component.