Download JAR files tagged by down with all dependencies

We offer a suite of integrated utility components tailored for enterprise-level development. Our platform encapsulates common technical solutions, covering a vast range of tools and business scenarios. Designed for immediate use and easy adaptation, we aim to lower the learning curve and accelerate onboarding. Our solution alleviates the challenges faced by small and medium projects that often get bogged down in framework setup, allowing developers to stay laser-focused on delivering business value.

AutoComplete is a library allowing you to add IDE-like auto-completion (aka "code completion" or "Intellisense") to any Swing JTextComponent. Special integration is added for RSyntaxTextArea, since this feature is commonly needed when editing source code. Features include: Drop-down completion choice list. Optional companion "description" window, complete with full HTML support and navigable with hyperlinks. Optional parameter completion assistance for functions and methods, ala Eclipse and NetBeans. Completion information is typically specified in an XML file, but can even be dynamic.

With distributed systems being developed as a part of the cloud age. With focus on performance associated with an application dependent on one DB instance, there is a need to bring down the dependency to a database to generate unique numbers for creating a private key when lots of data needs to be stored in the database tables. This library is intended to provide a way of generating unique numbers on the fly in a JAVA based distributed system. This is not a new concept but this library helps in keeping you focused on the business logic that you need to develop for your applications rather than spending time on how this is done. Typically applications powered by RDBMS can leverage the benefit as instant scalability might not be available for these setups when the load to the system spikes.

Box is an add-on framework for Java EE applications that performs asynchronous gathering of source data with subsequent processing or transformation of that data into output JSON documents and exposing those documents through a web API. Box excels at maintaining existing documents including keeping them up-to-date in real time and deleting them when required. Box supports aggregating data from multiple sources as well as splitting data into multiple documents. How documents are processed is left up to each application. The web api makes the documents available by ID or by harvesting all documents. Harvests can be filtered using facets and documents can be pared down by requesting only needed fields.

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

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