Download JAR files tagged by only with all dependencies

Suji is a converter library from Japanese number notation to numerical value, and from numerical notation to Japanese Kansuji notation. Converter.values(src) to convert from Japanese number notation to numerical value: Japanese number notation can include Kansuji. The String "１つの価格が二兆30万五千十7円になります。" will be converted to two BigDecimal, 1 and 2000000005017. And also, 打率は三割二部五厘です。 will be a 0.325. The return value is a list of Suji Numeral objects. If the input string has no number notation, Suji returns a empty list. The Numeral object has three methods: value(), begin(), and end(): value(): a BigDecimal instance of a numerical value for the number notation. begin(): the begin index (int) of the found number notation at the input string. end(): the end index (int) of the found number notation. Converter.kansujis(src) to convert from numeric notation to Japanese Kansuji notation: The String 20兆30万五千十7円になります。 will be converted to the Kansuji string, 二十兆三十万五千十七. The boolean flag one is interpreted as whether to display the first character 一 or not. The output of Converter.kansujis('1000万', true) will be converted to 一千万, and the output of Converter.kansujis('1000万', false) will be converted to 千万. Note that kansujis does not support numerical notation after the decimal point. If the input string is 32.01, the output will 三十二, not 三十二割一厘. The return value is a list of Kansuji objects. If the input string has no number notation, Suji returns a empty list. The Kansuji object has three methods: value(), begin(), and end(): value(): a String instance of a Kansuji notation. begin(): the begin index (int) of the found number notation at the input string. end(): the end index (int) of the found number notation. Suji is a one-pass parser. That is, Suji parse a source text from the head to the end only once.

The Data Highway is a service that allows data to be easily landed and consumed via REST interfaces which accept and produce JSON messages. The data is first defined using a schema and a "road" is created which will accept data messages that conform to this schema. Producers of data sets thus only need to define the structure of their data and are then able to send their data to a REST endpoint and not be too concerned with what happens next. The Data Highway will ensure that this data is made available for downstream streaming consumption and also stored reliably in a "data lake" in the cloud for access by various end users.

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 library contains native facade implementations of the JBrew utility libraries with the Java Native Interface (JNI). This set of libraries features specific optimizations for Unix-based systems in terms of performance and memory. This is achieved through careful tuning using the C programming language to not only control for garbage collection, but also to ensure maximum performance for elected library features. This library in particular features example usages of the JNI in order to test hardware for usability.

This library contains native facade implementations of the JBrew utility libraries with the Java Native Interface (JNI). This set of libraries features specific optimizations for Unix-based systems in terms of performance and memory. This is achieved through careful tuning using the C programming language to not only control for garbage collection, but also to ensure maximum performance for elected library features. This library in particular features example usages of the JNI in order to test hardware for usability.

This library contains native facade implementations of the JBrew utility libraries with the Java Native Interface (JNI). This set of libraries features specific optimizations for Unix-based systems in terms of performance and memory. This is achieved through careful tuning using the C programming language to not only control for garbage collection, but also to ensure maximum performance for elected library features. This library in particular features example usages of the JNI in order to test hardware for usability.

A plugin for the Apache Felix Webconsole. When installed, this bundle will add a tab on the Web Console that provides a graphic overview of the OSGi framework, including services, bundles, and components. Colors are used to encode the different states. Bundles are shown to be started, stopped, starting, resolved, and installed. Services are shown to be used, looked for, or registered in the air. Components can be seen to be operating or not satisfied. Most objects have a tooltip with extra information and all objects can be clicked upon. Hovering over a bundle or service shows only the conenections to/from the component. The display updates every 5 seconds to provide a continuous view on the operations of the framework it runs on.

Bundle with a synchronous activator which will install OGEMA resources from XML (.ogx) or JSON (.ogj) files located in config/resources (default). This requires a running OGEMA framework when the bundle is started and enables the installation of basic resources before other applications are activated. Also adds a service for felix fileinstall that will install such resource files. Files installed through fileinstall will be reinstalled when they are updated or when a newer version of an installed file is found after a restart (using the file's last modification timestamp). Files installed from the configuration directory will only be reinstalled on a restart, if they have been changed.