Download JAR files tagged by listeners with all dependencies

Core interfaces and support classes to ease information systems development. Usually requirement is to implement multi-tier application using database, DAOs, services, models and listeners.

A highly-concurrent modeling of properties (or really any String-serializable key-value store) with support for reading and writing sets of properties atomically, and additionally registering listeners to changes of specific properties.

This project implements an Entity-Component Event-based System (ECES) framework. In such a framework, classes are organized as components that attach to entities, and listeners (or callbacks) can be easily configured to asynchronously run upon the creation/deletion/update of selected components.

An OSGi bundle used in integration tests. This bundle exports the package containing the service definition for HelloService and imports the Jsr330BundleActivator and javax.inject from the OSGi runtime and uses the Jsr330BundleActivator to find a provider for HelloService and expose the service to listeners.

An OSGi bundle used in integration tests. This bundle exports the package containing the service definition for HelloService2 and embeds the Jsr330BundleActivator and imports javax.inject from the OSGi runtime and uses the Jsr330BundleActivator to find a provider for HelloService2 and expose the service to listeners.

An OSGi bundle used in integration tests. This bundle exports the package containing the service definitions for HelloService3a, HelloService3b, and HelloService3c, and embeds the Jsr330BundleActivator and javax.inject and uses the Jsr330BundleActivator to find a provider for HelloService3a, HelloService3b, HelloService3c, and set up listeners for the providers' dependencies and when the dependencies arrive, expose the service to listeners.

D-Haven Managed Pool is a library designed to provide pools that are asynchronously managed in a background thread. The pool system is very flexible and can accomodate just about every need. It boasts the ability to add pool listeners so that you can instrument and intercept the pooled objects when they are created, destroyed, acquired, and released.

Dryuf Concurrent is enhancement over original Java Concurrent Future design. Apart from providing ListenableFuture functionality, it provides flexibility how to handle cancel() operations, can delay the notifications. It allows various types of notification listeners, distinguishing among successful end, failure and end due to cancel request. Last but not least, it has very low memory footprint and excellent performance, even outperforming JDK Future without listener support.

Test Drop-in Framework for Selenium WebDriver 4.1.x This repository contains these major deliverables: a) the Test Drop-in Framework, b) a WebDriver implementation offering enhanced logging capabilities, and c) the @FindByJS annotation support Provides a thin abstraction layer between the test environment and the test class plus its helpers. This makes the test code independent of the test environment, thus allowing exchange of tests between organizations or even companies. It comes with an event firing WebDriver wrapper plus corresponding interface. This allows you to implement listeners to arbitrary WebDriver activities for various purposes such as logging. Offers support of JavaScript commands to find elements in a way similar to @FindBy used on fields in Page Object classes.

This Tool provides the means to monitor the performance of Spring Batch applications without the need to manipulate the respective code basis. Through Listeners and AOP it evaluates the throughput of a monitored Job and writes the result to a simble database-schema (a file-based H2 by default). It measures the performance of Job, Step, Chunk, Reader/Processor/Writer/Tasklet down to indivdual Items. Installation/Usage: 1. Add the springBatchPerformanceMonitoring-dependency to your POM 2. Add the de.viadee.spring.batch.infrastructure.Configurator.class to your Spring-Application-Context (via @Import on your Configuration) 3. Run the Job 4. By default the monitoring result is written to project-folder/target/database/monitoringDB.mv.db