Download JAR files tagged by container with all dependencies

PLSA.R is an Open Source Java Server + API for high demand, low latency requirements. There are no static references, no file reads, access to static fields per request. Everything is either cached and or instantiated on the fly. PLSA.R runs via one command so there are no .war files to deploy, no additional plugins to install it is a simple yet powerful alternative to container deployment environments. PLSA.R even boasts a little dependency injection for data logic. www.plsar.net

This ApplicationProperties Java package provides a fast and easily configurable application.properties loader that mimics some key features of the Spring Boot application.properties loader. This package allows for multi-level overloading of properties based on a basename and optional suffix by searching the classpath, optional configurable file paths along with the JNDI server container context. The class [ApplicationPropertiesConfig](src/main/java/com/lyders/application-properties/ApplicationPropertiesConfig.java) controls the features of the overloading of properties such as the base name of the properties file, an optional suffix that allows for the loading of environment-specific or scenario-specific property files as needed. The following features are supported: * Names of properties files can be customized * Locations of properties files can be customized. The following path types are supported: * class path * file system paths * JNDI environment naming context (e.g., Servlet/JSP running under Tomcat) * Environment-specific property files can override the values in default properties files via a "suffix"

The MAJ API was written by Richard Cartwright, with the help and support of Guillaume Belrose and Fang Ren. To contact the author, please raise an issue. The software is provided AS IS with no warranty whatsoever. The MAJ API (pronounced madge) is a pure Java API for creating, reading, manipulating and writing MXF (SMPTE ST 377), AAF structured storage and Reg-XML (SMPTE ST 2001) files. MXF files are commonly used as a container for professional media file formats and AAF is supported by a number of professional video editing packages. MXF and Reg-XML are used as part of the Interoperable Mastering Format suite of specifications.

According to Docker best practices a Docker container should not be up if the process fails to load properly. Apache Tomcat deploys all the web applications loaded in its webapp folder. This is a resilient solution for web applications not influencing the application server. However, In a Docker environment according to best practice, the process should fail in case the web application failed to initialize properly. By adding the additional jar created by this project to Tomcat classpath and adding the new listener in the Tomcat conf/server.xml the user can make sure the Tomcat process fails in case there is an initialization exception in their web application which will cause the Tomcat used the tomcat container to abort in immediately indicate that there was an initialization error Abort tomcat when a webapp fails to deploy in Docker container Docker container best practice. Tomcat does not stop if a webapp fail to deploy and the container will continue to run. By adding this listener the tomcat will abort in case the Tomcat fails to deploy the webapp, And the container will not start. You will need to place the listener in Tomcat server.xml and set the Tomcat classpath to contain this jar

jmockring - Java test MOCKing tool for spRING. A test harness tool for projects using the following technology stack: - Java 6+ - Spring 3.1 or greater as a DI/Deployment container - JUnit 4 and Mockito for testing - Jetty/Servlet API 3.0 for web app (war) deployment - for testing only Main features: 1) Partial Spring context deployment with automatic bean mocking for unavailable beans 2) Bootstrapping embedded Jetty server via JUnit runners 3) Configurable web application contexts 4) Automatic injection of Spring beans and mocks in JUnit tests via Java5 annotations

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

This is an endorsed version of the original Deployment Client for Oracle GlassFish Open Source Edition. The purpose of the endorsement is to provide a shaded JAR which has the OSGI meta data removed because it causes the original Deployment Client to fail when used within a module running within a GlassFish container due to some class loader configuration conflicts between the container and the deployed module. This issue has been reported to the GlassFish project at https://java.net/jira/browse/GLASSFISH-20856 . It is hoped that it can get fixed so that this workaround project can get deprecated soon.

<b>JCAPTCHA</b>, for <b>J</b>ava <b>C</b>ompletely <b>A</b>utomated <b>P</b>ublic <b>T</b>est to tell <b>C</b>omputers and <b>H</b>umans <b>A</b>part <br/>The open source java framework for captcha definition and integration <br/> A captcha is a simple captcha container that contains a question, a challenge, and a response validation routine.<BR/> A captcha can only be built by a captcha factory that provides methods to build localized captchas.<br/> This jar aims to provide interfaces and implementation of generic and typed captcha and captcha factories.<BR/> It uses the word generator, types sub packages (image and sound) components (word to image, word to sound) to build typed captchas captchas.