Download JAR files tagged by case with all dependencies

Samply.Common.MDRFaces is a Java Server Faces library which eases the user interface design of web applications where the respective data model relies on well defined data elements. Especially in case of systems for electronic data capturing, where the necessary data model is not known beforehand and can even vary over time, the user interface has to be easily adjustable. This often means the user instead of the developer designs the various forms for data entry and therefore an easy to use mechanism has to be provided. By using Samply.MDRFaces the developer can focus on the implementation of that mechanism, e.g. some editor component, but does not have to cope with the visualization of every single data element as for that is taken care of automatically.

Adds deployment support for akka-http applications in kubernetes. The facilities are: 1) promotheus statistics export and collection for akka http routes. The library collects http result codes, timings, and requests in flight. It additionally optionally exposes some basic akka statistics. 2) Graceful shutdown, health and readiness functions. These routes are provided at a low level to they can be used by both the routing DSL and special case implementations. 3) Access log collection. These functions can be freely composed to (e.g.) exclude health check routes from statistics and access log, or include them, depending on the requirements and standards of the user

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